docs: refresh banner with Gemini brand palette and Claude/Gemini lockup

[elkaix]

Banner: Gemini blue→violet→red gradient on model badges/chips, new sparkle glyph, Claude ⇄ Gemini lockup, v2.0.0 pill, stat-strip gradient baseline. README: colorful shields + Claude Code / Gemini / MCP brand badges. Verified: SVG XML valid, rendered at 1280×480 in headless Chrome, prettier clean.

Summary by CodeRabbit

• Documentation
  • Updated README badges with service-specific colors for improved clarity.
  • Added badges linking to Gemini 3.7 Flash and MCP resources.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 5f74ce18-2c20-4246-b27c-dd55bf21ec3c

📥 Commits

Reviewing files that changed from the base of the PR and between a27c4cb and 927a802.

⛔ Files ignored due to path filters (1)

• assets/banner.svg is excluded by !**/*.svg

📒 Files selected for processing (1)

• README.md

---

📝 Walkthrough

Walkthrough

The README badge row now uses service-specific colors for existing badges and includes Claude Code, Gemini 3.7 Flash, and MCP badges with links.

Changes

README badge updates

Layer / File(s)	Summary
Badge presentation updates README.md	Existing CI, npm, Node.js, and license badges use distinct colors. Claude Code, Gemini 3.7 Flash, and MCP badges were added.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/banner-gemini-refresh

---

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

[greptile-apps]

Greptile Summary

This change refreshes the README and visual branding while updating the package’s default delegation model and fallback chains to the Gemini 3.7 family. A controlled MCP client/server run invoked every exposed tool and recorded its runner arguments: each tool selected the intended available model, and follow-up sessions continued without adding a model override. The repository regression suite also completed successfully with 73 passing tests and 1 skipped test. No defects were found.

Confidence Score: 5/5

The updated model-routing behavior and MCP tool exposure operated as intended in controlled runtime execution.

All exposed tools were exercised against a controlled model listing, their actual runner model arguments matched the updated routing configuration, baseline behavior was compared against main, and the repository test suite passed.

Files Needing Attention: No files need follow-up attention.

T-Rex Logs

What T-Rex did

• Ran an in-memory MCP client/server contract against HEAD with controlled model listings and mocked runner dependencies, and verified that all tools were exposed and every routing assertion passed.
• Compared HEAD against the main baseline by running the same contract in a detached worktree; the baseline selected earlier 3.5 Flash fallback models while HEAD used the updated 3.7 routes.
• Ran the repository regression suite and observed that 73 tests passed and 1 test was skipped.
• Verified in a follow-up pass that HEAD and baseline executions exited with code 0 and that the HEAD routing contract and the baseline routing contract both exposed MCP tools with routing assertions passing, with the repository regression suite again showing 73 tests passed and 1 skipped.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "docs: refresh banner with Gemini brand p..." | Re-trigger Greptile}