Prepare tiingo-mcp 2.1.0 release

[wshobson]

Summary

• prepare the backward-compatible 38-tool REST/upstream-WebSocket expansion as semantic version 2.1.0
• synchronize Cargo.toml, the root Cargo.lock package, and the MCPB manifest, and convert the changelog to 2.1.0 (Unreleased)
• clarify that 2.0.2 remains the published registry/installer release while local source installs exercise the unreleased 2.1.0 tree; keep installer URLs pinned to v2.0.2

Verification

• cargo +stable fmt --check
• strict Clippy on stable 1.98.0 and Rust 1.88.0
• full locked offline suite on both toolchains: 184 passed, 12 authorized-live tests ignored
• cargo +stable llvm-cov --all-targets --all-features --locked --fail-under-lines 93 --summary-only: 93.95% lines
• stable and Rust 1.88.0 locked release builds
• cargo deny check all
• dist plan for all five release targets
• cargo +stable publish --dry-run --locked
• focused RMCP contract/tools/resources/prompts and stdio process tests
• local Apple Silicon MCPB 2.1.2 validation, pack, and inspection
• CodeRabbit CLI rereview: 0 issues

Ignored live tests were not run; they remain separately authorized and quota-consuming.

Release stop

This PR does not tag, publish the crate, upload MCPB bundles, or create a GitHub release. Those actions remain separately authorized.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 9851bd50-5960-402d-8609-7310082f63cc

📥 Commits

Reviewing files that changed from the base of the PR and between a8196a5 and e24e12a.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (4)

• CHANGELOG.md
• Cargo.toml
• README.md
• packaging/mcpb/manifest.json

Included review availability: 0 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour.

---

📝 Walkthrough

Summary by CodeRabbit

• Documentation

  • Updated release-status messaging for version 2.1.0.
  • Clarified installation options and documented the release-preparation tool coverage.

• Release

  • Updated package and crate versioning to 2.1.0.
  • Marked version 2.1.0 as unreleased in the changelog.

Walkthrough

The release metadata now uses version 2.1.0. The changelog and README identify the release as unreleased, while installation instructions distinguish published 2.0.2 packages from local builds.

Changes

2.1.0 release preparation

Layer / File(s)	Summary
Version metadata and changelog Cargo.toml, packaging/mcpb/manifest.json, CHANGELOG.md	Package versions changed from 2.0.2 to 2.1.0. The changelog heading now identifies 2.1.0 (Unreleased).
Release and installation documentation README.md	The README labels the 38-tool surface as release preparation and separates published 2.0.2 installation from local 2.1.0 installation.

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

Merge Risk: ⚪ Minimal · up to e24e1

This PR synchronizes the 2.1.0 release metadata and documentation without publishing or changing runtime behavior; no actionable merge-blocking risk remains beyond normal checks and review.

Poem

A rabbit checks the version line
2.1.0 now hops in time
The changelog wears its future name
Local builds join the release game
Published paths stay clear and bright
Ears up for launch night

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: preparing the tiingo-mcp 2.1.0 release.
Description check	✅ Passed	The description directly explains the 2.1.0 release preparation, synchronized version updates, documentation changes, verification, and release scope.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (4 skipped: 4 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/release-2.1.0-prep

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch codex/release-2.1.0-prep

---

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