SESSION-1: register in-flight session fields; move site_id ownership to BRIDGE-1

[JarbasAl]

Consolidates the SESSION-1 §2.1 field-registry edits that were previously bundled as companion edits inside the CONVERSE-1 (#25), FALLBACK-1 (#39), PERSONA-1 (#37), USER-ID-1 (#54) and BRIDGE-1 (#43) feature PRs into a single one-file change to the spec they all amend — per the 1 file, 1 PR rule.

Changes (ovos-session-1.md)

• §2.1 registry — register converse_handlers (CONVERSE-1 §2.1), fallback_handlers (FALLBACK-1 §4), persona_id (PERSONA-1 §3), the identity fields user_id/voice_id/face_id/name_id/passphrase_id/default_user_id (USER-ID-1 §2) and auth_level (integer, USER-ID-1 §3).
• §3.3 site_id — move the full definition to OVOS-BRIDGE-1 §3.4; this section and the registry Owner column become pointers, retaining only the orchestrator-pipeline consumer constraints (opaque, no-overwrite).
• See-also — fix ownership: active_handlers → PIPELINE-1 §7.1, converse_handlers → CONVERSE-1 §2.1; add owners for the new fields.
• Version 1 → 2, add the missing SESSION-1 CHANGELOG section, README index updated.

Compatibility: V1 (backwards-compatible) — every field is OPTIONAL on the wire; a V0/V1 consumer that ignores the new fields is unaffected.

The feature PRs listed above will drop their SESSION-1 edits and forward-reference this PR.

[coderabbitai]

Warning

Review limit reached

@JarbasAl, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 44 minutes and 8 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

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 credits.

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: fe064b63-7c6c-43bd-96f9-03f5614eddc0

📥 Commits

Reviewing files that changed from the base of the PR and between 54c6a0e and f47556d.

📒 Files selected for processing (2)

• CHANGELOG.md
• session-1.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch spec/session1-v2-field-registry

---

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.}