feat: add immutable level template lifecycle
This commit is contained in:
+1
-1
@@ -30,7 +30,7 @@ This is the ordered implementation roadmap following the accepted exhibit model.
|
||||
|
||||
- [x] Add boards, exhibits, exhibit types, subtype tables, immutable template versions, and mutable levels.
|
||||
- [x] Cut over the explicitly disposable POC database directly; no transitional data existed to backfill or compare.
|
||||
- [ ] Implement template instantiation and “save level as template” as transactional clone operations.
|
||||
- [x] Implement template instantiation, version selection, reset, and “save level as template” as transactional clone operations.
|
||||
- [x] Introduce a server-side repository/service boundary so SQL and cloning transactions do not live in Express route handlers.
|
||||
- [ ] Move the frontend to an exhibit/widget registry backed by the normalized API.
|
||||
- [x] Remove transitional `widgets`, `widget_relations`, and `playthrough_*` tables in the canonical cutover migration.
|
||||
|
||||
Reference in New Issue
Block a user