|
Some checks are pending
build-gate / build (push) Waiting to run
Ran the browser-free gate suite inside a fresh clone -- the inheritor's conditions. Five passed; check:dxlife went red with "clone not found at /root-dx-life - nothing to check". That is not a defect. The gate deliberately uses three values (0 unchanged, 1 drift, 2 no clone) because it exists after a check that returned the PASS value BECAUSE IT FAILED: `cd root-dx-life && git status --porcelain | wc -l` printed 0 for a directory that is not a git repo. Collapsing "cannot judge" into "pass" is exactly the bug it was written to prevent. But `bun run` and any && chain see only zero/non-zero, so the middle value evaporates precisely where a reader consumes it. The fix belongs in the documentation, not the gate: added a preconditions row stating what it needs, what exit 2 means, and that it is NOT in build:unlocked, so a clone still builds. Verified the whole inheritor path again after the Cargo.lock change: clone (2358 files, lockfile present) -> bun install exit 0 -> bun run build exit 0, 18 bundles / 27 profiles, with check:dep-names and check:no-abs-paths both running inside the clone's own build. |
||
|---|---|---|
| .. | ||
| architecture | ||
| assets | ||
| contributing | ||
| readme-images | ||
| screenshots | ||
| CONTRIBUTING.md | ||
| 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 | ||
documentation/ — 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.