History

doxa-maps-88655c70 59e9695aaa Correct the record: the dead bundle was my merge, not a duplicate import dx-shepherd's verifier traced it. Merge `52ab6089` from this worktree committed public/doxa-maps/gospel-resources/gospel-resources.js with 21 conflict markers — both sides concatenated, 1.13 MB — and that is what threw "Identifier Ge has already been declared" and killed every gospel leaf. My diagnosis last commit was wrong. I blamed a module imported twice and re-routed the import; that change was harmless but it was not the cause. The REBUILD that came with it is what repaired the file. A plausible cause that a fix appears to confirm is the easiest kind of wrong answer to believe. THE ACTUAL CAUSE IS A LANDING SCRIPT I WROTE. On a conflict it resolves the one file it expects — public/doxa-maps/index.html — and then runs "git add -A public", which stages every OTHER file under public/ including the ones still holding markers. One line of convenience turning a conflict git correctly refused to guess at into a committed artefact. So: a check that names the real condition. It scans every tracked file for an unresolved marker, is built from character codes so it can never trip itself, and carries a poison arm. It runs FIRST in check:gospel-all, because there is no point measuring anything else about a tree that is mid-merge. Also verifies the 8 links the GRN recheck recovered, which check:gospel-all caught as shipped-but-unverified on its very first run — psi, alk, nos, jle, lma and three more, all now confirmed landing on their own 5fish language pages.		2026-09-25 10:19:07 +00:00
..
external-bundles	Data out of public/: sources live in data/, the web-root is generated	2026-09-16 01:24:41 +00:00
people-groups	All People Groups loads fast on a light map; the Vision Card becomes a true funnel from data	2026-09-25 07:18:30 +00:00
posters	The poster print preview rasterises too, and a deployment can ship sources without rasters	2026-09-24 08:07:22 +00:00
pplr	PPLR data maps (WIP): move the ten PPLR research views into plugin-designs	2026-09-25 06:33:49 +00:00
tables	Correct the record: the dead bundle was my merge, not a duplicate import	2026-09-25 10:19:07 +00:00
vendor	Vendor Vue for the gallery shell, so the self-hosted rung finally exists	2026-09-22 04:59:30 +00:00
README.md	Complete app-profiles->plugin-designs sweep across comments/docs; build green; layouts kept at root (load-bearing)	2026-09-17 18:18:19 +00:00

README.md

data/ — the bundler's source-of-truth data

The law: data lives here; public/ is generated. Every folder in data/ is copied into the served web-root by the build (internal/generate-tree.mjs), exactly like the per-profile data in plugin-designs/*/data/. You should be able to rm -rf public/ and get it all back with bun run build.

Folder	Served at	What it is
`people-groups/`	`/assets/people-groups/`	People-group datasets (CSV/JSON) the maps read at runtime
`vendor/`	`/assets/vendor/`	Third-party runtime assets (e.g. table libraries)
`posters/`	`/assets/posters/`	Rendered poster webp set (heavy pipeline output; poster walls fetch these)
`tables/`	`/assets/tables/`	The MERGED served table set (its index.json is the merge; per-profile `plugin-designs/*/data/tables` are build-time sources)
`external-bundles/`	not served	Prebuilt map IIFEs vendored from sibling projects (not built here); only the optional `layouts/` shell mounted them, so the build no longer copies them into `public/`

Don't edit anything under public/ by hand — change it here (or in plugin-designs/*/data/, layouts/*/assets/) and rebuild.