chore: notify branching strategy in README

[scarmuega]

Summary by CodeRabbit

• Documentation
  • Updated README to clarify branch guidance: v3 tracks the upcoming major with multi-chain support, while the main branch references the production-ready Oura v2.
  • Improved migration context for users moving between branches, outlining where to find stable vs. next-major information.
  • Removed outdated warnings about V1/V2 tracking to reduce confusion.
  • No changes to runtime behavior or APIs; this update is informational only.

[coderabbitai]

Walkthrough

README updated to reflect branch guidance: v3 tracks the next major Oura with multi-chain support; main branch documents production-ready Oura v2. No code changes.

Changes

Cohort / File(s)	Change Summary
Documentation README.md	Replaced prior V1/V2 tracking notice with details about v3 (next major, multi-chain) and clarified main branch aligns with production-ready Oura v2.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A nibble of notes on branches three,
V2 for today, V3 to-be.
I twitch my whiskers, docs now clear—
Multi-chain dreams are drawing near.
Thump-thump! I stamp in tidy glee,
README patched—ship it, whee! 🐇

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title clearly indicates that the change is a chore to update the README with branching strategy information, which directly matches the summary of changes. It succinctly identifies the scope (README) and purpose (branching strategy notification) without extraneous detail. This makes it easy for reviewers to understand the main change at a glance.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch v3

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 61dc55e and 1af8f27.

📒 Files selected for processing (1)

• README.md (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: Test Suite
• GitHub Check: Check (windows-latest, stable)
• GitHub Check: Check (ubuntu-latest, stable)
• GitHub Check: Lint Rust

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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