docs: archive advisory UI scoping task

[BigSimmo]

Summary

• verify the already-landed advisory UI scope implementation on current main
• archive fix: close bug-hunter stale-state paths #137 now that mockup-only/quarantine gating and fail-open coverage remain green

Verification

• npm run check:ci-scope
• npm run check:gate-manifest
• npm run check:outstanding-issues -- --base-ref origin/main
• npm run check:branch-review-ledger
• git diff --check
• verify:pr-local not run: documentation-only closure of already-merged, current-main-verified behavior.
• UI verification not run: no UI or workflow behavior changed in this PR.

Risk and rollback

• Risk: minimal; the only risk is archiving an incomplete record. Current-main code and self-tests directly satisfy the row's outcome.
• Rollback: revert this PR to return fix: close bug-hunter stale-state paths #137 to the open table.
• Provider or production effects: GitHub PR/check workflow only; no application/provider changes.

RAG impact: no retrieval behaviour change — documentation-only closure.

[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 ↗︎.

[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:45 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: b9c681e3-7168-42aa-a162-edaa8bdae971

📥 Commits

Reviewing files that changed from the base of the PR and between fde68ed and f1d3f9e.

📒 Files selected for processing (2)

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

---

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