docs(ledger): record the post-merge verification of PR #2543

[BigSimmo]

Summary

• One immutable review record for claude/mockup-retirement-xw0vmn, scope prlanded, created by npm run ledger:append. No other file changes.
• PR Make the written record the gate on retiring a mockup, and retire seven #2543 merged as squash 374a5603. The prlanded check that matters here is content, not ancestry: git diff --stat 374a5603 4877a2e4 is empty, so every commit on the branch tip reached main and the auto-merge race orphaned nothing. That race has cost this repo a fix-forward before, which is why the record states the comparison rather than just the merge.
• The record's --head is the full 40-character squash SHA, not the branch tip, per the prlanded skill.

Verification

• npm run check:branch-review-ledger — 880 live table records + 1206 archived + 589 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 705c2f64a788..HEAD
• Branch cut fresh from origin/main at 705c2f64, carrying exactly one appended record and no canonical-ledger edit.

Verification not run: npm run verify:pr-local — the diff is a single added docs/branch-review-records/*.record.md file with no executable scope. The two gates above are the ones that govern this file, and both are green. .prettierignore deliberately excludes docs/branch-review-records/, because the filename is the SHA-256 of the row and reformatting breaks its own guard.

UI verification not run: no UI, routing, or styling surface is touched.

Not run: any provider-backed gate. None applies.

Risk and rollout

• Risk: None. The change is one new append-only documentation file.
• Rollback: git revert the single commit, or delete the record file.
• Provider or production effects: None
• RAG impact: none

Notes

Recorded outcome, verbatim from the row:

MERGED as #2543 squash 374a560; content diff against branch tip 4877a2e empty, no orphaned commits. Policy + check:mockups gate + seven mockup retirements (1403 added, 4330 deleted, 34 files). Three Codex P2 findings fixed and threads resolved; adversarial review withdrew two candidates.

Two things the record deliberately preserves rather than rounds off:

• check:dead-code-candidate refused that diff and is recorded as refusing. 64 of 201 candidates, every one a bare-symbol-name collision on a file-local identifier. No threshold and no refusal-list entry was changed to make it pass — the point of PR chore(cleanup): remove unused exports and add a dead-code safety gate #2204's post-mortem was that the diff yields to the gate, never the reverse.
• Advisory UI failed on several intermediate heads and was not this PR's. rankToolRecords("Risk & Safety") returned 3 where the test asserted 1, on catalogue files the branch never touched. Assert the ranking, not a tool count the Tools search mockup has rotted twice #2554 fixed it on main independently, and the lane is green on the merged head.

🤖 Generated with Claude Code

https://claude.ai/code/session_015UPvNZYvyuDxc1o7xfTGCS

---

Generated by Claude Code

---

Note

Low Risk
Append-only documentation under the branch-review ledger; no runtime, UI, or security-sensitive code paths change.

Overview
Adds one immutable append-only row in docs/branch-review-records/ (via ledger:append discipline), with no other file changes.

The record documents post-merge verification for branch claude/mockup-retirement-xw0vmn after #2543 landed as squash 374a5603. It states the content diff from that squash to branch tip 4877a2e4 is empty (no orphaned commits), summarizes the merged work (policy + check:mockups gate and seven mockup retirements), and captures CI/local gate outcomes—including that check:dead-code-candidate refused the original diff and was recorded without tuning thresholds.

^{Reviewed by Cursor Bugbot for commit ae00f06. Configure here.}

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

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: 85a10eb7-4bd6-4e04-9014-4b7165ae4274

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-03T00:13:17.196607Z	88cb478	Draft marked ready

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_aa0b67c8-0d4b-4613-9c20-125293024960)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_73a109bd-430c-42fb-8c7a-b60e023671d5)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_e1a1124b-17d1-4ce5-a37d-571f4197518f)