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.
f331c962c0