doxa-life/doxa-maps
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Delete the "Show on map does not select the zone" exemption — it outlived its defect

Browse source 
regions' headless sweep reported interop row 10 as a KNOWN DEFECT owned by me, while rega had proven the
same path working on both engines. dx-shepherd asked which was true. It is the register that is wrong.

★ PROVEN BEFORE DELETING, because "someone said it is fixed" is exactly how a stale exemption becomes a
hidden live one. Four independent checks on main:
  - THE ENTRY'S OWN CLAIM IS FALSE. It said onShowOnMap "answers with go('map') only; it never re-dispatches
    doxa:select-zone". It does — and it also writes a `select-zone` ATTRIBUTE first, so a pane that mounts
    later still reads the request. The attribute is the stronger half and the entry does not know it exists.
  - THE CITED COORDINATE IS WRONG. upg-100-mfe.vue:143 is an unrelated comment about tab rendering; the
    handler is at :274. A file:line in a register ages into a false claim the moment anyone edits above it —
    the third time this cycle a line number has drifted into fiction (gospel's engine offender moved
    1490→1505→1509 the same way).
  - BOTH FIXES ARE ANCESTORS OF main: 12a64702 (release the retained request on success — the FIRST press
    was losing the zone) and 67e9ede5 (the wall clears its memory when its pane goes inert).
  - The receiving side still registers its listener, and rega proved it end to end at 810ffa26.

⚠ AND THE REGISTER'S OWN CONTRACT SAYS THIS SHOULD NOT HAVE HAPPENED. Six lines above it:
"DELETED in the same commit as the owner's fix so main never carries a stale exemption or a red gate on
someone else's bug." The entry outlived its defect by three landings because the deletion was not part of
the fix. A convention that depends on remembering is not a convention; the MAPBOX_KNOWN block right below
records the same rule being followed correctly, which is why that one is empty and honest.

The block stays with the reasoning in it rather than being emptied silently, so the next reader sees what
was checked and why — and the printing machinery is untouched for the next real entry.
This commit is contained in:
Doxa Maps 2026-09-28 02:33:09 +00:00
parent 2e92a05b30
commit daa6ee6eda
1 changed files with 15 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
internal/check-research-gallery-embed.mjs
View file

@ -71,10 +71,21 @@ const NEIGHBOUR_KNOWN = {
}
// KNOWN, ROUTED gaps in a composite's internal link (not measurable as pass/fail yet: no DOM hook).
const LINKED_KNOWN = {
// upg-100-mfe.vue:143-148 answers `doxa-upg-100-list:show-on-map` with go('map') only; it never
// re-dispatches `doxa:select-zone` (the event upg-100-list.vue:1366-1381 isolates a zone on), so
// "Show on map" scrolls to the map without selecting that list's zone. Routed 2026-09-25.
'upg-100: "Show on map" does not select the zone on the map': 'upg100-plugin (upg-100-mfe.vue:143 re-dispatch doxa:select-zone)',
// EMPTY ON PURPOSE. The one entry — upg-100's "Show on map" not selecting the zone, routed 2026-09-25 —
// is DELETED as STALE, not waived. It outlived its defect by three landings, and the gate's own contract
// above says an exemption is deleted in the SAME commit as the fix; that did not happen here, so the
// register red-flagged a bug that was already gone.
// ⚠ PROVEN BEFORE DELETING, because "someone said it is fixed" is how a stale exemption becomes a hidden
// live one. Measured on main:
// - the entry claimed onShowOnMap "answers with go('map') only; it never re-dispatches
// doxa:select-zone". It does: upg-100-mfe.vue dispatches that event AND sets a `select-zone`
// attribute first, so a pane that mounts later still reads the request.
// - the cited coordinate upg-100-mfe.vue:143 is an unrelated comment about tab rendering; the handler
// is at :274. A file: line in a register ages into a false claim the moment anyone edits above it.
// - both fixes are ancestors of main: 12a64702 (release the retained request on success — the FIRST
// press was losing the zone) and 67e9ede5 (the wall clears its memory when its pane goes inert).
// - the receiving side still registers its listener.
// - rega proved it end to end on BOTH engines at 810ffa26.
}
const MAPBOX_KNOWN = {
// pplr-data-maps (new Experimental bundle, exp-shepherd) loads the Mapbox GEOCODER script even when