docs(issues): reconcile queued ledger requests (remediation Phases 2–3, #2105 resolutions) - #2120
Merged
Merged
Conversation
#2105 resolutions) Apply the 88 queued outstanding-issues inbox requests to the canonical ledger in one serialized transaction from a fresh origin/main base. The batch covers the database-remediation set (updates to #316, #56 and #183, four add requests and ten cancellation decisions) together with the manual done resolutions queued by PR #2105. No request was adjudicated by hand: `npm run issues:reconcile` applied what was queued and moved every processed request and cancellation into docs/outstanding-issues-inbox/applied/ as the audit trail. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C6WXAK931ZPgisknbCTnpR
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Contributor
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in:49 minutes Limit details: You’ve used all 1 included review currently available under your plan. You completed 102 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 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (90)
Comment |
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C6WXAK931ZPgisknbCTnpR
Uh oh!
There was an error while loading. Please reload this page.
1 task
BigSimmo pushed a commit
that referenced
this pull request
Aug 18, 2026
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C6WXAK931ZPgisknbCTnpR
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/outstanding-issues-inbox/requests to the canonical ledger in one serializednpm run issues:reconciletransaction, run from a worktree whose base was exactlyorigin/mainatce702ba(check-base-freshness:behind 0, ahead 0).#316,#056and#183update requests (503c3553,5ed2f873,41576279), four add requests, and ten cancellation decisions — together with the batch of manual done resolutions queued by PR feat(viewer): implement crop-to-page bounding box overlay and record 53 manual ledger resolutions #2105.docs/outstanding-issues-inbox/applied/as the immutable audit trail; it refused nothing. The diff is exactly one modified canonical file plus 88 renames.Verification
npm run verify:pr-local -- --files <89 changed paths>— classified as recognised low-risk documentation scope; all 11 selected gates completed, none failed, none unreached:Lint, typecheck, the full unit suite, the RAG fixture scan, the build and the offline RAG checks were skipped by the selector as out of scope for a docs/ledger-only diff.
The three decisive ledger lines:
check:ledger-write-disciplinecompares two committed refs, so it was re-run after the commit; its pass is the proof that the canonical diff equals the recorded reconciliation transaction exactly.npm run formatwas run over the whole tree before committing and reported every file unchanged;format:changedinsideverify:pr-localpassed on the pushed blob.UI verification not run: no UI, routing, styling, browser, reduced-motion or forced-colors behaviour changed.
Provider-backed gates not run: no retrieval, ranking, selection, chunking, answer-generation, Supabase or deployment behaviour changed.
Risk and rollout
git revertof the single reconcile commit restores both the canonical ledger and the 88 request files to their pre-reconciliation paths, since the transaction is one commit of one modification plus 88 renames.Notes
mainmerged into it. The reconciler validates its base andcheck:ledger-write-disciplinerequires the canonical diff to equal the recorded transaction exactly, so a merge commit invalidates the proof. Ifmainmoves and this PR conflicts, close it and redo the reconciliation from a fresh base rather than syncing this branch.claude/issues-reconcile-20260818, "reconcile seven queued requests into the outstanding-issues ledger") is open and carries its own competing transaction againstdocs/outstanding-issues.md, recorded against an older base. Two open reconciliations is exactly the serialization this process exists to prevent. One of the two should land and the other be closed and redone from the post-merge base; this PR is the one whose base is current atce702ba.docs/outstanding-issues.mdis the canonical rendered source and is current, but the register refresh (refresh-issues-list.ps1→ISSUES-LIST.html) is an absolute-Windows-path operator step that a Linux container cannot run or verify. Per.claude/skills/issues/SKILL.mdno substitute renderer was improvised. The reconciliation commit that made it stale is the single commit on this branch.Generated by Claude Code