feat(questionnaires): F9.4 demo-content seed + F9.2 operational runbook#57
Merged
Merged
Conversation
F9.4 — env-gated, DEMO-ONLY seed (025-demo-content.ts) that populates a "Northwind Logistics" demo client plus a fully launched, attributed sample questionnaire on a fresh DB. No-ops unless LOAD_DEMO_CONTENT=1, so it never loads in production; idempotent on re-seed; writes through the real ingestion writeGraph seam rather than hand-rolled inserts. A fork strips it via the DEMO-ONLY marker. F9.2 — operational runbook (runbook.md) taking a presenter from fresh checkout to a respondent answering the first question: seeded fast path, branding, content (clone-first), launch, invite, first session, reset. Cross-linked from demo-clients.md. Also: mark P0–P9 feature trackers done, document LOAD_DEMO_CONTENT in .env.example, refresh development-plan status. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two P9 deliverables on one branch (F9.4 built first so the F9.2 runbook can exercise it).
F9.4 — Demo content seed (DEMO-ONLY)
A one-command seed (
prisma/seeds/app-questionnaire/025-demo-content.ts) that takes a fresh DB from nothing to something demo-able, no admin clicks:LOAD_DEMO_CONTENT=1, so it can never load in production. The gate lives insiderun()so the runner still stampsSeedHistoryon the no-op.writeGraph(the same path the ingestion route uses), not hand-rolled inserts.DEMO-ONLY; a fork strips it viagrep -rl "DEMO-ONLY". Nothing imports it (glob-discovered), so deletion is clean.F9.2 — Operational runbook
.context/app/questionnaire/runbook.md— a road-tested "spin up a demo client end-to-end" walkthrough taking a presenter from a fresh checkout to a respondent answering the first question: seeded fast path → branding → content (clone-first, upload-and-extract as alternative) → launch → invite → first session → reset. Cross-linked fromdemo-clients.md(the demo hub). Documentation only — no runtime capability.Housekeeping
LOAD_DEMO_CONTENTin.env.example(with the "didn't appear? clear SeedHistory" gotcha).doneand refreshdevelopment-plan.mdstatus.f9.2.md,f9.4.md).Test plan
npm run type-checkpasses.LOAD_DEMO_CONTENT=1 npm run db:seedon a fresh DB → Northwind demo client + launched questionnaire appear; re-seed produces no duplicates.npm run db:seedwithout the flag → no-op (no demo content).🤖 Generated with Claude Code