Loading…
Reference in a new issue
No description provided.
Delete branch "build/demo-seed-lanes-8-10"
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?
This extends the dev demo seed (
webapp/backend/demo/) to lanes 8 and 10. Every built feature gets at least 5 entries of different kinds, plus a README coverage row. The lane 8 rows move out of "Not built yet".Seeded:
:::gm×10,:::for×5 (one for the owner's character) and:::party×2;content.pyrefuses names it can't resolve.readyand 1failed);audio_deleted_atset. There are 5session_usagerows withpurpose='test'.Files:
media/private/campaigns/<demo campaign>/.--dry-run.--resetclears only the demo campaigns' own folders, and the writer refuses any path outside them.Maps are tiled synchronously: the task's cutting loop moved into a pure
app.tasks.map_tiles.cut_tiles(), which the task and the seed both call. The behaviour is unchanged.Not seeded (in the README):
shelf_reveal_messages(nothing went to Discord),platform_linksandnotification_deliveries.Found: a raw
DELETE FROM campaignsfails onquest_objectivesbecause of two cascade paths. The app's ORM purge is fine. Filed as #943; the seed deletes the lane 8 tables first.Checks:
test_demo_seed.pyplus the wiki map, tile, picture, handout and quest tests: 83 pass.--reset(same ids, stale file removed) and--dry-run(no files) all behave.changelog.py checkpass.Next dev deploy: re-run the seed with
--reset.🤖 Generated with Claude Code