[mashfromband]

PassShareの回収済み検査SDKを既存safe-deleteで退避できるようにします。元の所有記録が一致する3rootだけに限定し、rustup相対link・Windows内部junction・全inventory/内容を移動前後で検証します。一般planのreparse/Git/外部hardlink保護は維持します。

Go race/vet/buildと合成fixtureの回帰検査に成功しました。実物3rootの読み取りinspectも成功し、内容量は合計2,813,105,600bytesです。別モデルレビューとCI成功後に配備・退避します。退避は削除量や空き増加として報告しません。

---

Note

Medium Risk
Bounded to three fixed receipts but performs large same-drive moves with complex Windows reparse/junction rules; mis-invocation or partial failure can leave dual locations until manual follow-up.

Overview
Adds a ToDo3004 path in safe-delete to preserve (not delete) three PassShare SDK inspection roots whose ownership receipts match fixed integrity hashes.

New inspect-sdk --id runs read-only collection/evidence checks and reports measured inventory; quarantine --id --reason sdk-links moves the tree to same-drive 削除希望 after fixture lock + stopped CC-PSW-fixture service checks. Quarantine uses a dedicated sdkScope that snapshots metadata and SHA256 into preservation.json, validates before/after move, and allows only the 13 runtime/sdk/bootstrap/bin → rustup.exe relative symlinks plus the internal INetCache/Content.IE5 junction (raw reparse hash + absolute target preserved, not walked). rawIdentity and optional Target on preservation entries support that scanner; ordinary plan / default walks still reject reparse points.

Docs (README, docs/todo3004-sdk-recovery.md) describe scope and remaining rollout steps. Windows tests cover link/junction preservation, external links/Git/secrets rejection, tamper detection, and receipt forgery.

^{Reviewed by Cursor Bugbot for commit 7c261a1. 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: ee41ffe3-e686-465e-b969-1e1e7d246dcc)

[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: 11042053-b5e1-41ac-a7e9-256626a7e2c9)