feat: campaign templates and cloning (#125) #1215
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/125-campaign-templates"
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?
Fixes #125: campaign templates and cloning. Design:
docs/design/campaign-templates.md(branchdesign/125-campaign-templates). The owner answered Q188 to Q191, all (a).Server
a125c0b1e5e1(revisesa126ca1e0d01, the calendar). It adds:campaigns.one_shot_archive_dismissed_at;campaign_invites.invited_role(player or gm);import_jobs.kindandclone_args;campaign_invitation.setup_only, keeps an allow-list of sections, and never carries history:GET …/setuplists the pages by kind with default ticks: the world is ticked, and player characters, quests and pages that came from a session are not.POST …/setup-filereturns the setup zip.POST …/cloneruns a background job through the import machinery. The new campaign is owned by the caller, and both campaigns get an audit row.campaign_invitationnotification, in the bell and by email under each person's own settings. It carries only a line and the link.kind.Screens
Tests
test_campaign_setup_copy(48+), export, notifications and parity, 256 in the latest run; the full suite in the 4.6.0 rehearsal passed 10,333.Squash on merge.
🤖 Generated with Claude Code