chore: vendor tinyagents dependency

[senamakel]

Summary

• add TinyAgents as the vendor/tinyagents git submodule using the canonical public HTTPS repository
• replace the fork-pinned Git dependency with the vendored TinyAgents 2.0 path dependency
• initialize submodules in CI and release checkouts

Why

TinyCortex previously fetched a specific TinyAgents fork commit directly through Cargo. Vendoring the canonical dependency matches the repository layout used by OpenHuman, makes the dependency source inspectable and editable in-tree, and avoids requiring fork-specific Git access.

The submodule is pinned to released TinyAgents 2.0.0 because it includes the embedding APIs TinyCortex consumes. The published 1.9.0 crate does not contain those APIs, so retaining a version = "2" fallback keeps cargo package verification and downstream crates.io consumption compatible.

Validation

• cargo fmt --all -- --check
• cargo check --locked
• cargo test (1,132 passed; 1 ignored doc test)
• cargo package --locked --allow-dirty
• verified vendor/tinyagents is a mode 160000 gitlink at TinyAgents v2.0.0

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 19 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 3ddb4bc5-6636-48da-bda2-b5cc49686c7c

📥 Commits

Reviewing files that changed from the base of the PR and between 1a3fcc5 and 648b0b0.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (5)

• .github/workflows/ci.yml
• .github/workflows/release.yml
• .gitmodules
• Cargo.toml
• vendor/tinyagents

---

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