d0568ebd35
Card 1 asks that one public Forgejo repo be the live catalog source and that the merge lose nothing. Both halves were marked done-verified on 2026-09-19, two publishes ago, so this re-measures rather than trusting the field: the catalog is still a zero-diff match for the freshly-built tree, all 17 live bundles hash to their own manifest integrity, and the live public manifest is byte-identical to the catalog's. An HTTP status cannot make that claim. /app/doxa-maps/manifest.json returns 200 and is a 2,872-byte HTML sign-in page, so a status check reads the login wall as healthy. Every profile already carries an integrity hash the build computed for an unrelated reason, so comparing it against the live bytes is a cryptographic identity proof with no new source of truth to keep in sync. Network-dependent, so not in build:unlocked and not in CI. It distinguishes "could not reach" from "reached and wrong" and only the latter fails, because a gate that fails on a network blip gets switched off. Negative-tested four ways: the login wall fails with the reason, an unreachable host skips at exit 0, the catalog-comparison mode confirms the sha256 match, and the baseline proves 17 of 17. |
||
|---|---|---|
| .. | ||
| architecture | ||
| assets | ||
| readme-images | ||
| screenshots | ||
| develop-a-plugin-and-see-it-live.md | ||
| explanation.md | ||
| how-to.md | ||
| README-embed-example.md | ||
| README-longform.md | ||
| README-SECTION-3-cli-commands.md | ||
| README.md | ||
| reference-capability-exemplars.md | ||
| reference-library-index.md | ||
| reference.md | ||
| slide-deck-outline.md | ||
| tutorial.md | ||
| why.md | ||
docs/ — pick your path
"what is this?" "teach me" "how do I …?" "look it up" "all the detail"
│ │ │ │ │
why.md ──────────► tutorial.md ────► how-to.md ────► reference.md ───► architecture/
(2 min, 1 diagram) (first map) (task recipes) (tables) (contracts)
- why.md — the problem and the "map islands" idea. Start here.
- tutorial.md — build your first map, no jargon.
- how-to.md — recipes: embed, iframe, SPA, colors, CDN, mobile, tokens.
- reference.md — config fields, build scripts, the
profile-configcontract. - explanation.md — the model in 15 lines.
- architecture/ — the deep end: full contracts, the per-file catalog.
- README-embed-example.md — the drop-in README used when this bundler is embedded inside a host repo.
Nothing on the simple path is longer than a few minutes; everything complex lives in
architecture/, linked from where you'd need it.