Demo seed: The Amberwake Accord (GM copy), with the owner in the GM's seat (#951) #954

Merged

claude-bot merged 4 commits from build/demo-gm-copy into main 2026-09-30 06:38:48 +00:00

Conversation 0 Commits 4 Files changed 6 +889 -464

claude-bot commented 2026-09-30 06:09:31 +00:00

Collaborator

Copy link

Closes #951. The owner's review of lanes 0–10 has about 40 GM-only pieces, and on dev the owner is only ever a player in the demo campaigns. This adds a fifth demo campaign, "The Amberwake Accord (GM copy)": Amberwake mirrored row for row under its own ids, with two seats swapped. The owner sits in Dana's GM seat (and owns the campaign); Dana sits in the owner's player seat and plays the owner's character, Hollis.

How it works:

• The variant: demo/engine.py has a frozen Variant(salt, name, swap_seats).
  • AMBERWAKE is the original; GM_COPY has salt gm-copy.
  • Variant.did() salts every deterministic id except people (user:*, which are shared).
• The builder: it takes the variant.
  • self.main_id and self.did() replace the module constants (a mechanical rewrite across Builder and WikiMixin).
  • self.dana became self.gm, and uid() maps the member and Dana through the seats.
  • The engine's own GM strings ("Edited by …", "Rewritten by …", the pack publisher, audit lines) name the owner in the copy.
• The build: it runs the original, then mirror():
  • the main campaign, prep, lane 8 and the party;
  • not the people, the Tuesday Tide or the admin campaigns.
• --reset and the guards: GM_COPY_ID is in CAMPAIGN_IDS, so --reset, delete_demo, the "elsewhere" guard and write_media's folder guard cover it with no other change. Everything stays inside the same armed tripwires and one transaction.
• Notifications: the copy's bell is a GM's:
  • transcript ready and failed, wiki suggestions, a member joined, ownership answered, safety waiting, and threads started;
  • plus session_at_risk and audio_deletion_pending, which only a GM gets.
  • Dana's bell is the owner's Amberwake player bell, re-addressed.

Deliberately identical: transcripts and world text. So "Dana" still appears inside content (the table talk, and a few template lines). Only the engine's own attributions change.

Not mirrored:

• the Tuesday Tide's share of lanes 6 and 8;
• the other three campaigns;
• content notices;
• the two admin audit events about Amberwake's pack.

Checks:

• test_demo_seed.py: 6 pass. The new mirror test covers:
  • the copy's name, owner and seats;
  • equal per-table counts across 59 tables (notifications +2, audit −2, as above);
  • GM-authored rows attributed to Dana in Amberwake and to the owner in the copy (a prep sheet, an approval, a reveal, a bot test);
  • :::for rendering for Dana and the GM, and not for Marcus;
  • the GM bell's kinds;
  • the round trip for --reset, and files in each campaign's own folder (76 each).
• The CLI on a freshly migrated database:
  • the first run wrote 5 campaigns and 152 files;
  • a re-run said "already exists" and exited 0;
  • --reset rebuilt it;
  • --dry-run wrote nothing.
