fix(setup): stop remaining uninstall removals after a client fails

A configuration that passes the preflight can still fail when uninstall
rereads it to edit, for example when it changes concurrently. Rereading
keeps that edit from overwriting the newer file; stopping at the failure
keeps later clients, the skill, and REA data from being removed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/installation.md

@@ -574,7 +574,8 @@ rea uninstall --purge-data
 Uninstall preserves Hopper, Node.js, Evidence files, captures, unrelated skills
 and other MCP servers. Purging removes only REA's cache and state under
 `~/.rea`. A client configuration that is malformed, unreadable, or at an unsafe
-path stops the operation before anything is removed; a purge path that is a
+path stops the operation before anything is removed, and a client that fails
+while being updated stops the remaining removals. A purge path that is a
 symbolic link is retained and reported rather than followed. See the
 [CLI guide](cli.md#output-and-exit-status) for exit statuses.