docs(issues): close stale #066/#067 after main landings

[BigSimmo]

Summary

Docs-only ledger sync after work already on main:

• Create node.js.yml #66 — archive: proven via PR Land streamlined six-item sidebar (#066) #1174 (4dc76306)
• Delete .github/workflows/label.yml #67 — archive: fixed via PR Fix scoped-label pagination and stabilize reconciliation preflight test #1191 in-process preflight (no timeout raise / lock bypass)
• Drop already-resolved Potential fix for code scanning alert no. 1: Workflow does not contain permissions #30/Refresh dependencies #75 from the recommended queue and renumber
• Soften #078 queue wording that still said “After #067”

RAG impact: no retrieval behaviour change — docs/outstanding-issues ledger only.

Verification

• Confirmed Land streamlined six-item sidebar (#066) #1174 and Fix scoped-label pagination and stabilize reconciliation preflight test #1191 merged on origin/main
• Confirmed tests/reconciliation-preflight.test.ts uses in-process collectReconciliationState()
• Ledger open/resolved/queue integrity asserts
• UI/provider gates not run: docs-only

Risk and rollout

• Risk: Low — ledger hygiene only
• Rollback: Revert the docs commits
• Provider or production effects: None

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[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]

Warning

Review limit reached

@BigSimmo, you've reached your PR review limit, so we couldn't start this review.

Next review available in:53 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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 Plus

Run ID: a2e53dc7-7e91-4d96-ba85-df3a16eba98c

📥 Commits

Reviewing files that changed from the base of the PR and between 0b4dccc and cf94bf8.

📒 Files selected for processing (2)

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cursor/ledger-066-067-519b

---

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.}