History

doxa-maps 71f36b5079 A9 leaf hints: key on the bundle's engine, not the leaf's isMap flag rega's A9NET run found two production composite tabs — regions-dashboard/ regions-mfe and research-map-plus-grid — getting NO hints, because my first cut gated on the leaf's isMap flag and both are isMap:false composites that mount a map child and load the engine at runtime. Same trap the check:leaf-engine-per-provider isMap gate fell into. The gate now keys on whether the leaf's OWN page loads a map engine: a real map leaf (isMap), OR a cap-4 nested-elements-mfe composite whose BUILT bundle references an engine (builtBundleLoadsEngine). It excludes a cap-5 nested-mfe-spa shell (maps are iframe children), a genuinely map-less composite (big-picture, stack-demo: 0 engine refs), and a plain non-map leaf sharing a bundle with a map (connectivity-list). regions-mfe (33 engine refs) is now hinted; research-map-plus-grid is not — its own bundle has 0 refs, the engine loads in a lazily-fetched child (recorded gap; the deeper cause is the upstream isMap classifier mislabelling these composites, which composes-by-tag where the child .vue filename differs). check:leaf-hints rebuilt to the same rule, read from the manifest (profile type + isMap) and the built bundle, so gate and generator cannot drift. PASS 37 hinted / 27 bare; both new poisons bite (composite stripped of hints; non-map leaf in a map bundle given a hint).	2026-09-29 14:40:27 +00:00
..
dx-maps	A9 leaf hints: key on the bundle's engine, not the leaf's isMap flag	2026-09-29 14:40:27 +00:00
README.md	Gate the country-name join, and record that the wiring was already done	2026-09-29 01:38:07 +00:00

doxa-maps 71f36b5079 A9 leaf hints: key on the bundle's engine, not the leaf's isMap flag

rega's A9NET run found two production composite tabs — regions-dashboard/
regions-mfe and research-map-plus-grid — getting NO hints, because my first
cut gated on the leaf's isMap flag and both are isMap:false composites that
mount a map child and load the engine at runtime. Same trap the
check:leaf-engine-per-provider isMap gate fell into.

The gate now keys on whether the leaf's OWN page loads a map engine: a real
map leaf (isMap), OR a cap-4 nested-elements-mfe composite whose BUILT bundle
references an engine (builtBundleLoadsEngine). It excludes a cap-5
nested-mfe-spa shell (maps are iframe children), a genuinely map-less
composite (big-picture, stack-demo: 0 engine refs), and a plain non-map leaf
sharing a bundle with a map (connectivity-list). regions-mfe (33 engine refs)
is now hinted; research-map-plus-grid is not — its own bundle has 0 refs, the
engine loads in a lazily-fetched child (recorded gap; the deeper cause is the
upstream isMap classifier mislabelling these composites, which composes-by-tag
where the child .vue filename differs).

check:leaf-hints rebuilt to the same rule, read from the manifest (profile
type + isMap) and the built bundle, so gate and generator cannot drift. PASS
37 hinted / 27 bare; both new poisons bite (composite stripped of hints;
non-map leaf in a map bundle given a hint).

2026-09-29 14:40:27 +00:00

dx-maps

A9 leaf hints: key on the bundle's engine, not the leaf's isMap flag

2026-09-29 14:40:27 +00:00

README.md

Gate the country-name join, and record that the wiring was already done

2026-09-29 01:38:07 +00:00

README.md

public/ — the built output

This folder is GENERATED by bun run build; do not edit it by hand. It holds exactly one thing:

dx-maps/ — the output folder: 25 plugin bundles and 37 pages, self-contained. Copy this one folder to any web host (or open it from disk) and it works.
- dx-maps/index.html — the front page: the Plugin Studio, every plugin in one place.
- dx-maps/<plugin>/<plugin>.js — a plugin's bundle (a custom element; load it with a <script> tag).
- dx-maps/<plugin>/<page>/index.html — a ready-made page for one plugin view (embed it in an <iframe>).
- dx-maps/manifest.json — every plugin, page and embed snippet, machine-readable.
- dx-maps/assets/ — the data, fonts and images the plugins fetch at runtime.

The folder's name comes from name in vite.doxa-maps-build-config.json. Sources live in plugin-designs/, library/ and data/; rm -rf public/ && bun run build recreates all of this.