docs: appendix — divergence catalogue and gaps reconciled with the refactored specs

[JarbasAl]

Brings the non-normative appendix in line with the refactored spec bodies:

divergences.md

• §5.2: records the <skill_id>:common_query → <skill_id>.common_query.request rename — the full-answer request is an addressed message, not a dispatch, so it moves off the colon shape MSG-1 §2.1.1 reserves for dispatch topics.
• §5.4: records STOP-1's no-escalation-on-silence behavior — a silent stoppability poll falls back to the recency-selected active_handlers target instead of escalating to a global stop.
• §5.4: records the TRANSFORM-1 priority-convention divergence — the reference implementation sorts descending (reverse=True), the exact inverse of the spec's ascending convention; inverse-convention assignments must be renumbered or the chain executes backwards.

gaps.md

• Drops the "per-plugin behavioural specs" gap — fallback, ocp, and persona now have their own specs (FALLBACK-1, OCP-1, PERSONA-1), closing the candidate list.
• persona_id removed from the unclaimed-session-fields list (claimed by OVOS-PERSONA-1).
• The bridge audio-over-bus gap is narrowed to what is still open: the outbound leg is covered by OVOS-AUDIO-1 (ovos.utterance.speak.b64 → ovos.audio.speech, base64 payloads on ovos.audio.queue/play_sound); only inbound satellite-to-hub raw-audio transport remains undefined.

reference.md / rationale.md

• Fixes the "OVOS-MSG-1 v2 §2.1.2" mislabels — the topic conventions live under MSG-1 §2.1, and MSG-1 is not cited by a v2 class.

No appendix page describes SYSTEM_confirm/SYSTEM_select or the player time convention, so no reconciliation was needed there; the appendix banners (non-normative headers) are untouched. Non-normative — no CHANGELOG entry.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 53 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 54ac9244-ca4e-426f-bd49-500cb33711b9

📥 Commits

Reviewing files that changed from the base of the PR and between 9003dcd and 0674d50.

📒 Files selected for processing (4)

• appendix/divergences.md
• appendix/gaps.md
• appendix/rationale.md
• appendix/reference.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/appendix-reconcile

---

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