9dc4dda8cf
Driver 2026-09-21: 'a folder called deployment which will store the capacitor
folder, wordpress folder and tauri folder', and 'a folder called documentation
to store the contributing folder so docs are in one place'.
docs/ + contributing/ + CONTRIBUTING.md -> documentation/ (three doc homes into
one). capacitor/ + wordpress/ + src-tauri/ -> deployment/.
The public/ -> dist/ rename the Driver asked about is NOT here: after seeing the
measured blast radius (855 tracked files, 54 source refs, and public/ is the
served web-root four consumers point at) the Driver withdrew it - 'keep the
public folder the same'.
Path references were rewritten mechanically (258 across 87 files), but three
classes needed hand fixes because a prefix regex cannot see them:
- join(ROOT,'docs',...) in 10 internal scripts - a quoted SEGMENT, not a prefix
- tauri frontendDist '../public' -> '../../public', since src-tauri is now one
level deeper; check:tauri caught this exactly as the card predicted
- the WordPress contract test's dirname(__DIR__,2) -> 3, same reason
Also reverted one over-reach: the rewrite renamed a FINDING-CATEGORY label
'docs' in public-hygiene-check.mjs, which is a rule name in its own header, not
a path.
Verified: full build ALL GUARDS PASS, SRI consistent; check:tauri, check:mobile
(cap sync + webDir OK), check:wp-embed, quoted-scripts, capability-citations,
capability-exemplars, library-index, public-hygiene, parse and drop all pass.
2.8 KiB
Reference — capability exemplars (GENERATED)
Do not hand-edit. Regenerate with
bun run capability-exemplars;bun run check:capability-exemplarsfails if this file falls behind the manifest.This answers one question authoritatively: which bundles are the capability-N examples right now? It is derived from
public/doxa-maps/manifest.json, which is what the build computed from each folder's real shape — so it cannot drift from what ships.Cite this file rather than remembering. The same citation has been wrong in three separate places: a gate, the README, and the
/plugin-designerskill. The trap is that a folder's apparent simplicity does not decide its tier — an*.instances.jsonmakes a bundleparameterized(cap-2) no matter how light it looks, and ameta.jsontypedeclares tiers 3/4/5.
Generated from 17 bundle(s).
Capability 1 — single-element
| Bundle | Profile | Machine key |
|---|---|---|
all-people-groups |
all-people-groups |
single |
cities-internet |
connectivity-list |
single |
cities-internet |
connectivity-map |
single |
cities-internet |
data-tables |
single |
country-posters |
countries-map |
single |
country-posters |
country-poster-wall |
single |
gospel-resources |
charts |
single |
gospel-resources |
data-tables |
single |
gospel-resources |
resources-list |
single |
gospel-resources |
resources-map |
single |
my-upg-100-list |
poster-wall |
single |
my-upg-100-list |
upg-100-list |
single |
template-bundle |
template-map-a |
single |
template-bundle |
template-map-b |
single |
Capability 2 — preset-element (prop-table)
| Bundle | Profile | Machine key |
|---|---|---|
demo-map |
demo-map |
parameterized |
doxa-simple-map |
doxa-simple-map |
parameterized |
doxa-vision-card |
doxa-vision-card |
parameterized |
people-groups-grid |
people-groups-grid |
parameterized |
Capability 3 — multi-view-element (monolithic)
| Bundle | Profile | Machine key |
|---|---|---|
doxa-research-map |
research-map |
monolithic |
research-dashboard |
research-dashboard |
monolithic |
Capability 4 — composite-element (nested-element SPA)
| Bundle | Profile | Machine key |
|---|---|---|
big-picture |
big-picture |
nested-elements-mfe |
dashboard-plus-grid |
dashboard-plus-grid |
nested-elements-mfe |
my-upg-100-list |
upg-100-mfe |
nested-elements-mfe |
stack-demo |
stack-demo |
nested-elements-mfe |
Capability 5 — app-shell (nested-SPA)
| Bundle | Profile | Machine key |
|---|---|---|
doxa-maps-spa |
doxa-maps-spa |
nested-mfe-spa |
plugin-studio |
plugin-studio |
nested-mfe-spa |