chore(issues): reconcile 9 queued ledger requests - #1968
Conversation
Applies the 9 pending outstanding-issues-inbox requests that had already landed on main via merged PRs but not yet been folded into the canonical ledger: - #231 (P1): incident addendum — rung-2 evidence from the 2026-08-14 live latency investigation (source-pinned #316 index restore). - #235, #237, #238: records that PR #1940's earlier `done` closures were reviewed and rejected — none of the three closures actually satisfied their row's evidence requirement (jsdom/DOM coverage standing in for a real-browser visual pass). - #316 (P1): 2026-08-14 incident findings — 2 of 21 missing indexes restored live, before/after latency, forensics pointer. - 2 cancellation decisions applied (duplicate #231 update requests superseded by the combined incident-addendum version above). Processed via `npm run issues:reconcile` on a fresh origin/main base per repo convention; the 9 source requests move to docs/outstanding-issues-inbox/applied/ as an audit trail.
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in:38 minutes 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 (41)
Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:2c01a5eee2
ℹ️ 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".
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Summary
mainvia other merged PRs but were not yet folded into the canonicaldocs/outstanding-issues.md, vianpm run issues:reconcileon a freshorigin/mainbase per repo convention.#231(P1): incident addendum — rung-2 evidence from the 2026-08-14 live latency investigation, pinned to the#316index restore (before/aftersupabase_rpc_latency_ms31610 → 1535/8519).#235,#237,#238: records that PR docs(issues): retire the stale IN FLIGHT annotations, archive 9 verified rows #1940's earlierdoneclosures for these three rows were reviewed and correctly rejected — none of the three actually satisfied its row's evidence requirement (jsdom/DOM-testing-library coverage standing in for a real-browser visual pass at a real viewport). All three rows remain open with the rejection reasoning captured so a future closure attempt doesn't repeat the same mistake.#316(P1): 2026-08-14 incident findings — 2 of the 21 missing indexes restored live (owner-approved), before/after latency measurements, forensics doc pointer.#231update requests superseded by the single combined incident-addendum version above.docs/outstanding-issues-inbox/applied/as an immutable audit trail (perdocs/outstanding-issues-inbox/README.md); this is a rename, not a content edit.Verification
npm run check:ledger-write-discipline→ledger write discipline self-test passed./Ledger write discipline passed for 7679dfa25339..HEAD.npm run formatwas run but flagged ~30 unrelated files across the tree with corrupted markdown escaping (pg_net→pg*net,_every_→\_every*) — a broken local Prettier install/version mismatch in this environment, not real formatting debt. Those changes were discarded (git checkout --) and are not part of this diff.docs/outstanding-issues.mditself was not touched by that run, i.e. the reconciler's own output is already Prettier-clean.Risk and rollout
applied/for re-processing if ever needed.Notes
#098,#189,#215,#194,#210,#293done;#212,#309update) — those aren't part of this reconciliation since they haven't merged tomainyet; they'll need a follow-up reconcile pass once that PR lands.Generated by Claude Code