docs(37): close defaults/current split and advance the queue

This commit is contained in:
2026-11-10 18:10:35 -08:00
parent e6c6913994
commit 1d35a7400f
4 changed files with 39 additions and 35 deletions
+16 -2
View File
@@ -1,6 +1,6 @@
# TASK 37 — Defaults vs current layout split
**Status:** ☐ Queued (2026-09-20)
**Status:** ✅ Complete (2026-11-10)
## Idea (creator directive 2026-09-20)
@@ -43,6 +43,20 @@ scene[0-4].layerList.[default | current].elementList
- A `current` stamped by a different (older/newer) build-id falls back to `default`.
- Revert-to-default restores `default` for one scene or all.
## Shipped 2026-11-10
- Current scene/source tables remain the live workspace. One-time `Default*` snapshot tables and
background-path settings live in the same SQLite file; schema additions are mirrored into the
snapshots. Existing profiles promote their saved layout once; a fresh profile snapshots its seeded
layout before creator edits. Default asset references are retained during current-layout saves.
- Startup restores the snapshot transactionally when the current build stamp differs. Matching builds
keep the saved current layout. Camera identity is never replaced by a layout restore; default scene
placements are rebound to the creator's currently selected camera.
- App Settings offers **Restore staged scene** and **Restore all scenes**, disabled while live or
recording. A one-scene reset saves pending changes in other scenes and keeps that scene staged.
- Integration coverage: `LayoutStoreSnapshotTests` and `LayoutResetIntegrationTests`.
**615 tests green; clean build, 0 warnings.**
## Cross-references
- `ai.md` — persistence architecture; `MyMistakes.md` — prior reorder persistence failures.
- `ai.md` — persistence architecture; `MyMistakes.md` — prior reorder persistence failures.