From Codex P1 on PR #665 (held autopilot tier): SKILL.md autopilot §3's merge command is not cross-wired to the new tier flags, so an ENABLED config could merge via the old gate path — a coherence gap in the enabled path. Not exploitable today: the tier ships disabled-by-default and #665 is operator-held; the gap only matters at activation.
Per the defer-forbidden backstop clause this is therefore a GATE-OFF FLIP PRECONDITION (joins the #476 precondition list; #642 precedent): the flip does not happen until §3 is wired to the tier flags AND the concrete second-account gh pr review --approve mechanic is specified.
Design fork to resolve first (escalated by the implementer — the fix collides with the 499/500 skill-quality line cap and the skill-contract test pins §3's prose):
- (a) raise the line cap for this skill (skill-quality budget decision), or
- (b) restructure: move the merge-command mechanics to a reference file §3 points at (no cap pressure, one more indirection).
RECOMMENDED: (b) — reference-file restructure; consistent with the plugin's existing reference/ pattern and avoids a cap exception precedent. Operator may override.
Origin thread on #665; implementer classification reply there. [Control tower routing; flip-precondition designation is Class B decide-and-log with operator veto window]
From Codex P1 on PR #665 (held autopilot tier): SKILL.md autopilot §3's merge command is not cross-wired to the new tier flags, so an ENABLED config could merge via the old gate path — a coherence gap in the enabled path. Not exploitable today: the tier ships disabled-by-default and #665 is operator-held; the gap only matters at activation.
Per the defer-forbidden backstop clause this is therefore a GATE-OFF FLIP PRECONDITION (joins the #476 precondition list; #642 precedent): the flip does not happen until §3 is wired to the tier flags AND the concrete second-account
gh pr review --approvemechanic is specified.Design fork to resolve first (escalated by the implementer — the fix collides with the 499/500 skill-quality line cap and the skill-contract test pins §3's prose):
RECOMMENDED: (b) — reference-file restructure; consistent with the plugin's existing reference/ pattern and avoids a cap exception precedent. Operator may override.
Origin thread on #665; implementer classification reply there. [Control tower routing; flip-precondition designation is Class B decide-and-log with operator veto window]