mirror of
https://github.com/DeusData/codebase-memory-mcp.git
synced 2026-11-11 09:25:35 +08:00
Martin VogelandClaude Fable 5.1
c572ddc4f3
A single agent configuration the editors refuse to touch (the reporter's ~/.cursor/mcp.json was a symlink into a dotfiles checkout) aborted the uninstall activation BEFORE index and binary removal. `uninstall -y` exited 1 and left a 300 MB executable plus the whole cache behind — the data-loss half of #1954 — while the transcript still read "removed". Agent-config failures are now collected instead of gating: every cleanup runs, the indexes and the executable go, and the command ends with one list of the files that could not be cleaned (agent, operation, path, observed target) and a non-zero exit. The existing per-error stderr line is unchanged. Two tests encoded the old hostage contract ("binary must survive failed cleanup") and move to the new one. The new test drives `uninstall -y` against a sandbox HOME with a dangling ~/.cursor/mcp.json link and asserts binary + index gone, exit non-zero, and the file named on stderr; on main it fails at ASSERT(binary_gone). (#1954) Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>