docs(issues): capture auth-connection-cap debt; fix broken #005 doc path

[BigSimmo]

Summary

Docs-only reconciliation of the outstanding-issues ledger (docs/outstanding-issues.md) against current main (post-#1033, which already resolved#2/#3):

• Capture Improve Clinical KB dashboard and RAG hardening #11 — the still-untracked Supabase Auth DB-connection allocation debt: operator-only dashboard action (percentage-based allocation before compute scale-up), not settable via SQL/MCP. Source: docs/auth-connection-cap-runbook.md.
• FixBump typescript from 5.9.3 to 6.0.3 #5 Source path — src/lib/rag/clinical-search.ts:1362 → src/lib/clinical-search.ts:1735. The rag/ path never existed, so it was failing docs:check-links on main; this flips that gate green. Also clarifies that ordering already sorts by the unbounded pre-clamp rankScore, so the clamp bounds only reported confidence (not order).

Verification

• prettier --check docs/outstanding-issues.md ✅
• npm run docs:check-links ✅ (1084 references resolve — repairs the pre-existing red)

Governance

• RAG impact: no retrieval behaviour change — docs-only ledger edit (no src/lib/rag/** or ranking/retrieval code touched).
• Clinical governance preflight: N/A — no ingestion, answer generation, retrieval/ranking, source rendering, document access, privacy, or production-config code changed. Single file changed: docs/outstanding-issues.md.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated the outstanding issues tracker with corrected source references.
  • Added a new open item covering operator-only database connection allocation.
  • Advanced the next issue identifier and preserved the resolved issues archive.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 85925942-84d5-456c-ad26-eee8b3624a3b

📥 Commits

Reviewing files that changed from the base of the PR and between cde6c5c and efcd93f.

📒 Files selected for processing (1)

• docs/outstanding-issues.md

---

📝 Walkthrough

Walkthrough

Updated the outstanding issues document’s open items table by advancing its counter, correcting a clinical search source reference, and adding an authentication database-connection allocation issue.

Changes

Outstanding issues documentation

Layer / File(s)	Summary
Open items update docs/outstanding-issues.md	Advances the next issue ID, updates item #005 source locations, and adds open item #011 with its details, next action, sources, and date.

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

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The PR only updates docs and does not implement the requested setup-node or TypeScript dependency bumps in [#2, #5].	Update the workflows/package config to bump actions/setup-node to 6 and TypeScript to 6.0.3, then rerun the required verification.
Out of Scope Changes check	⚠️ Warning	The only change is a docs ledger edit, which is unrelated to the linked dependency-update objectives.	Either add the actual dependency bumps or move the docs reconciliation to a separate PR tied to its own issue.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately summarizes the docs-only ledger reconciliation and path fix.
Description check	✅ Passed	The description includes a summary and verification notes, and largely matches the template despite not using every section heading.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/issues-ledger-reconcile

---

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