Declare the region-paint gate as on-demand while it is half-adopted
Registering a check that no chain runs turns the orphan guard red: it fails any gate-shaped script that nothing reaches and nobody declared. That guard is right, and it caught this the round after it was built -- "registered but not chained" is precisely the state it exists to force into the open, and it was the state this branch was in. The gate cannot be chained yet without holding the shared run red over another plugin owner's unlanded work: it asserts the regions idle paint has one source, and only one of the two maps has adopted the library export so far. So declare it on demand with the reason, in the file that requires one. The entry is temporary and says so. It is deleted in the same landing that chains the gate, once the second map's half lands. Verified the declaration satisfies the guard rather than silences it: blanking the reason makes the guard fail again, naming this entry and the file it is in.
This commit is contained in:
parent
ff27745032
commit
f331c962c0
1 changed files with 2 additions and 1 deletions
|
|
@ -7,6 +7,7 @@
|
|||
"check:composite": "rebuilds every bundle with vite to compare its bytes, minutes long by design; on every landing the precondition's fresh step rebuilds the composites that landing reaches",
|
||||
"check:hardcoded-english": "report-only while its findings are triaged (97 user-visible English strings on 2026-09-29); chaining it now would hold every gate red. Its :self-test IS chained, so the matcher stays proven",
|
||||
"check:shot-fonts": "checks that the MACHINE taking README screenshots can render emoji (fc-list): a property of that box, not of the product, so it runs before a screenshot session, not in the gates",
|
||||
"check:coverage-consistent": "the full run includes clause L, the age of the oldest link verification (45 days), which depends on the CALENDAR: chained, it would turn gates red on a date (first 2026-11-08) with no code change. Run it with the link re-verification; every other clause runs in gates:pre as check:coverage-consistent:chained"
|
||||
"check:coverage-consistent": "the full run includes clause L, the age of the oldest link verification (45 days), which depends on the CALENDAR: chained, it would turn gates red on a date (first 2026-11-08) with no code change. Run it with the link re-verification; every other clause runs in gates:pre as check:coverage-consistent:chained",
|
||||
"check:region-paint-single-source": "TEMPORARY, remove when chained. Asserts the regions idle paint expression has one source in the library rather than a copy per map. Half-adopted on purpose: research-map.vue took the library export (2026-09-29), countries-map.vue is the other plugin owner's file and its two assertions are red until they land their half. Chaining it now would hold gates:post red for everyone over another agent's unlanded work. It joins gates:post in the SAME landing as that half, and this entry is deleted in that commit"
|
||||
}
|
||||
}
|
||||
|
|
|
|||
Loading…
Reference in a new issue