From 6efb384261ea462064d83b692a9524d1700c7124 Mon Sep 17 00:00:00 2001 From: Beqa <91750923+BeqaKs@users.noreply.github.com> Date: Wed, 28 Oct 2026 01:16:13 +0400 Subject: [PATCH] docs(uninstall): clarify malformed shared config retention (#7507) Uninstall retains unverifiable shared registration storage without blocking REA-owned purge; document that exception beside the stop-before-removal rule. Fixes #7320 --- docs/client-configuration.md | 6 ++++++ docs/installation.md | 13 +++++++++---- 2 files changed, 15 insertions(+), 4 deletions(-) diff --git a/docs/client-configuration.md b/docs/client-configuration.md index 420b76273b..790e5a463c 100644 --- a/docs/client-configuration.md +++ b/docs/client-configuration.md @@ -636,6 +636,12 @@ boundaries. FreeBuff MCP loading and skill discovery have not been verified with an installed native FreeBuff client/version; filesystem tests cover REA's editing, discovery, and ownership behavior only. Automatic applicability requires the FreeBuff profile directory even when the shared MCP file exists. +When uninstall cannot establish FreeBuff or another shared-storage reader from +product discovery, a malformed or unreadable shared MCP file is retained +unchanged and does not stop other REA removals, including `--purge-data`. When +FreeBuff or ZCode product applicability is established or unresolved, the same +malformed shared file stops uninstall before removals. See +[Diagnose, update, and remove](installation.md#diagnose-update-and-remove). FreeBuff setup support requires `rea-agents@6.8.0` or later. Older versions reject `rea setup --client freebuff` as an unsupported client. See the diff --git a/docs/installation.md b/docs/installation.md index 2bd90427db..fa700a24e0 100644 --- a/docs/installation.md +++ b/docs/installation.md @@ -449,10 +449,15 @@ Lexically equivalent spellings of that default directory, including a trailing separator, a `.` segment, or a repeated separator, share its purge result. The comparison preserves POSIX `..` traversal and literal backslashes. A client configuration that is malformed, unreadable, or at an unsafe -path stops the operation before anything is removed, and a client that fails -while being updated stops the remaining removals. Uninstall reports each -candidate `configuration_path` with its outcome. A client with multiple files -keeps their individual `actions` alongside its aggregate status and detail, +path stops the operation before anything is removed when that client's +product applicability is established or unresolved. Shared registration +storage such as `~/.agents/mcp.json` whose product cannot be established +(for example when FreeBuff and ZCode discovery directories are absent) is +retained unchanged and does not block other REA removals, including cache +and state deletion with `--purge-data`. A client that fails while being +updated stops the remaining removals. Uninstall reports each candidate +`configuration_path` with its outcome. A client with multiple files keeps +their individual `actions` alongside its aggregate status and detail, including earlier removals when a later file fails. The paths name the discovered configuration candidates, not resolved physical file identities. For JSON clients, uninstall removes every repeated `rea` member in the effective