The badge read "27/26 zones" — a count exceeding its own total — in two shipped README screenshots. 26 was the leaf count before slice 09b-6 added the Frontier-Asia uncovered rows; the literal was never updated, so it drifted the moment the data grew. The denominator is now derived from perZone.size, which tracks the zone list automatically and cannot disagree again. Measured from clusters.json: 13 regional + 12 asia + 2 uncovered + 1 deaf = 28. The corrected badge also surfaces 1 genuinely unresolved zone that the stale denominator was masking. legend-tree.js asserted "33 leaves" and "7 Frontier-Asia uncovered" in a comment; the shipped data carries 28 and 2. Corrected to point at the arrays instead of a count. README showed "List — page 1" and "List — page 2" as the same picture. The shot loaded one URL twice and tried to reach a page 2 by scrolling and clicking Next; neither exists, the list has no pagination, and every attempt sat in try/catch so the miss was silent. The PNGs differed by 0.16% render noise, so no checksum would have caught them. Mean- while poster-wall — a real manifest-listed profile — had no screenshot at all. Shoot the real third thing rather than fake a fourth. check:shot-distinctness gates this, blocking in CI. It keys on url+viewport, so the deploy2 mobile shot of the same SPA stays legitimate rather than a false positive. |
||
|---|---|---|
| .. | ||
| 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-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.