Governance: record dirty-work consolidation reviews by BigSimmo · Pull Request #1363 · BigSimmo/Database

BigSimmo · 2026-07-28T12:03:59Z

Summary

Record the exact reviewed heads and dispositions for the three retained product branches using the repository ledger tool.

Sources reviewed

#1332, #1334, #1342, #1343, #1344, #1345, and #1358.

Retained

Only current-main-compatible append-only review history for this consolidation.

Rejected

Stale wholesale ledger snapshots, reused issue IDs, a second ledger authority, and incompatible hook/queue rewrites. The lookup/append tooling and issue #89 resolution are already on main and were not duplicated.

Verification

git diff --check
npm run check:branch-review-ledger: passed at 1150 records
npm run verify:cheap: passed; 412 test files, 4198 tests passed, 3 skipped

Not run

No hosted CI reruns or provider-backed checks.

Risk

Append-only documentation only; the union merge driver remains intact.

Summary by CodeRabbit

Documentation
- Added review records covering platform reliability, navigation overlays, and design mockup consolidation.
- Documented retained compatibility requirements, rejected regressions, and safety considerations.
- Clarified that experimental calculator and therapy-navigation work remains isolated from production experiences.
- Recorded an accessibility lint correction for a decorative icon.

supabase · 2026-07-28T12:04:05Z

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

coderabbitai · 2026-07-28T12:04:32Z

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:9 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: 745e0ddf-e6b8-489b-ba90-93f3cd5947e0

📥 Commits

Reviewing files that changed from the base of the PR and between 9cffcd9 and fe33ca7.

📒 Files selected for processing (1)

docs/branch-review-ledger.md

📝 Walkthrough

Walkthrough

Three ledger entries document approval outcomes for Codex consolidation reviews covering platform reliability, navigation overlays, and design mockups, including retained changes, rejected areas, and verification results.

Changes

Review ledger updates

Layer / File(s)	Summary
Add consolidation review entries `docs/branch-review-ledger.md`	Adds approval records for three Codex consolidation reviews and documents their retained, rejected, and verified changes.

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

Possibly related PRs

BigSimmo/Database#719: Updates the same branch review ledger with review records.
BigSimmo/Database#870: Appends related review outcomes to the ledger.
BigSimmo/Database#903: Documents dirty-work and cleanup review decisions in the same ledger.

Suggested reviewers:cursoragent

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately reflects the main change: recording consolidation reviews in governance docs.
Description check	✅ Passed	The description covers summary, sources, retained/rejected scope, verification, and risk, so it is mostly complete.
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.}

coderabbitai

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/branch-review-ledger.md`:
- Around line 1193-1195: Update the verification summaries in the ledger rows
for codex/consolidate-platform-reliability,
codex/consolidate-navigation-overlays, and codex/consolidate-design-mockups so
each row clearly scopes its own verify:cheap counts and does not imply one
shared final run. Identify check:github-actions as a local validator rather than
a hosted/provider-backed check, and if recording a single final run, replace the
mixed counts with that run’s exact output.

🪄 Autofix (Beta)

❌ Autofix failed (check again to retry)

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: c0b26e84-f204-452d-9a36-4abe47208af1

📥 Commits

Reviewing files that changed from the base of the PR and between 18bed6d and 9cffcd9.

📒 Files selected for processing (1)

docs/branch-review-ledger.md

BigSimmo · 2026-07-28T13:42:14Z

@cursoragent resolve Merge conflict

cursor · 2026-07-28T13:42:23Z

Merge conflict on #1363 is resolved.

GitHub’s CONFLICTING state was staleness (branch was 5 commits behind main), not a content fight — git merge-tree was clean. I merged origin/main and pushed.

Commit:fe33ca75 — Merge origin/main into codex/consolidate-ledger-governance
PR status:MERGEABLE (checks re-queued; still BLOCKED until they finish)
Ledger: auto-merged; check:branch-review-ledger passed (1163 records)

coderabbitai · 2026-07-28T13:42:29Z

Note

Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it.

❌ Cannot run autofix: This PR has merge conflicts.

Please resolve the conflicts with the base branch and try again.

Alternatively, use @coderabbitai resolve merge conflict to automatically resolve the conflicts.

Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

docs: record dirty-work consolidation reviews
9cffcd9

coderabbitaiBot reviewed Jul 28, 2026
View reviewed changes

Comment threaddocs/branch-review-ledger.md

This was referenced Jul 28, 2026
chore: activate universal ledger ownership updates #1358
Closed
docs(ledger): open-PR usefulness triage #1367
Merged

BigSimmo enabled auto-merge (squash) July 28, 2026 13:41

Merge origin/main into codex/consolidate-ledger-governance
fe33ca7
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

BigSimmo merged commit 3924b55 into mainJul 28, 2026
19 checks passed

BigSimmo deleted the codex/consolidate-ledger-governance branch July 28, 2026 13:46

Navigation Menu

Governance: record dirty-work consolidation reviews - #1363

Governance: record dirty-work consolidation reviews#1363
BigSimmo merged 2 commits into
mainfrom
codex/consolidate-ledger-governance

BigSimmo commented Jul 28, 2026•
edited by coderabbitai Bot
Loading

Uh oh!

supabaseBot commented Jul 28, 2026

Uh oh!

coderabbitaiBot commented Jul 28, 2026•
edited
Loading

Review limit reached

Walkthrough

Changes

Uh oh!

coderabbitaiBot left a comment •
edited
Loading

Uh oh!

Uh oh!

BigSimmo commented Jul 28, 2026

Uh oh!

cursorBot commented Jul 28, 2026•
edited
Loading

Uh oh!

coderabbitaiBot commented Jul 28, 2026•
edited
Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

BigSimmo commented Jul 28, 2026• edited by coderabbitai BotLoading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Sources reviewed

Retained

Rejected

Verification

Not run

Risk

Summary by CodeRabbit

Uh oh!

supabaseBot commented Jul 28, 2026

Uh oh!

coderabbitaiBot commented Jul 28, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review limit reached

Walkthrough

Changes

Uh oh!

coderabbitaiBot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

BigSimmo commented Jul 28, 2026

Uh oh!

cursorBot commented Jul 28, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitaiBot commented Jul 28, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

BigSimmo commented Jul 28, 2026•
edited by coderabbitai Bot
Loading

coderabbitaiBot commented Jul 28, 2026•
edited
Loading

coderabbitaiBot left a comment •
edited
Loading

cursorBot commented Jul 28, 2026•
edited
Loading

coderabbitaiBot commented Jul 28, 2026•
edited
Loading