feat!: release v2.0.0 — default to Gemini 3.7 Flash (High)

[elkaix]

What changed

• Default model and all tool routing chains bumped Gemini 3.6 Flash → Gemini 3.7 Flash (High) (src/config.ts, src/tools.ts, src/server.ts)
• README refresh: benchmark highlights, MCP stack guide, updated routing tables
• Banner redesign + new assets/benchmarks.svg
• Version bump to 2.0.0 (package.json, server.json)

Why

Gemini 3.7 Flash (High) is now the strongest available default for delegation workloads; this is a breaking change to default routing behavior, hence the major bump.

How verified

npm run format:check, npm run typecheck, npm test (73 passed), npm run build — all green locally.

Summary by CodeRabbit

• New Features
  • Updated the default delegated model and fallback routing to Gemini 3.7 Flash (High).
  • Improved model-routing coverage across analysis, search, lookup, review, and delegation workflows.
• Documentation
  • Expanded setup, configuration, benchmarking, context, MCP, routing, and fallback documentation.
• Chores
  • Released version 2.0.0 with updated model defaults and routing behavior.
  • Updated validation coverage for model parsing, failover, cooldowns, caching, and exhaustion scenarios.

[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: 7833e87f-7dae-43c4-a899-0b666857d1ff

📥 Commits

Reviewing files that changed from the base of the PR and between d8089f3 and 33284f8.

⛔ Files ignored due to path filters (3)

• assets/banner.svg is excluded by !**/*.svg
• assets/benchmarks.svg is excluded by !**/*.svg
• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (9)

• README.md
• package.json
• server.json
• src/config.ts
• src/server.ts
• src/tools.ts
• test/config.test.ts
• test/models.test.ts
• test/server.test.ts

---

📝 Walkthrough

Walkthrough

The project now defaults to Gemini 3.7 Flash, updates all delegated tool routing chains, refreshes related tests and documentation, and increments package and server versions to 2.0.0.

Changes

Gemini 3.7 model migration

Layer / File(s)	Summary
Default model and tool routing src/config.ts, src/tools.ts, README.md	Configuration defaults, tool fallback chains, routing examples, and documented fallback values now use Gemini 3.7 Flash.
Model selection test updates test/config.test.ts, test/models.test.ts, test/server.test.ts	Model parsing, resolution, caching, concurrency, delegation, failover, cooldown, and exhaustion tests now use Gemini 3.7 Flash.
Release metadata package.json, server.json, src/server.ts	Package and server versions now report 2.0.0.

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

Possibly related PRs

• PyModel/claude-agy-mcp#14: Updates release versions in the same package and server metadata files.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/release-v2.0.0

---

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

[greptile-apps]

Greptile Summary

This release updates the MCP bridge to version 2.0.0, changes the default and tool-specific routing preferences to Gemini 3.7 Flash, and refreshes documentation and visual assets.

The routing behavior was exercised with Gemini 3.7 absent from the available-model listing. When Gemini 3.5 Flash was available, the bridge selected it explicitly. When no configured model was available, it omitted --model and reported use of agy's default. This disproves the concern that the new preference would be passed to agy as an unknown model. Type checking and the full automated test suite passed.

Confidence Score: 5/5

Safe to merge based on the exercised fallback behavior and passing repository checks.

The updated model-selection path was exercised through the MCP handler with controlled available-model lists, covering both an available fallback model and the no-configured-model path. No defects remain in the review output.

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

T-Rex Logs

What T-Rex did

• I ran a focused Vitest test through the MCP handler with controlled agy models listings and observed the routing results as Gemini 3.6 Flash (High) for a parent-release scenario, then Gemini 3.5 Flash (High) when 3.7 was unavailable, and finally omitted the model with agy default when neither option was present.
• The routing logic in src/models.ts selects only names returned by agy models and appends the configured default only if listed, while the handler passes the resolved value to the runner and labels an undefined value as agy default.
• The test setup also documents that the delegate preference is Gemini 3.7 Flash (High) with Gemini 3.5 as fallback and that the default is 3.7, and notes that a focused test was copied into Vitest and run through the injectable runner because a live agy executable was not present.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "feat!: default to Gemini 3.7 Flash (High..." | Re-trigger Greptile}