Skip to content

APPENDIX: point the normative-document list at the README registry#73

Merged
JarbasAl merged 1 commit into
devfrom
rec/appendix-normative-list
Jun 26, 2026
Merged

APPENDIX: point the normative-document list at the README registry#73
JarbasAl merged 1 commit into
devfrom
rec/appendix-normative-list

Conversation

@JarbasAl

Copy link
Copy Markdown
Member

APPENDIX.md enumerated the normative specs inline, and that list had drifted — it omitted SESSION-2, AUDIO-IN-1, BRIDGE-1, AUDIO-1, GUI-1, PERSONA-1, FALLBACK-1, and OCP-1.

Rather than re-sync a duplicate list that will drift again, this points readers at the README spec registry — the single source of truth for the spec set.

Single-file, non-normative (no version bump). Touches a different region of APPENDIX.md than #37, so the two do not conflict.

🤖 Generated with Claude Code

The inline enumeration of normative specs had drifted out of sync with
the spec set (it omitted SESSION-2, AUDIO-IN-1, BRIDGE-1, AUDIO-1,
GUI-1, PERSONA-1, FALLBACK-1, OCP-1). Reference the README spec registry
as the single source of truth instead, so the appendix cannot drift.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jun 26, 2026

Copy link
Copy Markdown

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 58 minutes and 19 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: 9a30bbc5-eb9d-4b82-b2d4-4e562bd6c840

📥 Commits

Reviewing files that changed from the base of the PR and between b7e16b9 and 0b46c96.

📒 Files selected for processing (1)
  • APPENDIX.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch rec/appendix-normative-list

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

Comment @coderabbitai help to get the list of available commands.

@JarbasAl JarbasAl merged commit 9d7c7a2 into dev Jun 26, 2026
1 check passed
@JarbasAl JarbasAl deleted the rec/appendix-normative-list branch June 26, 2026 22:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant