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

Adding fixes that lets us pull a myster in the db into a json file

Browse Source
This commit is contained in:
gitprov
2026-08-23 21:37:06 +02:00
parent 3c099a5daa
commit 7dec2994b4
8 changed files with 719 additions and 290 deletions
Download Patch File Download Diff File Expand all files Collapse all files
mysteries/README.md
+21 -3
View File
@@ -1,14 +1,32 @@
# Mystery content packages
Mysteries live outside the React application as authoring manifests and immutable source assets. Importing a manifest exercises the same public operations as the level editor: it creates a mutable authoring level, uploads assets, saves normalized exhibits, freezes an immutable template version, and instantiates a separate playable level.
A mystery is a self-contained, version-controlled folder: `mysteries/<slug>/mystery.json` plus a `mysteries/<slug>/assets/` sidecar for any binary assets it references by filename. A single `mystery.json` holds the whole story — the flow `narrative` (NPC cast + graph) and every `levels[]` board the graph embeds — so one directory reproduces one complete mystery.
Importing exercises the same public operations as the level editor: for each embedded level it creates a mutable authoring level, uploads assets, saves normalized exhibits, freezes an immutable template version, and instantiates a playable level; then it authors the mystery and seeds its story graph.
With the local Docker stack running and editing enabled:
```bash
npm run mystery:import -- mysteries/glass-harbor/mystery.json
npm run mystery:import -- mysteries/barricelli-files # a folder (self-contained)
npm run mystery:import -- mysteries/glass-harbor/mystery.json # or a single manifest
```
The command prints the template version, authoring-level ID, playable-level ID, and player URL. Importing the same manifest again creates a new immutable version; it does not rewrite an earlier version.
Importing the same content again creates a new immutable template version; it does not rewrite an earlier version.
## Syncing back from a running instance
`mystery:pull` serializes a mystery from a running instance's database into the folder format above, so you can edit on a server and bring the result back into git. It defaults to the local dev instance; pass `--prod` to pull from https://gupi.glitch.university (which requires an `OSINT_ADMIN_JWT` minted inside the `gnommo-osint-board` container).
```bash
npm run mystery:pull -- barricelli-files # dev → mysteries/barricelli-files/
OSINT_ADMIN_JWT=<token> npm run mystery:pull -- barricelli-files --prod
```
The pull is deterministic and round-trips: importing a pulled folder into a clean database and pulling again yields an identical `mystery.json`. Node/utterance keys are synthesized from labels, so a re-exported file is stable but need not match hand-written keys byte-for-byte — the exported file is the source of truth. (Known gaps: node music and NPC pose artwork are not yet carried through the pull.)
## Legacy single-manifest format
`glass-harbor/` and `barricelli-scene-7/` are older single-manifest packages (one level plus an optional inline `narrative`) kept as importer test fixtures — `barricelli-scene-7/fixtures/` holds OCR text used by the integration tests. `mystery:import` still accepts this shape (a file with no top-level `levels[]`); new mysteries should use the self-contained folder format.
## The Glass Harbor Diversion