* feat(setup): give five mcp-add clients one client-table row
Cline VS Code extension, Kiro, Mastra Code, Zed and Amp move from
registration-only catalog entries to rows in the client table. rea mcp add
projects those rows, so doctor, update and uninstall now inspect, refresh
and remove what it wrote, and setup offers each client when detected.
Refs #7181
* refactor(setup): keep FreeBuff's comment on its declaration
The client helpers added for the folded mcp-add clients were inserted
between FreeBuff's profile-directory comment and its declaration. Move
them above it, and drop an import the folded locations no longer use.
* test(setup): refresh an older mcp-add registration through setup
Address review: seed each folded client with an older REA-owned package
runner launcher, then check that doctor reports it stale, update selects
it, setup plans and applies the update, and doctor then reads the
current launcher.
* fix(setup): register Amp in settings.jsonc when that is its settings file (#10717)
Amp reads ~/.config/amp/settings.json or settings.jsonc. REA always
used settings.json, creating a second file beside an existing
settings.jsonc. Use settings.jsonc when it is the only file, and refuse
when both exist because Amp does not document which one it reads.
* feat(setup): manage Cline in VS Code Insiders, VSCodium, Cursor and Windsurf (#10729)
* feat(setup): manage Cline in VS Code Insiders, VSCodium, Cursor and Windsurf
The Cline extension keeps its MCP settings in the global storage of
whichever editor runs it. REA resolved only VS Code's, so a Cline in
another editor was never configured, inspected or cleaned. Add one
client-table row per editor, resolved through the shared Code-OSS user
data rule, and detected where that editor's Cline settings exist.
* test(setup): cover VSCODE_PORTABLE for Cline's editor hosts
Address review: VSCODE_PORTABLE moves only VS Code's own storage, so the other editors keep their settings path; and the older-release note now says which hosts mcp add could register before.
* fix(setup): find a Linux Flatpak Zed's configuration (#10721)
* fix(setup): find a Linux Flatpak Zed's configuration
Zed's config_dir honors FLATPAK_XDG_CONFIG_HOME first, and a Flathub Zed
reads ~/.var/app/dev.zed.Zed/config/zed inside its sandbox. REA always
wrote ~/.config/zed, which that Zed never reads. Honor the override, use
the sandbox folder when it is the only one, and refuse when both a
native and a Flatpak configuration exist.
* fix(setup): treat an XDG_CONFIG_HOME naming the Flatpak folder as one Zed folder
* fix(setup): treat linked native and Flatpak Zed folders as one configuration
* test(setup): expect doctor to report the Amp registration mcp add wrote
Configuration roots read from XDG_CONFIG_HOME, VSCODE_APPDATA and
VSCODE_PORTABLE now come from one module whose functions reproduce a named
reader: xdg-basedir (OpenCode, Kilo), the XDG rule used by Rust dirs and
etcetera (Zed, Goose), and VS Code's getUserDataPath. mcp add's ad hoc
platformPaths() is removed. Zed no longer takes a relative XDG_CONFIG_HOME
that Zed ignores, and the Cline extension and Kilo's VS Code marker follow
VS Code's portable and VSCODE_APPDATA selection.