docs(ledger): record PR #1378 merge closeout

[BigSimmo]

Summary

• Append an exact-head docs/branch-review-ledger.md row for PR Remove document result overlays #1378 babysit closeout after required CI went green and squash auto-merge landed.
• No product, retrieval, or governance behavior changes.

Verification

• npm run check:branch-review-ledger — passed.
• Provider-backed / UI gates — not applicable (docs-only ledger append).

Risk and rollout

• Risk: None (append-only ledger row).
• Rollback: Revert this commit.
• Provider or production effects: None.

Clinical Governance Preflight

• Source-backed claims still require linked source verification before clinical use; no clinical UI or answer path changed.
• No patient-identifiable document workflow was introduced or expanded.
• Supabase target remains Clinical KB Database (sjrfecxgysukkwxsowpy); no Supabase configuration changed.
• Service-role keys and private document access remain server-only; no auth or access code changed.
• Demo/synthetic content remains clearly separated from real clinical sources.
• Source metadata and governance calculations remain unchanged.
• No clinical decision-support or deployment-classification behavior changed.

  

Summary by CodeRabbit

• Documentation
  • Updated the branch review ledger with the latest merge status, verification results, and review outcomes.
  • Recorded successful required checks, zero unresolved review threads, and no open automated findings.

[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: 11 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 @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: b2203ef7-fe8e-4cc5-bd16-d5b68e0163df

📥 Commits

Reviewing files that changed from the base of the PR and between 6644ddb and 7d60f15.

📒 Files selected for processing (1)

• docs/branch-review-ledger.md

📝 Walkthrough

Walkthrough

The branch review ledger now records PR #1378’s squash auto-merge, restored governance notice, removed overlays, successful checks, zero unresolved threads, no open Bugbot findings, and a passing verify:cheap 4273.

Changes

Branch review ledger

Layer / File(s)	Summary
PR #1378 merge record docs/branch-review-ledger.md	Adds the merge outcome and associated CI, review-thread, Bugbot, and verification results.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• BigSimmo/Database#810: Updates the same ledger with merge-babysit outcomes.
• BigSimmo/Database#830: Adds a related babysit outcome entry to the same ledger.
• BigSimmo/Database#856: Records related babysit and squash-merge details in the same ledger.

Suggested reviewers: cursoragent, claude, copilot

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise, specific, and accurately reflects the ledger closeout change.
Description check	✅ Passed	The PR body matches the template with Summary, Verification, Risk and rollout, and Clinical Governance sections filled in.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

_{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 ↗︎.

[BigSimmo]

@cursoragent Inspect the PR and repository state, identify the root cause of every failing CI check, unresolved review comment, merge conflict, and related defect. Apply the smallest robust fix using existing project patterns and best practices, without unrelated changes. Run Bugbot and all relevant lint, type-check, test, build, and CI-equivalent commands, fix any issues found, then resolve only the review comments that are fully addressed. Summarise the root causes, changes made, validation results, and any remaining blockers.

[cursor]

PR #1384 is merge-ready: mergeable_state: clean, required CI green, 0 unresolved threads.

Root causes

1. False “DIRTY” merge state — branch was behind main (ledger/design landings). git merge-tree was clean; GitHub was reporting staleness, not a content conflict.
2. Codex P2 — closeout row used pre-squash tip c3feb4ce…, which is gone after squash. ledger:lookup could not throttle on that SHA.
3. No failing CI / Bugbot findings — required checks were already green; Bugbot triage found 0 defect threads.

Changes

• Merged origin/main (repeated as main moved: feat(design): port Clinical Sky token system, elevation ladder and radius grid #1375/perf: cut fixed per-request round trips and add preamble Server-Timing #1376, docs(ledger): record PR #1379 babysit closeout #1382, Cover clinical calculator scoring and the batch image signed-URL route #1383).
• Appended superseding ledger row via ledger:append --supersede with resolvable squash SHA 6f2f1aa259ad7b554b3bac4e6c24adf2f8d28436.
• Replied to and resolved the Codex thread.

Tip: 820050fd · unique diff vs main: +2 lines in docs/branch-review-ledger.md.

Validation

Check	Result
check:branch-review-ledger	passed (1223 records)
ledger:lookup … --head 6f2f1aa2…	ALREADY REVIEWED
runtime / lock parity / format / lint / typecheck	pass
npm run test	4302 passed | 4 skipped
build / UI / provider gates	skipped (docs-only; not applicable)
Hosted PR required / Static / PR policy / CircleCI	pass

Remaining blockers

None for merge. Concurrent ledger PRs can push this branch behind again quickly — re-sync with origin/main if GitHub flips back to DIRTY/behind before squash.

  

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6644ddb189

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