[Maintenance] Run /instruction-placement:migrate cutover-check (reopened after #5160 false close)

[cursor]

Context

Continuation of #4281, which was closed by mistake when #5160 merged because its PR body carried a "Do not close" line, which GitHub reads as a closing keyword. #4281 is a standing monthly fleet tracker; one canary cycle does not complete cutover.

Condition 3 grades only on a logged-in host and was [MET] on 2026-09-29 (latest table below). Shim removal waits on the owner decisions on #4282 (CI canary) and #4283, and on a recheck across the ten in-scope repos.

Recurring obligation

Same as #4281 (both stay open until the owner picks the canonical tracker):

• Run /instruction-placement:migrate cutover-check across the ten in-scope repos on the monthly cadence in .github/recurring-schedule.json, and comment the per-condition table here.
• Also run after any Claude Code release that touches AGENTS.md handling.
• When every condition reports met, shim removal is unblocked via remove-shims with operator confirmation.

Latest known table (2026-09-29, Claude Code 2.1.284, ten in-scope repos)

Condition	Verdict
1 native reading off remote flag	MET
2 action pins and CI canary	MET on pin arithmetic, provisional: CI-canary component pending the owner decision on #4282
3 lone AGENTS.md canary	MET (logged-in host)
4 path detection	MET

Earlier table (2026-09-28, this marketplace only, from #5160): condition 3 was UNREACH (loggedIn: false).

Acceptance criteria

These describe one cycle of the recurring item, not a one-time completion; they reset each cycle.

• /instruction-placement:migrate cutover-check has been run at least once since this item was last checked, with its per-condition met/unmet/unreachable output recorded in a comment on this issue.
• The check has also been run after any Claude Code release whose changelog, per /claude-ops:changelog, touches AGENTS.md or instruction-file loading.

[kyle-sexton]

This was generated by AI during triage.

Triage: human-gated

Summary: Standing recurring tracker (recurring-schedule id agents-md-cutover-check), not a defect. Keep open; do not close on a partial grade (#4281 was a false close).

Open question: None: condition 3 (UNREACH) needs a logged-in Claude, which an agent lane does not have.

Evidence that settles it: a monthly run by the operator, and after AGENTS.md-related Claude Code releases

RECOMMENDED: run /instruction-placement:migrate cutover-check, comment the table, and unblock remove-shims once all four conditions are MET.

[kyle-sexton]

From the 2026-09-29 audit of the Cursor run. Owner authorization for the audit fixes: Claude Code session, 2026-09-29. This is a decision packet; nothing has been decided.

Decision needed: which issue is the canonical monthly cutover-check tracker

Context. #4281 is the original: ten-repository scope, per-cycle acceptance criteria, history from 2026-09-21/22, and the recurring + cadence: monthly labels. It was falsely closed on 2026-09-28 (#5160's "Do not close #4281" parsed as a closing keyword) and is now reopened. #5163 was filed by the agent after that false close. It has only needs-human and priority: low, has zero run comments, and ADR 0036 plus .github/recurring-schedule.json point to it. This cycle's per-condition table is posted on #4281 (#4281 (comment)), which closes the "run result not commented" gap for this cycle. The agent-authored PR text that called #4281 "open" is historical.

Options

• A) [Maintenance] Run /instruction-placement:migrate cutover-check #4281 canonical: close [Maintenance] Run /instruction-placement:migrate cutover-check (reopened after #5160 false close) #5163 as a duplicate with a pointer, repoint ADR 0036 and the schedule notes to [Maintenance] Run /instruction-placement:migrate cutover-check #4281.
• B) [Maintenance] Run /instruction-placement:migrate cutover-check (reopened after #5160 false close) #5163 canonical: add the recurring and cadence: monthly labels, inline the cycle acceptance criteria in its body, leave [Maintenance] Run /instruction-placement:migrate cutover-check #4281 closed with a pointer.
• C) Keep both open. Not recommended: two places to look, and the schedule row's close_previous behavior becomes ambiguous.

Recommended (AI recommendation, not a decision): A. Basis: #4281's body and labels are what the recurring-schedule mechanism and the monthly obligation text name; its history is in one place; the schedule row's notes already cite #4281 as first instance (.github/recurring-schedule.json:53).

Unblocks. The docs repoint (ADR 0036 and the schedule notes) and a single comment target for each monthly run.

Until you choose, this issue stays open with needs-human. I have not added recurring or cadence: monthly here, because the schedule row's close_previous would then treat both issues as live. Run comments go on #4281. Fix PR #5285 makes no choice.