spec: converse.md — RECOMMENDED tuning defaults, identity-gated response mode, pure updated_session channel#107
spec: converse.md — RECOMMENDED tuning defaults, identity-gated response mode, pure updated_session channel#107JarbasAl wants to merge 1 commit into
Conversation
…esponse mode, no in-place session mutation Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 52 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Refines OVOS-CONVERSE-1 for internal purity and self-consistency (per-file split of the consistency audit).
Changes
session.converse_handlers; a pruned or unrecognised holder is discarded viaMatch.updated_session, never delivered to."done"removal is gone — PIPELINE-1 §4.2'sMatch.updated_session-only channel discipline now holds without exception; removal defers to the next claiming match or the §3.2 TTL.<skill_id>.converse.ping/.pong); the only colon topics are genuine PIPELINE-1 §7 dispatches (<skill_id>:converse,<skill_id>:response).skill_id/intent_namelive in the topic, not repeated indata; slot map namedslotsper PIPELINE-1 §4.1.result) is protocol-local; OVOS-SESSION-1 cited by canonical title.Principle
Colon
<x>:<y>is reserved for the orchestrator dispatch shape (MSG-1 §2.1.1); everything else is dotted. MUST/MUST NOT mark correctness/interop invariants only; numbers are RECOMMENDED defaults. One channel for session writes (Match.updated_session) with zero exceptions.Versionstays2: VERSIONING.md defines the field as the V0-compatibility class, which these edits do not change.🤖 Generated with Claude Code