docs: close Safety Plan privacy issue

[BigSimmo]

Summary

• archive issue [WIP] Harden authentication and protect sensitive tokens #60 after the verified Safety Plan privacy fix landed in PR fix: keep Safety Plan Generator identifier-free #1119
• promote [WIP] Improve data integrity and reliability of ingestion #61 as the next code task
• capture the load-sensitive reconciliation-preflight timeout as Delete .github/workflows/label.yml #67 without weakening timeouts or the shared test lock

Verification

• npx prettier --check docs/outstanding-issues.md — passed
• git diff --check — passed
• ledger assertions — queue orders 1–36 are continuous; [WIP] Harden authentication and protect sensitive tokens #60 is archived and absent from open items; Delete .github/workflows/label.yml #67 appears once in the queue and once in open items; next ID is 068

Checks not run

• Product/unit/browser suites were not repeated because this PR changes only the durable issue ledger. The implementation in PR fix: keep Safety Plan Generator identifier-free #1119 already passed its focused, broad, production-build, and hosted gates.

Risk and rollback

• Documentation-only; no runtime, database, provider, deployment, or retrieval behavior changes.
• Roll back by reverting this single commit if the ledger disposition is incorrect.

RAG impact: no retrieval behaviour change — documentation-only issue ledger update.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 35 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: 7143b0b0-3679-4680-b5d6-95d4ea88710e

📥 Commits

Reviewing files that changed from the base of the PR and between fea21f9 and 6f7f781.

📒 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/close-safety-plan-ledger

---

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

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6f7f781d58

ℹ️ 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".

[chatgpt-codex-connector]

Align #67's queue acuity with its open priority

This new queue row marks #067 as A3, but the open-items row for the same ID marks it P2. The SessionStart /issues hook renders queued IDs from the queue and then suppresses them from the separate priority summary, so this reliability issue is surfaced only as planned/A3 work even though the ledger classifies it as P2; set the queue acuity or the open priority to the same severity before this durable ledger becomes the source of truth.

AGENTS.md reference: AGENTS.md:L453-L456

Useful? React with 👍 / 👎.