Skip to content

docs(appendix): timeless gaps page, drop PR pointer#101

Merged
JarbasAl merged 1 commit into
devfrom
docs/polish-gaps
Jun 27, 2026
Merged

docs(appendix): timeless gaps page, drop PR pointer#101
JarbasAl merged 1 commit into
devfrom
docs/polish-gaps

Conversation

@JarbasAl

Copy link
Copy Markdown
Member

Editorial polish of appendix §7 (known gaps) for timeless,
standalone reading:

  • Remove the "AI-generated draft / not yet fully reviewed" provenance
    banner (the page header already carries a "Non-normative" notice).
  • Retitle "Known gaps and planned work" -> "Known gaps".
  • Remove the in-flight PR pointer "(in flight at PR OVOS-SESSION-2: Session Lifecycle and State Ownership (draft) #27)" and the
    temporal words "not yet claimed", "current OVOS already carries",
    "do not currently have".
  • Reword "deferred to a future X specification" / "a future revision"
    to the timeless "separate X specification" / "a revision".

Non-normative companion content only; the gap list is unchanged.

Editorial polish of appendix §7 (known gaps) for timeless,
standalone reading:

- Remove the "AI-generated draft / not yet fully reviewed" provenance
  banner (the page header already carries a "Non-normative" notice).
- Retitle "Known gaps and planned work" -> "Known gaps".
- Remove the in-flight PR pointer "(in flight at PR #27)" and the
  temporal words "not yet claimed", "current OVOS already carries",
  "do not currently have".
- Reword "deferred to a future X specification" / "a future revision"
  to the timeless "separate X specification" / "a revision".

Non-normative companion content only; the gap list is unchanged.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@JarbasAl JarbasAl merged commit 7ee0a7b into dev Jun 27, 2026
@JarbasAl JarbasAl deleted the docs/polish-gaps branch June 27, 2026 00:06
@coderabbitai

coderabbitai Bot commented Jun 27, 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 33 minutes and 30 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: d6ead9bb-5b8e-4022-b6ac-c1a887e793bb

📥 Commits

Reviewing files that changed from the base of the PR and between 2033980 and db5a259.

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

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.

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