spec: audio-in.md — wakeword signal, device-scoped sleep, language precedence

[JarbasAl]

Refines OVOS-AUDIO-IN-1.

Changes

• §6.5 ovos.listener.wakeword — the wake-word detection signal (wake_word required, lang optional), emitted before ovos.listener.record.started; it is the observable event behind a wake-word-derived session.request_lang in multi-wakeword deployments. Push-to-talk / ovos.mic.listen capture emits no wake-word signal.
• §6.3 device-scoped sleep — sleep is a physical device state: a sleeping service captures nothing for any session, regardless of which session carried the request. Sleep entry is unacknowledged by design; the only sleep-related emission is ovos.listener.awoken on the sleep→awake transition. (Statement lives with the sleep request itself, not in the wakeword section.)
• §5.1 language resolution as a clear rule — MUST-precedence (detected_lang → request_lang → session.lang → deployment default): a deterministic order is what lets every producer of a language hint predict the transcription language, so it is an interop rule, not tuning.
• context.voice_match marked as an illustrative key name, not claimed by this spec.
• Bus surface and conformance updated; CHANGELOG entry appended under the class-2 section (Version stays 2 — additive within the class).

No timeouts/tuning values exist in this spec; nothing to downgrade to RECOMMENDED.

🤖 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: 52 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: 5bc53149-d911-44b2-a774-54a49fb0b94f

📥 Commits

Reviewing files that changed from the base of the PR and between 9003dcd and 869c1f6.

📒 Files selected for processing (2)

• CHANGELOG.md
• audio-in.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch spec/audio-in

---

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