afb998f17b
Some checks are pending
build-gate / build (push) Waiting to run
There were THREE staging surfaces, not two. The repo-root index.html was Vite's default dev entry, and its title was the line that kept reappearing in front of the Driver: "doxa-maps · Embeddable JAMstack Maps · staging", above a bundle strip that loaded each chosen map into the page itself. It is archived with its internal/staging.js, not deleted, and git recorded both as renames so history follows. Archiving is safe because it was never a build input: rollupOptions.input is built from per-bundle JS entries, and the root HTML is referenced only on the dev branch. It was also already unreachable — the dev plugin intercepts /, /index.html, a query-string root and /__gallery, all measured returning the studio with no staging title before the move, and measured again after. What remained was a file that would resurface the moment the middleware changed. The settled-tree leaf floor drops from 50 to 40 because the architecture changed, not because the tree got sicker. That floor was set when the build also emitted a chooser page per bundle; those 19 pages are deliberately gone, which takes a correct tree from 63 leaves to 44. Left at 50 the gate would fail on every correct build, and the cheapest way to make it green again would be to restore the choosers — so a stale floor does not protect the tree, it defends the old architecture. The floor still catches the partial-wipe it was built for, and the load-bearing assertion is now that every embed.iframe target resolves: 43 checked, 0 missing. |
||
|---|---|---|
| .. | ||
| index.html | ||
| staging.js | ||