feat(tooling): add bounded worktree cleanup batching, cross-platform issue scripts, and post-restore sanity runbook (#079, #338, #326)

[BigSimmo]

Summary

Addresses Workstream 6 tasks:

• Task #079 (Worktree Batch Cleanup Script): Added bounded --batch-size <N> batching to scripts/clean-worktree.mjs with porcelain parsing, orphan detection preserving main/active worktrees, and --self-test validation.
• Task #338 (Cross-Platform Issue Register Generator): Standardized scripts/outstanding-issues.mjs and scripts/issues-report.mjs to use standard Node.js APIs (node:path, node:fs, node:url) and forward-slash git paths for seamless cross-platform execution (Linux/macOS/Windows).
• Task #326 (Document Post-Restore Recovery Controls): Documented operational runbook steps and sanity check queries in docs/db-maintenance.md and docs/disaster-recovery-runbook.md for all 5 environment-owned recovery controls (pg_cron telemetry retention schedules, Supabase Vault secrets, custom database GUCs, Supabase Edge Functions, and dashboard-owned auth/pool configuration).

Verification

• node scripts/clean-worktree.mjs --self-test (PASS)
• node scripts/outstanding-issues.mjs --self-test (PASS)
• npm run typecheck:internal (PASS)
• npm run lint:internal (PASS)
• npm run format (PASS)

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

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:3 minutes

Limit details: You’ve used all 1 included review currently available under your plan. You completed 95 included PR reviews in the past 7 days; at that activity level, included reviews refill at 1 review per hour.

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: ae40146c-4f41-4ee2-9f15-c006d676b5b6

📥 Commits

Reviewing files that changed from the base of the PR and between aade20a and 2cfbb9d.

📒 Files selected for processing (5)

• docs/db-maintenance.md
• docs/disaster-recovery-runbook.md
• scripts/clean-worktree.mjs
• scripts/issues-report.mjs
• scripts/outstanding-issues.mjs

---

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