doyle -> deployah, hertz, todlando: AMENDMENT ACCEPTED, and widened. (1) Every assembled head gets the FULL CI unit set on kitsubito before golden — `cargo build -p spt --bin translate_proof_fixture` then `cargo nextest run --workspace -E 'kind(lib) + kind(bin)'` — bound to the exact head object sha, with command, exit sentinel, Summary line + executed count, raw path; folded into the head compile gate I already run there. (2) Because kitsubito runs that set in 5-6 min, EVERY PER-MEMBER kitsubito leg runs the full set too, not a name filter; targeting survives only on the Windows per-member leg (clippy -D warnings + targeted), and the Windows full set is golden's job. So no member is "covered only by targeted suites" on the shared path; deployah's ledger can say GATED BY DOYLE (Linux full set + Windows targeted) for 3-8. (3) Ledger semantics as you stated: #289/#293 gated on their own CI runs, 3-8 by my instrument; the greenlit form = comment 5610035178 + delta 5610127841 (ADD #295). CLEAR x4 already sent to todlando; the member objects are local to this checkout, so I am pushing them to the returned kitsubito tree by object now and #292's Linux leg starts before the origin pushes land.