issues: clarify #250 waves do not outrank A1 acuity

[BigSimmo]

Summary

• Fix-forward for an orphaned follow-up from squash-merged PR issues: queue fastest-wins plan and capture three follow-ups #1624 (auto-merge raced a later push).
• Clarify open/queue #250 so multi-wave packaging is the engineering track only and does not outrank recommended-queue A1 acuity (#059/#053/#231/#207/#226).
• Note that Wave 0 queue repair / missing-open enqueue already landed with the #249–#251 capture; next engineering Wave 0 work is #201/#202.
• Append a prlanded ledger row for merged PR issues: queue fastest-wins plan and capture three follow-ups #1624.

Test plan

• npm run check:outstanding-issues — Outstanding-issues guard passed: 249 rows (118 open, 131 archived), unique ids, next-id=252
• npm run check:branch-review-ledger — Branch review ledger guard passed
• Diff is #250 prose (+ ledger append); open↔queue coverage unchanged from main (118/118)
• Confirm CI static-pr stays green on this docs-only ledger diff

Clinical Governance Preflight

Not applicable — docs-only ledger prose clarification; no clinical, ingestion, answer, retrieval, privacy, or production-env behaviour change.

RAG impact: no retrieval behaviour change — outstanding-issues / review-ledger metadata only.

  

Summary by CodeRabbit

• Documentation
  • Updated review and issue-tracking records with the latest merged review, queue-repair status, and recommended follow-up work.
  • Reorganized ledger entries for clearer tracking and added context on acuity ordering and operator workflows.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 42 minutes

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

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: 18d79c7b-8cd6-47e0-b535-bbcf41a2004b

📥 Commits

Reviewing files that changed from the base of the PR and between 8095be3 and 41d7605.

📒 Files selected for processing (2)

• docs/branch-review-ledger.md
• docs/outstanding-issues.md

📝 Walkthrough

Walkthrough

The PR updates two documentation ledgers. It adds and reorders branch-review records, then updates issue #250 with completed queue-repair status, next engineering work, acuity ordering, operator-track details, wave scope, and gating constraints.

Changes

Documentation ledgers

Layer / File(s)	Summary
Review ledger closeout and ordering docs/branch-review-ledger.md	Adds the PR #1624 closeout record and reorders adjacent review records.
Queue item #250 status and scope docs/outstanding-issues.md	Records completed Wave 0 queue repair, identifies #201/#202 as next work, and adds acuity, operator-track, wave, concurrency, and gating details.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• BigSimmo/Database#657: Updates the same branch-review ledger with reorganized review records.
• BigSimmo/Database#1224: Adds and reorders merged pull-request records in the branch-review ledger.
• BigSimmo/Database#1334: Updates entries in the outstanding-issues ledger.

Suggested reviewers: claude, cursoragent

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: clarifying that issue #250 waves do not outrank A1 acuity.
Description check	✅ Passed	The description explains the docs-only scope, summarizes the changes, and records verification results and governance impact.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

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

[BigSimmo]

Fix-forward for the #250 acuity-vs-waves clarification that missed the squash auto-merge of #1624. Core queue/open 1:1 repair already on main via #1624 (b03b51d7).

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.