spec: README.md — spec-index titles match the spec headers#128
Conversation
…-1, INTENT-4 titles)
|
Warning Review limit reached
Next review available in: 53 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 |
Aligns the README spec index with each spec file's own header title (the index drops the trailing "Specification" by convention):
All other listed titles and Version values were checked against the spec headers and match.
Not fixed here (out of scope; each lands in its own per-file PR): the stale in-body citation "Session Carrier Wire Shape Specification" for OVOS-SESSION-1 still appears in persona.md, common-query.md, fallback.md, session-2.md, intent-context.md, and converse.md, plus the CHANGELOG.md section heading.
Non-normative — no CHANGELOG entry.
🤖 Generated with Claude Code