issues: close #087 — the knip failure was a worktree-install false positive

[BigSimmo]

Closes #087 in docs/outstanding-issues.md as not a defect.

The reported findings — unused devDependencies rimraf / tsx / @testing-library/dom, and playwright-core unlisted across scripts/capture-chrome-parity.ts and four tests/ui-*.spec.ts — only appeared because the worktree had no node_modules of its own, so tooling resolved from the parent checkout.

After npm ci in the same worktree, npm run check:knip exits 0 with no ignore-list change and no dependency edit.

The archived row keeps the durable lesson: never act on a knip finding from a worktree that has not been installed.

One row moved from Open items to Resolved / archive. No code, config, or dependency change.

🤖 Generated with Claude Code

[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

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:34 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: 566c6dab-e5b1-4087-b669-5baf4d600f2b

📥 Commits

Reviewing files that changed from the base of the PR and between 8917466 and 81ae7de.

📒 Files selected for processing (1)

• docs/outstanding-issues.md

---

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

[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 #1340 was already healthy and landed while under inspection. No product defect, failing check, merge conflict, or review thread needed a fix.

Root causes

Area	Finding
Failing CI	None. Early BLOCKED was pending Static PR checks; then PR required / Static / Semgrep / Gitleaks all SUCCESS. Unit/Build/UI correctly skipped (docs-only).
Review threads	None. Bugbot/cursor[bot]: no findings.
Merge conflicts	None — 0 behind / 1 ahead; merge-tree clean.
Related defect	Auto-merge race: #1340 squash-merged as f39ca98a mid-babysit, orphaning a late ledger append.

Changes made

• Revalidated #087 claim: npm run check:knip exits 0 after install.
• Fix-forwarded the orphaned ledger rows → draft #1341 (cursor/pr1340-ledger-prlanded-c9d2).
• No product/code/dependency edits on issues: close #087 — the knip failure was a worktree-install false positive #1340 (none needed).

Validation

• Hosted issues: close #087 — the knip failure was a worktree-install false positive #1340: PR required SUCCESS; Static PR checks SUCCESS.
• Local: check:runtime, lock-parity, lint, typecheck, format:changed, docs:check-links, docs script-refs, check:knip, check:branch-review-ledger — all pass.
• prlanded: two-dot squash vs product tip empty; only ledger was orphaned.

Remaining blockers

• None for issues: close #087 — the knip failure was a worktree-install false positive #1340 (already on main).
• docs(ledger): record PR #1340 babysit and prlanded #1341 is draft docs-only; CI still settling.
• Cleanup candidate (not deleted): remote claude/close-knip-false-positive still points at the orphaned tip.