docs(issues): archive #004 as obsolete (rescue target gone; 2/3 already on main)

[BigSimmo]

What

Archives ledger item #4 ("Rescope provider-gated RAG safety ideas") to Resolved as obsolete. Single-file, docs-only change to docs/outstanding-issues.md.

Why

Triaging the open RAG items surfaced that #4's premise no longer holds:

• Rescue target is gone. The stale ~754-line RAG-safety worktree it wanted to rescue from is unrecoverable across every worktree and reachable git ref (pickaxe over all refs = 0 hits), consistent with the documented branch/worktree sweeps.
• 2 of 3 ideas already shipped on main. Answer-quality thresholds (rag-extractive-answer.ts + eval-answer-quality) and deep-health (?deep=1, feat(observability): OpenAI answer spend snapshot on the deep health probe #585/feat(ops): daily ops digest from the deep health probe (dispatch-only) #587) already exist.
• Only cost-cap preflight was genuinely missing — and, per session decision, it's dropped rather than re-filed.

Scope / safety

• Docs-only. No code, no protected RAG surface touched → no RAG impact: line required (pr-policy keys on code paths, not the ledger doc); no canary, no provider calls.
• Bump typescript from 5.9.3 to 6.0.3 #5 intentionally left open — another session (docs(issues): capture auth-connection-cap debt; fix broken #005 doc path #1046) already captured the same pre-clamp-ordering finding there and kept it as a P3 revisit-note.
• Bump actions/checkout from 4 to 6 #1 stays open, correctly gated on the provider 36/36 gate + ambiguity canary + approval.
• Gates run: prettier --check ✓, docs:check-links ✓ (1092 refs resolve).

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated the outstanding-issues documentation to move item #004 from open items to the resolved/archive section.
  • Recorded the resolution outcome, including the removal of obsolete work and the decision not to re-file the missing cost-cap preflight item.

[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: 1 minute

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: 263483b1-1c3a-4451-b2a7-fdb177b4350c

📥 Commits

Reviewing files that changed from the base of the PR and between 291527b and 41a3f29.

📒 Files selected for processing (2)

• docs/outstanding-issues.md
• docs/process-hardening.md

📝 Walkthrough

Walkthrough

Changes

Issue #004 archival

Layer / File(s)	Summary
Move issue #004 to resolved archive docs/outstanding-issues.md	Removes recommendation #004 from Open items and records its 2026-07-22 resolution under Resolved / archive.

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

Possibly related PRs

• BigSimmo/Database#903: Documents related cleanup and follow-up handling for the obsolete provider-gated RAG safety worktree.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly matches the main change: archiving #004 as obsolete in docs.
Description check	✅ Passed	It covers the summary, rationale, verification, and safety notes, though the template headings are not followed exactly.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/rag-ranking-safety-issues-09867c

---

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 291527b024

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".