mirror of
https://github.com/NanmiCoder/claude-code-haha.git
synced 2026-10-10 20:03:13 +08:00
程序员阿江(Relakkes)
38e2f11253
restoreAvailable conflated two questions: whether the files this checkpoint reports can be put back, and whether the checkpoint saw every file the turn touched. Any tool outside an 18-name allowlist — Bash, PowerShell, TaskCreate, every MCP tool — forced the second to false, and one such call anywhere from the target turn onward disabled undo for the whole range. In practice that is every real turn, so v0.5.3 shipped with undo effectively dead. Split the two. restoreAvailable now answers only the first question. The second becomes unverifiedChangeSources: tool names whose file effects the checkpoint could not capture. Undo stays available and restores exactly the files it lists, and the card, the confirmation, and the completion toast each name what it is leaving behind. An unrecognized tool now costs a warning instead of the feature. A transcript that cannot be read still blocks, because then even the reported file list may be wrong. Bash calls are classified against the existing read-only allowlist via a new recordedCommandIsReadOnly, which drops the sandbox/cwd checks that describe the live process rather than the replayed session. `git status` no longer warns at all, so the warning means something when it appears. Rewind also takes a mode. `conversation` skips the file restore entirely, so a turn whose files cannot be restored no longer costs the user the ability to back out of the prompt — matching how upstream keeps Restore conversation independent of Restore code. Files written by shell commands were never recoverable here; the checkpoint only ever covered the structured file tools. Reporting that is honest, and docs now say so.