[mashfromband]

万世紀の通常Prepareが拒否される元880の未完工程を、2026-10-15の本人直接指示から選びました。新担当2637を実装・Cargo/Civ6受入・別モデル・CI・PR/通常反映を行う指示付きで登録しています。

今回の新工程に限り、元2636/新2637/原880の正確な指示書と独立したSHA256、登録先、物理パス、正確なorigin、専用worktreeと枝、期限を確認するGo検証を追加します。原保護名簿があるときは優先し、元192項目の状態や未完依存を変更しません。原名簿は未復旧であり、未知のフォルダー・脱出リンク・別工程は許可しません。

検証: repair-guardのGo test/vet成功。実Git remoteとGitHub APIのnameWithOwnerを照合済み。別モデルレビュー2638と必要CIは実結果を確認後に反映します。登録や実装だけを製品の受入成功と扱いません。Cargo・Civ6・GPUをこの親担当では起動していません。

---

Note

High Risk
Changes security-sensitive repair admission and scheduler launch gates for a specific production repo; misconfiguration could allow or block the wrong work outside the intended window.

Overview
Adds a finite, time-boxed repair path for ToDo 2637 on civ6-banseiki, tied to owner 2636 and legacy 880, without reopening the full client registry or changing other ledger rows.

Windows repair-guard gains nextWorkPathAllowed (wired from main_windows.go): it only allows the three anchored spec files, the registered repo root, the preserved 880 worktree, and the 2637 allocation tree/branch after checks on UTC window, ledger rows (2636/2637/880), compiled SHA256 of the spec bytes, physical path containment, exact origin, legacy protection, and optional creation of the planned worktree.

When client-projects.txt is missing, cc-scheduler treats civ6-banseiki + id 2637 like the existing repair-tool projects: dispatch depends on repair_scope_allowed (repair-guard), not a blanket allow. parity.rs asserts only 2637 / civ6-banseiki can launch under that guard and that a restored registry still blocks launch.

docs/next-work-2636.md records scope, hashes, and rollout notes for this one-off engineering unit.

^{Reviewed by Cursor Bugbot for commit c0a47e8. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 1e2fdb94-3679-47d5-b320-f4f68baedb72)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 36bd2bf0-16f6-4099-8b1d-540978a1855c)