docs: check in the advisor plans and their outcome record

[oekazuma]

Summary

Checks in the plans/ directory — the implementation plans generated by the 2026-07-05 code-health audit, all now executed and merged (#114, #116–#119, #124–#127, #129, #131).

The durable value is plans/README.md:

• Execution record: what each plan did, which PR shipped it, and the non-obvious problems found along the way (pnpm 11's devEngines/lockfile behavior, vitest transforming in-process dynamic imports, etc.) with enough context to be useful later.
• Findings considered and rejected: audit findings that were deliberately not acted on, with rationale — so a future audit doesn't re-report them (DEBT-02 head-tag duplication, the perf/performance rule-directory split, and others).
• Direction notes: options recorded for future consideration (--fix policy, baseline/suppression files, the vite live-UI dashboard, MCP extensions).

The individual plan files (001–011) are the historical record of how each change was specified and verified.

All files are prettier-formatted so pnpm lint stays green. No code, no changeset.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 45 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 69304b37-b224-4bab-94f9-85463aa400d6

📥 Commits

Reviewing files that changed from the base of the PR and between 1fcaecb and 667ccfa.

📒 Files selected for processing (12)

• plans/001-diff-staged-path-mismatch.md
• plans/002-malformed-svelte-characterization.md
• plans/003-dedupe-collect-component-facts.md
• plans/004-agents-md.md
• plans/005-node-engines-floor.md
• plans/006-dev-ui-hardening.md
• plans/007-route-parse-cache.md
• plans/008-config-file-design-spike.md
• plans/009-enforce-core-purity-lint.md
• plans/010-config-file-implementation.md
• plans/011-config-file-docs.md
• plans/README.md

---

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