docs: triage future release milestones

[flyingrobots]

Summary

• Create and document explicit future release horizons for v8.1.0, v8.2.0, v9.0.0, and v10.0.0 after GitHub backlog triage.
• Update ROADMAP.md and BEARING.md to mirror live milestone counts, empty Beyond / open-unmilestoned queues, and the VISOR: emit GraphQL block artifact bundle with replay and visual scene facts #458 -> VISOR: validate packed-bijou-cells/1 and adapt to Surface #459 next-pull sequence.
• Record the triage in CHANGELOG.md and update WF-130 policy tests so stale COOL IDEA: compile GraphQL-authored UI scenes into Bijou Blocks #302/Beyond expectations cannot return.

Validation

• npx vitest run --config vitest.config.ts tests/cycles/WF-130/roadmap-goalpost-policy.part01.test.ts tests/cycles/WF-130/roadmap-goalpost-policy.part02.test.ts tests/cycles/WF-130/roadmap-goalpost-policy.part03.test.ts
• npm run docs:inventory
• git diff --check
• npm run typecheck:test
• npm run code-dojo:changed
• npm run lint
• pre-commit hook
• pre-push full verification, including 19 Vitest chunks and scripted interactive example smoke

[coderabbitai]

Warning

Review limit reached

@flyingrobots, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: c970adb2-dbd4-48b9-bed0-6518eb076cc9

📥 Commits

Reviewing files that changed from the base of the PR and between ef2ff00 and 3a2aa18.

⛔ Files ignored due to path filters (1)

• docs/ROADMAP.md is excluded by !docs/ROADMAP.md

📒 Files selected for processing (4)

• docs/BEARING.md
• docs/CHANGELOG.md
• tests/cycles/WF-130/roadmap-goalpost-policy.part01.test.ts
• tests/cycles/WF-130/roadmap-goalpost-policy.part02.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cycle/future-release-milestone-triage

---

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: af6dd79f36

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".