docs(issues): reconcile inbox requests from PR #2023/#2024 - #2032
docs(issues): reconcile inbox requests from PR #2023/#2024#2032BigSimmo wants to merge 9 commits into
Conversation
… ledger Applied after PR #2023 (440a34f) and #2024 (78fe906) landed their immutable inbox requests. npm run issues:reconcile allocated IDs and moved each processed request to docs/outstanding-issues-inbox/applied/. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01D2BUayF2Z9DAxvmL5XmLcC
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01D2BUayF2Z9DAxvmL5XmLcC
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. |
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in:58 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 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 (24)
Comment |
CI triageCI failed on this PR. Automated classification of the 2 failed job(s):
Compared with main CI run #11399 (cancelled). Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger. |
BigSimmo
commented
Aug 17, 2026
Superseded by #2043: a single fresh-base reconcile over the complete pending inbox. This branch reconciled a partial base (check:ledger-write-discipline: 'moved only part of the base inbox and left 6 request(s) pending'); a merge-and-rerun would allocate IDs as two batches and fail the same check, so it is replaced rather than repaired. |
BigSimmo
commented
Aug 17, 2026
Superseded by #2045, which has merged into Generated by Claude Code Generated by Claude Code |
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 36221231 | Triggered | Generic High Entropy Secret | d439b65 | tests/rag-adversarial-fixtures.test.ts | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Summary
npm run issues:reconcileto apply the 22 pending immutable inbox requests queued by PR harden(api): validate inbound DB and RPC payloads against Zod row contracts #2023 (squash440a34f71) and PR docs: coordination-chat handover for the RAG improvement programme #2024 (squash78fe906b8) into the canonicaldocs/outstanding-issues.mdledger. This is the one deliberately serialized fresh-base branch that is allowed to edit that file directly.docs/outstanding-issues-inbox/applied/as an immutable audit trail (standard reconcile behavior).npm run ledger:appendas a separate immutable record file.New/updated rows from the requested set
#212— corrected (unsafe-cast/JSON.parse remediation status)#J912J9— new, P1: governance question on fabricatedsimilarity: 1on document-summary rows#DP6M3G— new, P1: R1, unbudgeted strong escalation / lithium dosing route (packet S1b)#6BG9X2— new, P2: R2 + R3, claim-support strictness on verbatim-faithful restatements (packet S1c)#BTVMVK— new, P2: recurring Sentry "Unhandled server request error" on/api/search#ND10QT— new, P3:source_metadatapin inrag-row-contracts.tsis data-backed only#TYJ0XP— new, P3:eval-canary.ymlis post-merge only — record indocs/rag-behaviour#0MSNT8— new, P3: G1 implementation (governance Option B,similarity_origin: document_context)The remaining 14 applied requests (
#056,#098,#265,#314,#316,#318,#322,#237,#330,#331,#192,#162,#238,#324) were also pending in the inbox and were reconciled in the same transaction, sinceissues:reconcileapplies the full pending batch atomically.Verification
npm run check:outstanding-issues—Outstanding-issues guard passed: 348 rows (98 open, 250 archived), unique display and durable ids, collision-free allocation enabled, deprecated next-id marker ignored, no merge driver, no ids deleted from base 78fe906b8f30.npm run check:ledger-write-discipline—Ledger write discipline passed for 78fe906b8f30..HEAD.npm run verify:pr-local/verify:cheap— this diff touches onlydocs/outstanding-issues.mdand JSON inbox request files (a data move, not source/test/config), and is fully covered by the two ledger-specific gates above, which are exactly the gates this repo's own tooling designates for this transaction (check:ledger-write-disciplineis what CI/pre-push run for this exactdocs/outstanding-issues.mddiff).npm run formatwas run; it reported the reconcileddocs/outstanding-issues.mdas already Prettier-clean (no diff). It also reformatted unrelated pre-existing drift elsewhere in the tree; those changes were reverted to keep this PR docs/ledger-only per task scope.Risk and rollout
check:ledger-write-disciplineverifies the canonical-ledger diff exactly equals the recorded reconciliation transaction.docs/outstanding-issues-inbox/applied/for re-reconciliation if needed.Notes
RAG impact: no retrieval behaviour change — ledger reconcile only (docs-only edit to
docs/outstanding-issues.mdand its inbox; nosrc/lib/rag/**or retrieval/ranking/eval surface touched).Generated by Claude Code