chore(ledger): add outstanding issue closeout request rows

[BigSimmo]

Records closeout requests for completed/reviewed items into outstanding-issues inbox per current ledger state (no code-path changes).

Verification\n

• check:outstanding-issues\n- targeted tests and typecheck were run in prior worklog

[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:6 minutes

Limit details: You’ve used all 1 included review currently available under your plan. You completed 90 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: 4c0b6f08-9b4c-42e2-8fd7-b4085a158e16

📥 Commits

Reviewing files that changed from the base of the PR and between a96dcbb and 5bb043d.

📒 Files selected for processing (10)

• docs/branch-review-records/65bf63ffd245181d054f30ee9fc24f16ca83af0e52d784bb3860e470876e1e75.record.md
• docs/branch-review-records/8145832620703718dd3e73fb75753072cb7b441b62d2ddf6230bbc962e48a76c.record.md
• docs/outstanding-issues-inbox/314e5e31-7d15-46f2-adb0-c4d113bc589d.json
• docs/outstanding-issues-inbox/55cb57e8-7e6e-42f8-bd79-81b81a01ef3a.json
• docs/outstanding-issues-inbox/55f0d5de-8642-487a-b063-44c1c0bc0921.json
• docs/outstanding-issues-inbox/739887b7-24d6-4ea8-9aad-e7700a537913.json
• docs/outstanding-issues-inbox/7e454b66-74ae-4e67-8669-1f1fdc2c018c.json
• docs/outstanding-issues-inbox/81fdf812-4dd6-4fd6-b2e8-f3b730affd8a.json
• docs/outstanding-issues-inbox/a81b68eb-6b26-46db-81fa-90279a599886.json
• docs/outstanding-issues-inbox/e54f04f8-09bb-4887-b3e4-a5cd99958798.json

---

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

[BigSimmo]

Codex review-and-fix summary

Final state

• Head: b9dde76fd4bbf40b705b99f3b03da06727b87bf6
• Base: 27f6b60429ab56a0e4a779b5b16c35e9cce630db (main)
• The branch was updated with non-rebase merge commits. The final head contains the latest base, is 0 commits behind, and GitHub reports it mergeable with a clean merge-tree.
• Auto-merge was left unchanged and is not armed.

Review and fixes

• Confirmed a PR-introduced premature closeout for #098. Commit 563ce4195512b9e623df6ba98762f4a3dc1b9e8e completed the route-level budget test but did not resolve the remaining offline-runner integration decision. Changed the request from done to update, retained the stop condition, and left the item open until the runner decision is implemented and recorded.
• The other seven requests were supported by the referenced merged commits/evidence, or correctly retained remaining external work (#314).
• Independent CodeRabbit and Codex bot review was unavailable because both services reported usage limits. I performed a distinct manual adversarial pass instead.
• Review threads: none. No actionable review or comment remained to resolve.

Verification

• Focused offline checks: all eight JSON requests parsed and passed request-schema and uniqueness checks; both immutable review-record filenames matched the SHA-256 of their rows.
• Exact-head CI: PR required, Static PR checks, branch-review ledger integrity, outstanding-issues integrity, ledger write discipline, changed-file formatting, documentation checks, SAST/Semgrep, and Secret Scan/Gitleaks all passed.
• Advisory or out-of-scope jobs, including UI, build, coverage, Lighthouse, migration, production, and visual jobs, were skipped by the docs-only scope. No live or provider-backed gate was run.

Residual risks and blockers

• No merge blocker remains.
• #098 intentionally remains open for runner integration.
• #314 still requires an explicitly authorised deployment and live measurement.
• The recorded Chromium evidence for #237 and #238 was reviewed but could not be independently rerun in this connector-only environment.
• A true local worktree and full dependency-backed offline suite were unavailable. Exact GitHub objects, focused structural validation, and repository CI were used instead.

The PR was not merged. Final merge is left to the user.