Dev demo campaign: a full test campaign for reviewing as a player (#821) #822
Loading…
Reference in a new issue
No description provided.
Delete branch "build/demo-seed"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes nothing yet: #821 closes once the seed has been run on dev and checked.
What it is.
webapp/backend/demo/is a deterministic, re-runnable seed that puts one rich campaign on dev, so the owner can review the redesign against realistic data, as a player. It lives outsideapp/and is excluded from the image (.dockerignore). It runs inside the backend container with the package mounted, and the command is indemo/README.md.Two campaigns, in the prototype's fiction:
--member-user-idaccount plays Hollis Fenwright.demo/packs/: one good, one deliberately broken.Safety:
demo-seedissuer,@demo.invalid) and the single member account. The member's own user row is never modified.--resetgives identical ids.--dry-runrolls back.The standing rule. The build plan's §7 gains a rule: a lane that adds or changes a feature extends this seed in the same series. The README's coverage table lists what isn't built yet, and which lane owns it (discussions and lines and veils in lane 7, the wiki's pieces in lane 8, and so on).
Tests.
tests/test_demo_seed.py: 6 passed, with all the content, on postgres 16.--reset×3.🤖 Generated with Claude Code