2 commits

Author	SHA1	Message	Date
doxa-maps-88655c70	59f497eb67	Six more browser gates measure THIS build or nothing ... a9550858 guarded twenty gates; these six were still unguarded. Each now exits 75 (NOT MEASURED) rather than grading another tree: - check-legend-export-reachable, check-vision-card-numbers --url: requireThisTree on the URL they are given. - check-embed-basemap-paints: it picks a RANDOM port, not an OS-assigned one, so if another agent holds it, its own server fails to start and it would measure theirs. It now checks the leaf server's identity, stops its own servers and exits 75. Its "a server did not come up" path exited 1 and now exits 75. - check-tabs-localized, check-poster-prints read library/ from DOXA_REPO. Pointing that at another checkout now needs DOXA_REPO_MEASURE_OTHER=1 (new requireThisRepo helper). - check-packet-render refuses a packet file inside a DIFFERENT git checkout (new requirePathInThisCheckout helper); a file outside any checkout is allowed with a note. Proven by pointing each at a wrong build: a copy of this public/ whose manifest differs by one byte, served on its own port, and another worktree for the file and DOXA_REPO gates. All 8 (these 6, plus shell-scroll and upg-map-data) exit 75. On this tree they measure: legend-export, vision-card, upg-map-data, tabs-localized and poster-prints PASS. packet-render gets past the guard and fails on a non-packet file, as intended. embed-basemap measures and FAILS: "the page does NOT paint a basemap on its own baked token". That is a product finding, not the guard, and is reported to its owner.	2026-09-25 10:03:16 +00:00
doxa-maps-88655c70	4cb04480cc	Localize tab labels for it/ro/zh, and prove the catalog is actually read ... 120 keys across three locales: legend.json (12 each), search.json kinds (10 each) and tabs.json (18 each, previously absent entirely). Each locale follows its own established vocabulary rather than a parallel one — Popolo/Popor/民族, matching the terms already used in that catalog's detail and legend strings. zh stays Simplified here, as the rest of this tree is, even though the prayer packet's zh block is Traditional: a reader sees 民族 next to 祷告进度, never the two files side by side. Ceilings drop 94 -> 54 per locale. regions.json is the only i18n debt left in the app: 54 keys of full sentences, three locales. WHY THE NEW GATE. check:i18n-parity compares catalogs TO EACH OTHER, so it certifies a file no t() call ever reaches — perfect symmetry, zero consumers, green forever. Grepping for t('tabs. found ZERO call sites and tabs.json was nearly recorded as dead. It is not: the only consumer builds the key dynamically (SemanticTreeLegend.vue:40, 'tabs.' + (tab.i18nKey || tab.id)), which no literal-prefix grep can see. The reverse error appeared in the same pass — regions. and options. matched only poster-regions.mjs and a JS options parameter. Static reachability is unavailable in both directions, so check:tabs-localized renders the labels and reads them. It asserts DIFFERENCE from English, not mere presence: te() falls back to the hardcoded English label, so "shows some text" passes on the exact failure being tested. Mutation-tested three ways — missing catalog FAILs, an all-English catalog FAILs (first draft PASSed it, taking a per-pair exemption seven times), one legitimate collision still passes with a note. Both i18n gates now run in gates:post; neither was wired into the build before. Also fixed, found by the build rather than sought: - check-i18n-parity hardcoded an absolute path, so the studio copy silently graded wt-packet's locales and reported PASS on a tree it never read. Now repo-relative. That exposed the studio's own locale tree as a strict subset, 103 keys behind including buttons.json:share — the very orphan this gate's header says it was written to catch, reappeared unseen in a second repo. Synced forward: zero studio-only keys, zero text conflicts, lossless. - index.json still declared field-access-visas with rows:1146, a leftover from the commit that removed that table as private. The generator already filters private tables; the committed artifact predated the filter. Removing the declaration also removes the row-count leak. Copying the file in would have reopened the leak. - check:sfc-parse needs an installed node_modules and is the first pre-gate to fail without one, so a dependency-less worktree reads as a parse error. Documented, with the reason switching it to bun only appears to fix it.	2026-09-24 06:23:30 +00:00