routine-eligibility fails once on every push: the routine marker cannot name a head before it exists #5189

Work level: Delivery · Track: Follow-up · Intended Status: Ready

Owner

Root/fdev retains integration, typed metadata, native effects and acceptance. /root/archive5170 is the accountable full Delivery owner for the existing source and applicable receiver adoption; /root/context5276 remains independent reviewer. Existing repository owners and original reservations are preserved.

Done when

A push to a routine PR does not produce a guaranteed routine-eligibility failure plus an extra body-edit run. For example, routine-eligibility accepts a marker whose head= names the push's parent when the push event's before equals it and the body's other fields are unchanged, then requires a rebind before merge. Or the marker binding moves out of the body into a bot-written check or comment keyed by head. Required-context and settlement semantics stay unchanged, and controls cover a stale marker from an unrelated head, a rebind and a forged marker.

Current deliverable

Canonical5191 source and all nine existing receiver five-file adoptions are verified, including byte/mode equality with published120 and an actual Templates synchronize provisional-pass warning. The original5191 review explicitly retained F3: deepening could refresh main after observed_base was captured. That residual is now repaired in independently reviewed LOCAL ee3b2027b4a3672f7913be8bbc3676757be4012a/treefab01b75710f5e7f605ecc4400768259d227c0fe, two paths over846. All17 push-parent and23 moved-base controls pass; real shallow-transport and remove-only-refresh mutant prove the fix.

Next action

Root sequences the reviewed F3 canonical source component, coherent publication and applicable new receiver joins through the existing scripts/routine-closure.py route. Retain same full owner/reviewer and current successful old components. Do not recreate already delivered adoptions, use first-install on existing files, or alter sealed historical manifests.

Blocked on

New corrected source/publication and receiver effects wait Root integration and hosted capacity; M1 holds Hub846. Three maintained stale-pin findings are classified as sealed historical/pre-adoption references, not live five-file drift; preserve their bytes and checker limitations.

Acceptance evidence

Canonical source #5191 and existing adoptions under5202/5213 remain accepted components. Actual Templates857 synchronize41913778549/a1 shows the intended provisional warning without a new CI run. Local F3ee3b2027 independent SOURCEPASS with40 focused controls; original review6558535343 and all original runs/attempts retained. Full5189 remains open for corrected source, publication and applicable receiver qualification. Refs #5097, Refs #5182.