issues: capture the unreadable-CI token, at-risk worktree work, and the unpushed hook fix

[BigSimmo]

Summary

Ledger-only. Three findings from the 2026-07-30 organisation session were recorded nowhere durable — they existed solely in chat context, which is exactly what docs/outstanding-issues.md exists to prevent.

• #149 — CI verdicts are unreadable with the current GitHub token. The session PAT lacks Checks: Read. gh pr checks fails per context and /check-runs returns 403; /commits/:sha/statussucceeds but reports total: 0, because this repo reports through Actions check-runs rather than legacy commit statuses. The working endpoint is therefore silent rather than erroring, which reads like "no checks" instead of "no permission". Both docs: file loose dated records and close the docs index gaps #1436 and docs: close stale hook and script-count records #1458 were handed off with every local gate green and the hosted verdict unverifiable. Fix is a permission on the token; nothing in the repo changes.

• #150 — uncommitted work in worktrees whose branches are already merged. Four of them, so the changes exist in no branch and no PR: codex/reconcile-immediate-20260730 (+395/-200 across 19 files, including .github/workflows/ci.yml and package.json), codex/document-results-mockup-20260730, codex/chat-ledger-triage-d344, and claude/section-spy-browser-coverage. Recorded rather than actioned, because each needs a per-worktree commit-or-discard decision. This is also the check that stopped the 2026-07-30 cleanup from removing more than one of its two "safe" candidates.

• #151 — the #143 pre-commit fail-open exists only on a never-pushed branch.git branch -r --contains d2fd16d54 is empty. That branch is additionally 17 behind main and conflicts on docs/scripts-index.md, since main has landed both the rewritten index and the docs:update generator that owns its count sentence.

Verification

