PIPELINE-1: required_slots backstop, reserve fallback/common_query, listen field

[JarbasAl]

Consolidates the ovos-pipeline-1.md companion edits previously bundled into the union-slots (#56), FALLBACK-1 (#39), COMMON-QUERY-1 (#40) and AUDIO-1 (#38) feature PRs into a single one-file change — per the 1 file, 1 PR rule.

Changes

• §6.1 / §6.2 — orchestrator backstop for required_slots (INTENT-3 §5.3): after a plugin returns a Match, the orchestrator MUST treat it as declined if any required slot is absent. Second line of defense behind engine-side match() enforcement.
• §7.3 — reserve two further intent_names: fallback (FALLBACK-1 §6.3) and common_query (COMMON-QUERY-1 §3). COMMON-QUERY-1 asserted the reservation but never added the registry row — this closes that gap.
• §9.6 — add the OPTIONAL listen field to ovos.utterance.speak; the output-side behaviour is owned by AUDIO-1.

Compatibility: all additions are backwards-compatible. PIPELINE-1 is already V2 (its namespaced topics replace pre-spec names); these refinements don't change the class, so Version stays 2.

#56 / #39 / #40 / #38 drop their pipeline-1 companion 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 39 minutes and 58 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: 5ed90f15-cce3-4214-b415-28dbc4823fca

📥 Commits

Reviewing files that changed from the base of the PR and between 1926a80 and 04e35d4.

📒 Files selected for processing (2)

• CHANGELOG.md
• pipeline-1.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch spec/pipeline1-plugin-companions

---

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