spec: transformer.md — ascending priority + compose-once-per-utterance; Match.slots naming

[JarbasAl]

Refines OVOS-TRANSFORM-1 to Version 2.

• §4 priority order: ascending, 1 runs first, default 50; stated without external justification. A priority assignment authored for the inverse (descending) convention MUST be renumbered — the orderings are exact inverses, an unrenumbered chain runs backwards.
• §5.3 compose-once-per-utterance: the effective chain per injection point is composed once per utterance lifecycle from the session as committed at utterance start; mid-lifecycle mutations of <type>_transformers / blacklisted_<type>_transformers take effect on the next utterance. Composing from a live session would make the lifecycle's transformer surface depend on mutation timing.
• §3.4 slot naming: Match.slots (consistent with PIPELINE-1 §4.1); all captures wording renamed, See-also updated.
• ovos.intent.unmatched replaces the retired failure topic on the no-transcription path; still MUST NOT be emitted on the cancellation path.
• CONTEXT-1 citations repointed (§5.1 engine-side / §5.2 in-place / §5.3 ovos.session.sync); nonexistent bus mutation topics dropped; attribution precedence + cancellation-stamp rationale stated locally; SESSION-1 claims →§2.2; slot-typing deferrals made timeless out-of-scope statements.
• CHANGELOG entry + Version bump to 2.

🤖 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: 64269b5c-f1fe-4374-816a-57f6e7bdcaed

📥 Commits

Reviewing files that changed from the base of the PR and between 9003dcd and 1a04b8d.

📒 Files selected for processing (2)

• CHANGELOG.md
• transformer.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch spec/transformer

---

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