issues: capture reconciliation follow-ups

[BigSimmo]

Summary

• record the primary-checkout ownership gap discovered after reconciliation
• add deterministic reconciliation-evidence generation as a deferred tooling task
• add bounded retained-worktree cleanup batches
• advance the monotonic task-ledger ID marker to 080

Why

The completed reconciliation exposed three remaining workflow improvements that were not already covered by #55, #67, #75, or #76. Capturing them in the durable ledger prevents the lessons from being lost or reintroduced as broad cleanup work.

Files

• docs/outstanding-issues.md

Verification

• prettier --check docs/outstanding-issues.md — passed
• node scripts/check-docs-links.mjs — passed; 1,152 references
• node scripts/check-docs-script-refs.mjs — passed; 341 references
• git diff --check origin/main...HEAD — passed
• ID audit — highest 079, next marker 080, no duplicates
• npm run verify:pr-local -- --dry-run --files docs/outstanding-issues.md — selection reviewed

Checks not run

The full local verify:pr-local suite was not run because the net change is documentation-only and this isolated worktree has no dependency install. Required hosted checks remain the merge gate.

Risk and rollback

Documentation-only; no application, database, retrieval, provider, or deployment behavior changes. Rollback is a single PR revert. Unrelated dirty primary-checkout work was not touched.

[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: 25 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: 9c9214da-9612-45b5-b39c-7c7da0f12494

📥 Commits

Reviewing files that changed from the base of the PR and between d21f9f7 and 26ea913.

📒 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/reconciliation-lessons-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.}