docs: correct Gate E PR state and backfill missing review records

[BigSimmo]

Summary

• docs/rag-improvement/HANDOVER.md §2 — the Gate E row's PR cell still read (this PR). The tooling actually merged as PR feat(eval): Gate E blinded before/after capture and pairing tooling (#E0N0QC) #2208, squash 588191c06d89db11c4458b03ebbb5fb7da0a1f15 (verified with git log/git show). Set the PR cell to #2208 and the state cell to Merged 2026-08-21 (squash 588191c), prefixed onto the existing sentence; nothing else in that row changed.
• docs/branch-review-records/ was missing a record for both PR docs(issues): reconcile the queued inbox batch into the canonical ledger #2218 and PR docs(worker): answer two of the four B4 operator unknowns from measured evidence #2228 (confirmed absent by grep -rl "#2218"/"#2228" and npm run ledger:lookup, which returned NOT REVIEWED at this HEAD and scope for both). Added one backfilled record for each via npm run ledger:append (never hand-written), citing each PR's own squash SHA, diff, and self-reported verification.

Verification

• npm run verify:pr-local — run scoped to the changed files (-- --files docs/rag-improvement/HANDOVER.md,docs/branch-review-records/d021712c...record.md,docs/branch-review-records/f97d90d5...record.md); classified as recognised low-risk docs scope, so lint/typecheck/full unit suite were skipped by design. Result:

  PR-local verification summary:
  - completed: check:runtime, check:installed-lock-parity, format:changed, sitemap:check, docs:check-index, docs:check-inventory, docs:check-scripts, docs:check-links, check:branch-review-ledger, check:outstanding-issues, check:ledger-write-discipline
  - failed: (none)
  - not reached: (none)
  Skipping build: no build-affecting source, config, package, or container changes detected.
  

• npm run check:branch-review-ledger — Branch review ledger guard passed: 880 live table records + 1206 archived + 438 immutable (880 under the 2026-07-29 machine-readable contract), immutable review writes, six cells each, no conflict markers, mojibake, heading records, or duplicates.
• npm run check:ledger-write-discipline — Ledger write discipline passed for 65393e4402ac..HEAD.
• npm run verify:ui — not run: no UI, routing, or styling changed.
• npm run verify:release, eval/production-readiness gates — not run: docs-only change, no retrieval/answer/clinical/deployment behaviour touched, and these are provider-backed.

Risk and rollout

• Risk: Low. Documentation and immutable review-record additions only; no src/, worker/, or supabase/ paths touched.
• Rollback: git revert the single commit.
• Provider or production effects: None.
• RAG impact: no retrieval behaviour change — documentation correction only.

Clinical Governance Preflight

Not applicable: this diff touches only docs/rag-improvement/HANDOVER.md and docs/branch-review-records/**. No ingestion, answer-generation, search/ranking, source-rendering, document-access, privacy, production-env, or clinical-output behaviour changed.

Notes

• Still owed: an uncommitted prlanded review-record file (docs/branch-review-records/0265c1cb….record.md) was left in the separate main checkout at D:/Repos/Database. This session did not touch that checkout (other sessions have work in progress there); flagging it here so it isn't lost. It should be committed and pushed from that checkout in a follow-up.
• Scope note: docs/outstanding-issues.md was not edited and issues:reconcile was not run, per this task's authorization boundary.

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your current included review allowance is based on your included PR review attempts over the past 7 days.

Next review available in:8 minutes

Limit details: You’ve used the included review currently available. Your 86 included PR review attempts over the past 7 days set your current allowance 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?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: d20237bc-1861-47bf-b116-1c6947751de7

📥 Commits

Reviewing files that changed from the base of the PR and between 65393e4 and bd53aea.

📒 Files selected for processing (3)

• docs/branch-review-records/d021712c69d85d2e42499fadabae91ada5396e3de2eb4652d748b09fae84ba8c.record.md
• docs/branch-review-records/f97d90d561a026c4d126c174fc5ab7882423a4f351a6158170f0ad2fa240c3c3.record.md
• docs/rag-improvement/HANDOVER.md

---

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

[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 ↗︎.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:bd53aea9bd

ℹ️ 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".

[chatgpt-codex-connector]

Record the PR head instead of the squash commit

When ledger:lookup is run for either feature branch, it resolves the branch's pre-merge PR head and requires both the ref and HEAD to match; these two backfills instead pair the branch refs with merge squash SHAs (02d1bca… and 1fe3c60…). Reproducing the documented lookup therefore returns NOT REVIEWED and reports the record only as belonging to a different HEAD, defeating review throttling. Append superseding records using each PR's actual reviewed head SHA rather than its squash commit.

AGENTS.md reference: AGENTS.md:L147-L147

Useful? React with 👍 / 👎.