docs: mention Zoo Code as the Roo Code community successor

[taltas]

Roo Code (RooCodeInc/Roo-Code) was archived / shut down on May 15, 2026 and is now
read-only. Its own repo notes the community successor here:
https://github.com/RooCodeInc/Roo-Code#disclaimer

Zoo Code is the community-maintained fork that continues where Roo Code left off:

• Site: https://zoocode.dev/
• Source: https://github.com/Zoo-Code-Org/Zoo-Code/

This PR adds a Zoo Code reference alongside the existing Roo Code mention in the README so
readers looking for a maintained alternative can find it.

Do you min updating the about section in your repo as well to include Zoo Code?

Summary by CodeRabbit

• Documentation
  • Updated the supported CLI and tool list for Splitrail’s real-time token usage tracker.
  • Added Zoo Code and Kilo Code while retaining the VS Code extension and CLI support details.

[coderabbitai]

📝 Walkthrough

Walkthrough

The README’s real-time token usage tracker tooling list now includes Zoo Code while retaining the existing tools and “VS Code extension + CLI” description.

Changes

Tooling documentation

Layer / File(s)	Summary
Supported tools list README.md	Adds Zoo Code to the listed Cline, Roo Code, and Kilo Code integrations while preserving the existing descriptor.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: bl-ue

Poem

A rabbit hops through README lines,
Adding Zoo Code to the signs.
Cline and Roo still share the way,
Kilo joins the list today.
“VS Code plus CLI!” we say.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the docs update about Zoo Code as the successor to Roo Code.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 36: Update the companion README at vscode-splitrail/README.md to match
the supported-tool list in the root README, including Zoo Code and preserving
the existing Cline, Roo Code, and Kilo Code entries.
- Line 36: Update the README attribution entry for Zoo Code to identify it as
the community-maintained successor to Roo Code, retain its repository link, and
add the official Zoo Code website link. Include Roo Code’s May 15, 2026 archive
context as part of the attribution wording.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c68ac3cb-d643-4270-80f0-e3995555f155

📥 Commits

Reviewing files that changed from the base of the PR and between 9c8b14a and c3da62d.

📒 Files selected for processing (1)

• README.md

[mike1858]

@taltas Thank you very much for this PR!  Architecturally Zoo Code support was there but we didn't look for Zoo-specific file names yet, which I fixed in #205.  I'll merge this PR and update the repo description.