chore: align TinyAgents 2.1 and migration docs

[senamakel]

Summary

• Aligns TinyCortex on TinyAgents 2.1 and refreshes the lockfile and nested vendor pointer.
• Adds a standalone crates.io patch so a direct TinyCortex checkout consistently uses its reviewed nested TinyAgents source.
• Adds the persona feature to the CI feature matrix.
• Corrects migration documentation to reflect that the generic sync engine is crate-owned while OpenHuman retains scheduling, credentials, RPC, policy, and event-bus integration.

API Or Behavior Changes

No TinyCortex API behavior changes. This unifies dependency identity, expands CI coverage, and corrects ownership documentation.

Tests

Focused validation completed:

• cargo test --no-default-features --features persona -- --test-threads=1 (1284 unit tests plus integration and doc tests passed)

• OpenHuman CI Full TinyCortex Memory Tests passed in run 29925645209

• cargo fmt --check

• cargo clippy --all-targets -- -D warnings

• cargo build --all-targets

• cargo test

Documentation

Updated the OpenHuman memory-engine migration, compatibility, code-reference, and sync ownership documents in this repository.

[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: 40 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: d0e75402-d44e-424e-9fd0-681a89c90bad

📥 Commits

Reviewing files that changed from the base of the PR and between daaaf6b and 55bf066.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (10)

• .cargo/config.toml
• .github/workflows/ci.yml
• Cargo.toml
• docs/openhuman-memory-engine-spec.md
• docs/openhuman-memory-migration.md
• docs/openhuman-memory/README.md
• docs/openhuman-memory/openhuman-code-reference.md
• docs/openhuman-memory/sources-registry-sync.md
• docs/plan/05-openhuman-compat-matrix.md
• vendor/tinyagents

---

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