• npm run check:outstanding-issues — 149 rows (60 open, 89 archived), unique ids, next-id=152 above the highest
• npm run docs:check-links — 1415 repo path references resolve (first run failed on one path: #150 originally named an untracked mockup file that does not resolve in this repo, so it is now named without a full path)
• npm run docs:check-index — coverage OK: all 49 repository roots/modules/routes and all schema tables are indexed
• Prettier — clean, in the unpadded table style Stop Prettier padding the issues ledger table, closing #133 #1479 established

Rows follow the compact post-#1479 format; no other file is touched.

Note on #1458

#1458 is now redundant and should be closed rather than merged: main landed the same repo-root coverage pass in #1480 (same root kind, same ${name}/ candidate, same allowlist handling, same message, same all 49 result), the docs:update generator supersedes its hand-corrected counts, and its CLAUDE.md wording is already on main verbatim. Closing a PR needs owner confirmation, so it is left open.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated the branch-review ledger with new follow-up review records for outstanding capture-session items, including CI token permission constraints, worktree/uncommitted-change tracking, and a pre-commit-hook fix note.
  • Reordered and reconciled related entries to improve clarity on which PRs/issues own each portion of the review and to correct main-sync archival details.
  • Advanced the outstanding-issues sequence and added new open items for unreadable CI verdicts and preserved-but-uncommitted worktree changes.
  • Refreshed resolved/archive wording to reflect the corrected scope and remaining snapshot text.

[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:33 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: a6081725-1f8c-42f4-8cf9-b8ad90225898

📥 Commits

Reviewing files that changed from the base of the PR and between ad71cf2 and 9a356b4.

📒 Files selected for processing (2)

• docs/branch-review-ledger.md
• docs/outstanding-issues.md

📝 Walkthrough

Walkthrough

The PR updates outstanding-issue records for CI token access and preserved worktree changes, clarifies pre-commit-hook issue resolution, and appends corresponding branch review ledger reconciliation and follow-up records.

Changes

Issue Ledger Reconciliation

Layer / File(s)	Summary
Outstanding issue records docs/outstanding-issues.md	Advances the next issue ID to 154, adds open issues #152 and #153, and updates the archived records for #143 and #151.
Capture-session reconciliation docs/branch-review-ledger.md	Records CI token limitations, preserved worktree changes, the issue #148 deletion guard, and ownership corrections for issues #143 and #151.
Main-sync follow-ups docs/branch-review-ledger.md	Records issue closure and archiving, ID-collision renumbering, snapshot wording clarification, and the relocated PR #1433 review entry.

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

Possibly related PRs

• BigSimmo/Database#1410: Adds validation for the same outstanding-issues ledger structures updated here.
• BigSimmo/Database#1302: Updates the same monotonic issue ID tracking mechanism.
• BigSimmo/Database#1458: Overlaps with the issue #143 and branch-review ledger corrections.

Suggested reviewers:claude, cursoragent

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately summarizes the main ledger updates about unreadable CI, at-risk worktrees, and the hook fix.
Description check	✅ Passed	The description covers summary and verification well, but the template's Risk/Rollout and Notes sections are only partially filled or implicit.
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.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:bbc5d4625a

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

[coderabbitai]

Actionable comments posted: 3

🤖 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`:
- Line 264: Update the PR `#1458` wording in the ledger entry to state that it
should be closed after owner confirmation, preserving the surrounding
reconciliation details and avoiding an unconditional closure instruction.
In `@docs/outstanding-issues.md`:
- Line 158: Update the issue `#149` documentation entry to remove the partial
`github_pat_11AU2...` credential prefix, while retaining the generic
“fine-grained PAT” description and all unrelated troubleshooting details
unchanged.
- Around line 158-160: Update the dates for ledger rows `#149`, `#150`, and `#151`,
plus the “CORRECTED” date associated with `#143`, so they reflect the documented
July 30, 2026 capture/reconciliation unless a later event is explicitly
recorded. Preserve the audit chronology and ensure no July 31 date remains
unsupported by the entry’s event details.

🪄 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: b4da99c3-ff0e-4be3-a032-b2518836f24c

📥 Commits

Reviewing files that changed from the base of the PR and between ee34b4d and 5af405b.

📒 Files selected for processing (2)

• docs/branch-review-ledger.md
• docs/outstanding-issues.md

[BigSimmo]

@cursoragent resolve failing CI, comments and merge conflict

[cursor]

PR #1490 is green and mergeable at 55cc3f91.

• Merged current main (including fix(hooks): fail open when the inventory script is absent from the worktree #1494 and Close #130 by decision; capture the stale-install and reviewer-coverage gaps #1496)
• Fixed an ID collision: Close #130 by decision; capture the stale-install and reviewer-coverage gaps #1496 had reused #149/#150, so this capture’s open rows are now #152 (Checks: Read) and #153 (merged-worktree WIP); #151 archived via fix(hooks): fail open when the inventory script is absent from the worktree #1494; #143 fully resolved
• Review threads were already addressed
• CI: PR mergeability / Static PR checks / PR required all pass; merge state CLEAN

Did not merge into main.

[coderabbitai]

Note

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

Autofix skipped. No unresolved CodeRabbit review comments with fix instructions found.

[cursor]

Resolved on 55cc3f91:

• Merged current main (including fix(hooks): fail open when the inventory script is absent from the worktree #1494 fail-open and Close #130 by decision; capture the stale-install and reviewer-coverage gaps #1496).
• ID collision:Close #130 by decision; capture the stale-install and reviewer-coverage gaps #1496 reused #149/#150 for different findings. Kept those; renumbered this capture’s open rows to #152 (CI Checks: Read) and #153 (merged-worktree WIP); archived #151 via fix(hooks): fail open when the inventory script is absent from the worktree #1494; #143 marked fully resolved across chore(docs): automate documentation synchronization #1442+fix(hooks): fail open when the inventory script is absent from the worktree #1494.
• Review threads were already addressed on earlier heads.
• CI now green: PR mergeability pass, Static PR checks pass, PR required pass; mergeable CLEAN.

Did not merge the PR into main.

[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/outstanding-issues.md`:
- Line 158: Clarify the `#153` entry that each branch was already fully merged
into origin/main before its preservation snapshot commit was created.
Distinguish the pre-snapshot merged state from the current branch tips, which
now contain unpushed WIP commits and therefore are not fully merged; update the
cleanup guidance to inspect and preserve those snapshot commits before deleting
worktrees.

🪄 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: e052568d-c493-4204-9781-25b048a57d17

📥 Commits

Reviewing files that changed from the base of the PR and between 5af405b and 55cc3f9.

📒 Files selected for processing (2)

• docs/branch-review-ledger.md
• docs/outstanding-issues.md

[coderabbitai]

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.

[BigSimmo]

@cursoragent resolve merge conflict

[cursor]

Merge conflict resolved on ad71cf29.

Local merge-tree was already clean — GitHub’s DIRTY was merge=ledger staleness. Merged origin/main (9af15e1f); #152/#153 kept (including the snapshot wording fix). PR is MERGEABLE again and PR mergeability passed.

[cursor]

Resolved merge conflict on ad71cf29 by merging origin/main (9af15e1f).

Local git merge-tree was already clean — GitHub DIRTY was the usual merge=ledger staleness on docs/branch-review-ledger.md. Kept #152/#153 (including the pre-snapshot wording fix) and main’s archived CI/#132 closeouts. check:outstanding-issues and docs:check-links pass; PR is MERGEABLE again.

[BigSimmo]

Temporarily paused during the owner-authorized ordered merge sweep so main cannot move between exact-head review and merge. The branch and all commits are preserved; this PR will be reopened at its verified place in the queue.

[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 resolve merge conflicts please and fix CI failure

[cursor]

Merge conflict resolved and CI is green — PR #1490 also merged at 9a356b4f.

What was wrong
Real conflict in docs/outstanding-issues.md: main had already re-landed the same findings via #1508 under different IDs (#151/#152/#153), while this branch still had its older #152/#153 rows.

Resolution

• Kept main’s ID scheme (#151 CI/Actions, #152 worktrees, #153 archived pre-commit)
• Kept this PR’s clearer pre-snapshot wording on #152
• Pointed archived #143 at #153 (not open #151)
• Dropped the duplicate archived #151 pre-commit row

Checks

• check:outstanding-issues — passed (151 rows … next-id=154)
• docs:check-links — passed
• Hosted: PR mergeability / Static PR checks / PR required all pass

[coderabbitai]

Note

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

Autofix skipped. No unresolved CodeRabbit review comments with fix instructions found.