|
Some checks are pending
build-gate / build (push) Waiting to run
The OPEN WORK line asks for Playwright coverage over every plugin AND ALL SHARING. Sharing had never been exercised across the set this flight: the gate needs a served tree, a token, per-plugin --url flags and (on this box) --browser chromium, so a bare `bun run smoke:share` only prints usage. Derived the real coverage set -- grep -rln ShareButton plugin-designs/*/*.vue gives 8 built leaves -- and ran it: 8/8 pass. Every Share button emits a URL that resolves 200 text/html and reopens the correct element with a live canvas. The pass count alone would have proved nothing. The failure this gate exists to catch, an SPA fallback or a host stripping the hash deep-link, renders A map for every share URL, so all 8 pass while all 8 links are wrong. The discriminating evidence is six DISTINCT reopened tags, each matching its own plugin, canvas:y on all eight. reference.md now carries the copy-paste invocation, verified by running it verbatim from a clean shell (8/8, same six tags). It also corrects a detail: the doc said Firefox, which is the default but stops on this box -- the tool detects its own WebGL limitation and names the chromium flag in its output. |
||
|---|---|---|
| .. | ||
| 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.