refactor: add typed frontend exhibit registry

This commit is contained in:
2026-08-14 14:20:41 +02:00
parent c8a870549d
commit edfa4c866c
6 changed files with 129 additions and 23 deletions
+1 -1
View File
@@ -32,7 +32,7 @@ This is the ordered implementation roadmap following the accepted exhibit model.
- [x] Cut over the explicitly disposable POC database directly; no transitional data existed to backfill or compare.
- [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] Move exhibit and document rendering to a typed frontend widget registry backed by the normalized API.
- [x] Remove transitional `widgets`, `widget_relations`, and `playthrough_*` tables in the canonical cutover migration.
## Milestone 3: events and parties