688ba6cfde
★ THE PRECONDITION WAS RIGHT AND I COULD NOT READ IT. It refused four landings saying "a committed composite is not what its source builds" without naming one, and my own freshness run said clean. Running check-composite-freshness at the precondition's exact scope threw instead: a SyntaxError parsing public/dx-maps/manifest.json — '<<<<<<< HEAD' at position 2317. Ten built files carried committed conflict markers: both manifests and eight leaf pages. They came in through my own merge resolutions. 'git restore --ours' on a conflicted path gives MY side — and once markers were committed once, my side had them, so every later merge carried them forward and the precondition kept refusing a tree it literally could not parse. Regenerating from source clears all ten. The lander now checks for markers before committing built output, because a gate that cannot parse its input fails in a way that looks like the thing it was checking for. |
||
|---|---|---|
| .. | ||
| dx-maps | ||
| 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: 23 plugin bundles and 35 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.