Rule to encode
When a change in this repo removes or renames a surface that a pinned sibling checkout imports (today: the pinned objectui SHA that Console Pin Gate builds against), the removal must not merge alone. The same change series must update the sibling and bump the pin so the gate builds green at the moment of merge.
Why the rule is needed: the pin gate builds the pinned sibling against current main, so "retire the surface" and "leave the sibling untouched" cannot both hold — a retirement the pinned sibling still imports turns main red for every PR in the repo. A ruling that authorizes a removal therefore implicitly authorizes the sibling fix and pin bump as part of the same landing; a removal PR that cannot ship them does not ship.
Scope of work
- Encode the rule in
AGENTS.md (the retirement / PR-flow section) as one clear directive: a removal that breaks the pinned sibling ships together with the sibling fix and the pin bump, or it does not ship.
- If the retirement checklist or the spec-removal registry flow has a natural anchor for a pre-merge check ("does the pinned sibling import what you are removing?"), add the one line there; do not build new tooling in this card.
AGENTS.md is a governed face: draft PR, human merge, never flip ready.
Acceptance
- The directive exists in
AGENTS.md, findable from the section a retirement author actually reads.
- No behavior/tooling changes beyond the doc line(s).
Provenance
Maintainer ruling 2026-08-22 (decision-inbox digest with the skills seat, session_01ApyDuQY2fkunMCqXiqvBhR, accepted verbatim 「接受所有」): the p0 main-red pin-gate card #10856 was ruled A + C — fix the objectui side first, and adopt this rule. This card is the C half, commissioned to the skills seat by that ruling. Background refs (non-operative): retirement PR #10695, Console Pin Gate failure on queue build 32489707921.
Rule to encode
When a change in this repo removes or renames a surface that a pinned sibling checkout imports (today: the pinned objectui SHA that
Console Pin Gatebuilds against), the removal must not merge alone. The same change series must update the sibling and bump the pin so the gate builds green at the moment of merge.Why the rule is needed: the pin gate builds the pinned sibling against current main, so "retire the surface" and "leave the sibling untouched" cannot both hold — a retirement the pinned sibling still imports turns main red for every PR in the repo. A ruling that authorizes a removal therefore implicitly authorizes the sibling fix and pin bump as part of the same landing; a removal PR that cannot ship them does not ship.
Scope of work
AGENTS.md(the retirement / PR-flow section) as one clear directive: a removal that breaks the pinned sibling ships together with the sibling fix and the pin bump, or it does not ship.AGENTS.mdis a governed face: draft PR, human merge, never flip ready.Acceptance
AGENTS.md, findable from the section a retirement author actually reads.Provenance
Maintainer ruling 2026-08-22 (decision-inbox digest with the skills seat,
session_01ApyDuQY2fkunMCqXiqvBhR, accepted verbatim 「接受所有」): the p0 main-red pin-gate card #10856 was ruled A + C — fix the objectui side first, and adopt this rule. This card is the C half, commissioned to the skills seat by that ruling. Background refs (non-operative): retirement PR #10695,Console Pin Gatefailure on queue build 32489707921.