Sunset Roo Code client integration

Background

The Roo Code VS Code extension has announced it is shutting down. The repo is being archived and the last VS Code extension release shipped on May 15, 2026, after which the extension will no longer be maintained. From the announcement:

We're archiving the Roo Code repo, refunding any unused balances, and making the last extension release on May 15th. If you still need an extension, Cline has incorporated many of the Roo Code features and will welcome you with open arms.

ToolHive already ships a first-class Cline integration (thv client register cline), making migration straightforward for affected users.

ToolHive currently ships a full first-class integration for Roo Code (roo-code), including:

• Client registration and config file management (pkg/client/config.go, ClientApp = "roo-code")
• MCP server config written to rooveterinaryinc.roo-cline/settings/mcp_settings.json
• Skills support (~/.roo/skills, .roo/skills)
• E2E tests, API discovery, and generated Swagger/OpenAPI docs

Since the extension is archived and no longer maintained, keeping this integration active creates a misleading signal that the client is supported and functional. We should deprecate and eventually remove it.

Proposed sunset plan

Phase 1 — Deprecation warning (next release)

Print a deprecation warning to stderr whenever a user runs thv client register roo-code or any command that touches the roo-code client:

Warning: The Roo Code VS Code extension has been discontinued (last release May 15, 2026)
and its repository has been archived. Support for this client will be removed in a future
ToolHive release. The Roo Code team recommends migrating to Cline:
  thv client register cline

Update the CLI docs and README to mark roo-code as deprecated and point to cline.

Phase 2 — Removal (two minor releases after Phase 1)

Remove all code and test coverage for roo-code:

Acceptance criteria

• Phase 1: thv client register roo-code prints a visible deprecation warning to stderr pointing users to thv client register cline
• Phase 1: Docs/README note that roo-code is deprecated, link to the Cline integration, and state the planned removal version
• Phase 2: All references to RooCode / roo-code removed from non-generated source files
• Phase 2: All generated docs regenerated (task docs) after removal
• Phase 2: task test and task test-e2e pass with no roo-code references

Start in pkg/client/config.go alongside the existing Cline integration, then inspect the listed client, configuration, E2E, and generated documentation files. Run the relevant client tests and task docs to understand the current generated outputs. Done means the deprecation behavior and migration documentation are covered, or the planned removal leaves no non-generated Roo Code references and task test and task test-e2e pass.