glitch-university/gupi-osint-board
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: add typed frontend exhibit registry

Browse Source
This commit is contained in:
gitprov
2026-08-14 14:20:41 +02:00
parent c8a870549d
commit edfa4c866c
6 changed files with 129 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/TODO.md
+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
docs/exhibit-data-model.md
+2 -2
View File
@@ -1,6 +1,6 @@
# GUPI OSINT Board: canonical exhibit data model
Status: accepted design foundation; core schema implemented by migration 006. Template clone operations, parties, and the frontend exhibit registry remain roadmap work.
Status: accepted design foundation; the core schema, transactional template lifecycle, and frontend exhibit registry are implemented. Parties and richer event behavior remain roadmap work.
## Vocabulary
@@ -319,4 +319,4 @@ The following are computed and must not become duplicate source-of-truth tables:
## Implemented cutover
Migration 006 made this the sole persistence model. Because the POC database contained no canonical or legacy content worth preserving, the cutover intentionally dropped the JSON case store, `widgets`, `widget_relations`, and `playthrough_*` tables without a backfill period. Template save, version selection, instantiation, and reset now use one transactional board-cloning service. The remaining architectural work is the frontend exhibit/widget registry and the planned exhibit families.
Migration 006 made this the sole persistence model. Because the POC database contained no canonical or legacy content worth preserving, the cutover intentionally dropped the JSON case store, `widgets`, `widget_relations`, and `playthrough_*` tables without a backfill period. Template save, version selection, instantiation, and reset use one transactional board-cloning service. Exhibit and document types resolve through the typed frontend registry; the remaining model work is the planned exhibit families and richer behavior.