issues: queue fastest-wins plan and capture three follow-ups

[BigSimmo]

Summary

• Capture the 2026-08-05 fastest-wins planning session into docs/outstanding-issues.md.
• Add three new open rows (renumbered on main sync to #249 / #250 / #251): agent-safe wins classifier, execute Wave 0–4 plan, and gates + verification-router handoff pairing.
• Merge origin/main and keep main’s #246–#248 (results-band / search-health); bump issues:next-id to 252.
• Enqueue every previously open-but-unqueued item so the open table and recommended queue are 1:1, including PR ui: complete and activate the v2 design system #1616 follow-ups #237–#242, #244, #245 and main’s #246–#248.
• Repair earlier mislabeled recommended-queue rows from the original capture (order 27 → #201, order 35 → #202; queue #183 at order 82; drop stale archived #182).

Test plan

• npm run check:outstanding-issues — Outstanding-issues guard passed: 249 rows (118 open, 131 archived), unique ids, next-id=252
• Open vs queue recount: 118 open IDs, 0 missing from queue
• Merged origin/main with no leftover conflict markers; Bugbot found no bugs on the branch diff
• Confirm CI static-pr / outstanding-issues check stays green on this docs-only ledger diff

Clinical Governance Preflight

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

RAG impact: no retrieval behaviour change — outstanding-issues ledger and recommended-queue metadata only.

[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:56 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: e1c356a9-4a87-4d66-b455-6bf5162fa9cd

📥 Commits

Reviewing files that changed from the base of the PR and between 68d477e and 17d5ed5.

📒 Files selected for processing (1)

• docs/outstanding-issues.md

---

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

[supabase]

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[devin-ai-integration]

Devin Review found 1 potential issue.

⚠️ 1 issue in files not directly in the diff

⚠️ Eight open ledger items are still missing from the recommended queue despite the stated one-to-one repair (docs/outstanding-issues.md:157-159)

Eight already-open items (#237–#242, #244, #245) are left out of the recommended queue even though the queue was extended to cover every open row (rows added at docs/outstanding-issues.md:157-159 end at order 108), so the queue no longer matches the open list it claims to mirror.
Impact: Readers and the /issues tooling that treat the queue as the ordered view of all outstanding work will silently skip eight tracked items.

Counted open rows vs. queued IDs after the change

The file states the queue "is the ordered view of every open ledger row" (docs/outstanding-issues.md:35-36) and the PR claims 1:1 coverage. Parsing the current file gives 115 open rows but only 107 distinct IDs cited in the queue (order 21 covers two IDs). The IDs open-but-unqueued are #237, #238, #239, #240, #241, #242, #244, #245 (open rows around docs/outstanding-issues.md:285-291), all of which existed in the open table at the merge base. The guard scripts/check-outstanding-issues.mjs is structural only and does not detect queue/open divergence, so CI stays green.

View 1 additional finding in Devin Review.

[BigSimmo]

Flagging a sequencing dependency found during a cross-PR review sweep (not editing this branch directly, since it's not mine):

This PR's docs/outstanding-issues.md rows collide on ID allocation with #1620, which claimed the same range from an earlier main (the classic issues:next-id read-modify-write race — ledger #156/#168). #1620 has just been synced with current main and its rows renumbered to #249–#252 (next-id now 253).

Once #1620 merges, this branch will need the same treatment: merge origin/main, keep both sides' rows (never take one side wholesale — that drops rows), and renumber this branch's new rows to start from whatever next-id is at that point. npm run check:outstanding-issues will fail closed on the collision until that's done.

No action needed until #1620 lands — just flagging so it's not a surprise.

---

Generated by Claude Code

[cursor]

Addressed the Devin / Codex queue-coverage finding on 17d5ed53:

• Merged current main and resolved the docs/outstanding-issues.md conflict without dropping either side's rows.
• Kept main's #246–#248; renumbered this PR's fastest-wins appends to #249–#251 (next-id=252).
• Queued every open ID 1:1 (including #237–#242, #244, #245), moved A1 #226 into the A1 cluster (orders 1–5), and reclaimed order gaps with dense numbering.
• Refreshed the PR description so it no longer cites the already-taken #237–#239 IDs or the stale next-id=240 guard line.

npm run check:outstanding-issues → 249 rows (118 open, 131 archived), … next-id=252.

Re: the #1620 ID-race note — noted. This head now starts at #249; if #1620 lands first with #249–#252, this branch will need another renumber on the next main sync (classic #156/#168).

[BigSimmo]

Addressed the Devin / Codex queue-coverage finding on the latest head (377791de):

• Merged origin/main (was DIRTY / conflicting on docs/outstanding-issues.md).
• Kept main’s #246–#248; renumbered this PR’s fastest-wins follow-ups to #249–#251.
• Queued #237–#242, #244, #245, and main’s previously unqueued #246–#248 so open ↔ recommended queue is 1:1 (118/118).
• Gate: Outstanding-issues guard passed: 249 rows (118 open, 131 archived), unique ids, next-id=252.