History

doxa-maps-88655c70 e94253ed58 Some checks are pending build-gate / build (push) Waiting to run Details Route the north-star doc through the fast studio loop develop-a-plugin-and-see-it-live.md is the path an inheriting agent follows end to end, and it mentioned the plugin studio once while sending every iteration through a full build. Step 3b already argues well that a green build proves nothing about mounting -- it just pointed only at smoke:embeds, which needs the build first. Adds Step 3a: bun run dev, then bun run smoke:studio. Measured 4.7s for 29 tabs with 0 failed requests, against a full build of 43s to 4min on the same box -- 19 sequential bundles, queued behind any other build, so the spread is real. An order of magnitude either way, which is the point. A first draft said "roughly fifty times faster", derived by dividing by a remembered 4-minute constant rather than by what the build log actually showed (43s). Replaced with the measured range. That is the same defect this session flagged on the Forgejo card an hour earlier: a stored number that rots, quoted as if it were evidence. Also states why both steps exist rather than one replacing the other: the dev manifest hands rooted refs and the built manifest hands relative ones, so a base-join bug is invisible in one surface and fatal in the other. And names the single staging environment explicitly, pointing at /__gallery as the archived index kept only because the dev server imports its renderer -- so a reader who stumbles on it does not mistake it for a place to review work.		2026-09-22 20:06:04 +00:00
..
architecture	Document why a gate cannot import plugin source, and stop teaching public binds	2026-09-22 17:40:11 +00:00
assets	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
contributing	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
readme-images	Give the README map screenshots their basemap back	2026-09-22 10:16:54 +00:00
screenshots	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
CONTRIBUTING.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
develop-a-plugin-and-see-it-live.md	Route the north-star doc through the fast studio loop	2026-09-22 20:06:04 +00:00
explanation.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
how-to.md	Land the swarm's work: no iframes anywhere, a tree that keeps its shape, deeper facets	2026-09-22 14:51:52 +00:00
README-embed-example.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
README-longform.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
README-SECTION-3-cli-commands.md	Check a composite registers everything the leaf it bakes registers	2026-09-22 18:55:01 +00:00
README.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
reference-capability-exemplars.md	Give nested ProfileLoader children the profile-config they require	2026-09-22 09:37:35 +00:00
reference-library-index.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
reference.md	Document why a gate cannot import plugin source, and stop teaching public binds	2026-09-22 17:40:11 +00:00
slide-deck-outline.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
tutorial.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
why.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00

README.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-config contract.
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.