issues: align scheduled diagnostics priority

[BigSimmo]

Summary

• align open item #023 to P2 so it matches its A2 recommended-queue placement
• close the late review finding posted after PR docs: make outstanding issues the universal task ledger #1106 merged

Verification

• npx prettier --check docs/outstanding-issues.md
• session hook runtime assertion: 1 P1, 15 P2, 24 P3; #023 remains in the A2 queue
• npm run docs:check-links (1,136 references)
• git diff --check
• npm run verify:pr-local not run: one-cell documentation priority correction; protected CI is the exact-head broad gate.
• UI verification not run: no UI or browser behavior changed.

Risk and rollout

• Risk: Minimal; canonical ledger metadata only.
• Rollback: Revert this commit.
• Provider or production effects: GitHub PR/CI/merge only.

RAG impact: no retrieval behaviour change — task-priority metadata only.

Clinical Governance Preflight

Not applicable: no clinical behavior, retrieval, generation, source rendering, privacy, or production environment changed.

---

Note

Low Risk
Documentation-only priority field in docs/outstanding-issues.md; no runtime, RAG, or clinical code paths affected.

Overview
Updates the universal task ledger so open item #023 (read Sunday 2026-07-26 scheduled-run artifacts) is P2 instead of P3, matching its A2 placement in the recommended execution queue alongside #051 at order 8.

No task text, queue order, or application behavior changes—canonical priority metadata only.

^{Reviewed by Cursor Bugbot for commit 699af1f. Configure here.}

[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

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

Next review available in: 4 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 Plus

Run ID: 1152492d-3edd-4a66-82f9-e9cf81fbab8d

📥 Commits

Reviewing files that changed from the base of the PR and between 1391158 and 699af1f.

📒 Files selected for processing (1)

• docs/outstanding-issues.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/fix-ledger-priority-023

---

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