24b9ada48e
The Driver: a public plugin that is not yet a production map shows under Experimental until it is. A profile's .meta.json declares "stage": "production" | "experimental" (default experimental; a bundle is production if any profile says so) and "heavy": true for a live WebGL owner. generate-tree carries both into manifest.json, so the Studio and the gallery read the same field and neither keeps a list. The seven production bundles are marked: dashboard-plus-grid, research-map-plus-grid, regions-dashboard, my-upg-100-list, doxa-simple-map, cities-internet, gospel-resources. The Studio rail keeps its capability sections for them and puts every experimental bundle (gospel-internet among them) in one final Experimental section. The gallery's auto-discovered Experimental folder skips a production bundle. gospel-internet-board joins HEAVY_ELEMENTS (it can own two WebGL contexts). check:studio-rail asserts the split.
7 lines
1,015 B
JSON
7 lines
1,015 B
JSON
{
|
|
"stage": "production",
|
|
"_comment": "Capability-4 composite: the monolithic doxa-research-map (cap-3) stacked above the people-groups-grid (cap-2), scrolled as one element. THE MOBILE SIBLING of dashboard-plus-grid — the Driver's 2026-09-22 ruling was two separate cap-4 plugins rather than one element that swaps its top half by aspect ratio ('that would be really complex'); the SPA picks which one to show. Composes by TAG + BUNDLE URL (the stack-demo element/src contract) rather than baking the children in, because importing the research map's .vue directly would bypass doxa-research-map/index.js and silently drop its bundle-private colour strategies, its profileModules registry, its Pinia/i18n pair and the RTL plugin. The grid's own search + filters are ON here (unlike the desktop sibling, where the dashboard header owns them).",
|
|
"type": "nested-elements-mfe",
|
|
"composes": ["doxa-research-map", "people-groups-grid"],
|
|
"label": "Research Map + Grid (mobile composite, stacked to scroll)"
|
|
}
|