spec: OVOS-AUDIO-1 — bridge cite; listen-gating scope; barge-in policy note

[JarbasAl]

🤖 Auto-generated by Claude Fable 5 (claude-fable-5) via Claude Code — NOT human-reviewed. Verify before acting. Cross-spec citations were model-verified against dev source; behavior-change sections need owner judgment.

Summary

• AO1: fix §4.3 bridge citation OVOS-BRIDGE-1 §4.2.4 → §4.2.5 (verified against bridge-1.md — §4.2.4 is "Per-satellite response personalisation", §4.2.5 is "TTS as a service").
• AO2: scope §4.4's ovos.audio.output.ended-gated listen timing to the local-playback path; forward-reference §3.4's b64 exception (listen fires right after ovos.audio.speech, no queue/ended to gate on).
• AO4: new §6 paragraph — barge-in (wake-word during active playback) is deployer policy; a controller MAY subscribe to ovos.listener.wakeword (OVOS-AUDIO-IN-1 §6.5) and emit ovos.audio.stop. This spec mandates neither.
• AO5: scope §3.2's synthesis-failure clause per-segment (whole utterance or sentence-chunk); state partial-utterance failure has no observable bus contract beyond §5.2's ended-on-queue-empty.
• AO6: one-sentence note that is_speaking is deliberately session-scoped; no aggregate query exists in this version.
• CHANGELOG updated under OVOS-AUDIO-1 § 2.

Test plan

• Diffed audio-out.md against bridge-1.md headings to confirm §4.2.5 is correct.
• Cross-checked audio-in.md §6.5 for the wakeword topic/fields cited in §6.
• N/A — prose-only spec edit, no code/CI to run.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 41 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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 Plus

Run ID: c2ae616b-9d8c-427d-8edd-f6e3bf5ab598

📥 Commits

Reviewing files that changed from the base of the PR and between 1d3622b and 1cebab4.

📒 Files selected for processing (2)

• CHANGELOG.md
• audio-out.md

---

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