refactor: isolate level persistence from HTTP routes

This commit is contained in:
2026-08-14 13:57:51 +02:00
parent 545eb013bd
commit 9702b9c3d9
3 changed files with 291 additions and 219 deletions
+1 -1
View File
@@ -31,7 +31,7 @@ This is the ordered implementation roadmap following the accepted exhibit model.
- [ ] Add boards, exhibits, exhibit types, subtype tables, immutable template versions, and cloned mutable levels.
- [ ] Migrate transitional `widgets`, `widget_relations`, and `playthrough_*` data with equivalence checks.
- [ ] Implement template instantiation and “save level as template” as transactional clone operations.
- [ ] Introduce a server-side repository/service boundary so SQL and cloning transactions do not live in Express route handlers.
- [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.
- [ ] Remove transitional tables only after automated data-equivalence and behavior checks pass.