• The originals are unchanged: main's seed and this branch's were compared row by row in fresh databases. Every main row is present, except for server now() timestamps and one existing random default (a quest page's lore_entries.version_id). The branch's extra rows are exactly the copy.
• Lint and changelog: ruff check and format are clean, and changelog.py check passes.

On dev: the next deploy re-runs the seed with --reset. The README says how.

Changelog: changelog.d/951-demo-gm-copy.added.md.

🤖 Generated with Claude Code

Closes #951. The owner's review of lanes 0–10 has about 40 GM-only pieces, and on dev the owner is only ever a player in the demo campaigns. This adds a **fifth demo campaign, "The Amberwake Accord (GM copy)":** Amberwake mirrored row for row under its own ids, with two seats swapped. The owner sits in Dana's GM seat (and owns the campaign); Dana sits in the owner's player seat and plays the owner's character, Hollis. **How it works:** - **The variant:** `demo/engine.py` has a frozen `Variant(salt, name, swap_seats)`. - `AMBERWAKE` is the original; `GM_COPY` has salt `gm-copy`. - `Variant.did()` salts every deterministic id except people (`user:*`, which are shared). - **The builder:** it takes the variant. - `self.main_id` and `self.did()` replace the module constants (a mechanical rewrite across `Builder` and `WikiMixin`). - `self.dana` became `self.gm`, and `uid()` maps the member and Dana through the seats. - The engine's own GM strings ("Edited by …", "Rewritten by …", the pack publisher, audit lines) name the owner in the copy. - **The build:** it runs the original, then `mirror()`: - the main campaign, prep, lane 8 and the party; - not the people, the Tuesday Tide or the admin campaigns. - **`--reset` and the guards:** `GM_COPY_ID` is in `CAMPAIGN_IDS`, so `--reset`, `delete_demo`, the "elsewhere" guard and `write_media`'s folder guard cover it with no other change. Everything stays inside the same armed tripwires and one transaction. - **Notifications:** the copy's bell is a GM's: - transcript ready and failed, wiki suggestions, a member joined, ownership answered, safety waiting, and threads started; - plus `session_at_risk` and `audio_deletion_pending`, which only a GM gets. - Dana's bell is the owner's Amberwake player bell, re-addressed. **Deliberately identical:** transcripts and world text. So "Dana" still appears *inside* content (the table talk, and a few template lines). Only the engine's own attributions change. **Not mirrored:** - the Tuesday Tide's share of lanes 6 and 8; - the other three campaigns; - content notices; - the two admin audit events about Amberwake's pack. **Checks:** - **`test_demo_seed.py`:** 6 pass. The new mirror test covers: - the copy's name, owner and seats; - equal per-table counts across 59 tables (notifications +2, audit −2, as above); - GM-authored rows attributed to Dana in Amberwake and to the owner in the copy (a prep sheet, an approval, a reveal, a bot test); - `:::for` rendering for Dana and the GM, and not for Marcus; - the GM bell's kinds; - the round trip for `--reset`, and files in each campaign's own folder (76 each). - **The CLI** on a freshly migrated database: - the first run wrote 5 campaigns and 152 files; - a re-run said "already exists" and exited 0; - `--reset` rebuilt it; - `--dry-run` wrote nothing. - **The originals are unchanged:** main's seed and this branch's were compared row by row in fresh databases. Every main row is present, except for server `now()` timestamps and one existing random default (a quest page's `lore_entries.version_id`). The branch's extra rows are exactly the copy. - **Lint and changelog:** ruff check and format are clean, and `changelog.py check` passes. **On dev:** the next deploy re-runs the seed with `--reset`. The README says how. Changelog: `changelog.d/951-demo-gm-copy.added.md`. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

claude-bot added 4 commits 2026-09-30 06:09:31 +00:00

WIP #951: thread a Variant through the demo Builder for the GM copy ... 04aee299a6

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

WIP #951: tests for the GM copy ... 16c1e223e5

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

WIP #951: GM copy tests pass; scope Amberwake-only checks to the original ... 660e47c104

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

WIP #951: README and changelog fragment for the GM copy ... c70e6ce822

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

claude-bot merged commit 2c0e05aead into main 2026-09-30 06:38:48 +00:00

claude-bot referenced this pull request from a commit 2026-09-30 06:38:50 +00:00

Merge PR #954: demo seed — The Amberwake Accord (GM copy) (#951)

claude-bot referenced this pull request 2026-09-30 06:39:23 +00:00

Demo seed: a GM copy of The Amberwake Accord, with the owner in the GM's seat #951

claude-bot referenced this pull request 2026-09-30 06:40:52 +00:00

A raw campaign DELETE works: quest_objectives' FK is deferred (#943) #957

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

backend

Issue related to the backend

  

bot

Issue related to the bot

  

bug

Something is not working

  

duplicate

This issue or pull request already exists

  

enhancement

New feature

  

frontend

Issue related to the frontend

  

help wanted

Need some help

  

invalid

Something is wrong

  

question

More information is needed

  

recording

Issue related to the recording system

  

security

Security hardening / vulnerability work

  

wontfix

This won't be fixed

No labels

backend

bot

bug

duplicate

enhancement

frontend

help wanted

invalid

question

recording

security

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

rbrooks/Quest-Board!954

No description provided.