docs: record the 2026-08-08 audit plans and execution results (043–047)

[oekazuma]

Summary

Commits the planning record from the 2026-08-08 deep audit (run at 9e0cf9e), following the precedent of #216:

• The five implementation plans (plans/043–047) that shipped as fix(cli): reject flag-shaped and empty values on string flags #397–fix(vite): fail the build on an invalid config file instead of skipping the gate #401 (all merged), each with its executor's review outcome recorded in the index.
• The audit's vetted backlog ("next selection candidates", leverage-ordered), rejected findings with evidence (so they aren't re-audited), and direction notes — including the correction that the lang: 'ja' i18n spike was never accepted, and the cross-repo follow-up for svelte-vitals-action (applyScope callers must pass loadedConfig, see fix(cli): analyze the baseline under the current checkout's config instead of re-loading it in the worktree #400).

Documentation-only; no changeset needed.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Added detailed implementation plans covering CLI validation, Git changed-file handling, TypeScript rune analysis, baseline configuration reuse, and Vite configuration errors.
  • Documented audit results, implementation status, review outcomes, and follow-up candidates for plans 043–047.
  • Included testing, verification, scope, and maintenance guidance for each planned change.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 51 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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 Plus

Run ID: c25581eb-c3dc-490c-91e3-22fbf75d73ff

📥 Commits

Reviewing files that changed from the base of the PR and between 0c33b8d and 19321f4.

📒 Files selected for processing (6)

• plans/043-string-flag-value-guard.md
• plans/044-git-changed-files-z.md
• plans/045-ts-wrapper-rune-facts.md
• plans/046-baseline-config-once.md
• plans/047-vite-config-error-handling.md
• plans/README.md

📝 Walkthrough

Walkthrough

Adds five implementation plans for CLI validation, Git path handling, rune fact collection, baseline configuration reuse, and Vite config errors. Updates the plans index with audit status, dependencies, rejected findings, and future follow-up observations.

Changes

Implementation Plans

Layer / File(s)	Summary
CLI behavior plans plans/043-string-flag-value-guard.md, plans/044-git-changed-files-z.md	Documents string-flag validation and NUL-delimited Git path handling, including tests, verification, release steps, and scope limits.
Analysis integration plans plans/045-ts-wrapper-rune-facts.md, plans/046-baseline-config-once.md, plans/047-vite-config-error-handling.md	Documents planned changes for rune parsing, baseline configuration reuse, and Vite configuration error handling.
Audit status and follow-up record plans/README.md	Records the five plans, their dependencies, unplanned findings, rejected findings, and direction-only observations.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• oekazuma/svelte-vitals#73: Plan 044 extends the changed-file handling addressed by this PR.
• oekazuma/svelte-vitals#260: Plan 047 overlaps the Vite analysis and configuration flow.
• oekazuma/svelte-vitals#397: Plan 043 documents the CLI string-flag validation changes.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the documentation changes that record the 2026-08-08 audit plans and execution results for plans 043–047.
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.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

---

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

[coderabbitai]

Actionable comments posted: 2

🤖 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 `@plans/044-git-changed-files-z.md`:
- Around line 31-33: Update the fenced code example in the documentation to
specify the text language identifier, preserving the octal-escaped path content
unchanged so it satisfies markdownlint MD040.

In `@plans/README.md`:
- Around line 113-116: Resolve the contradiction between the Plan 039 entry and
the 2608-DIR-01(i18n) note: update the older Plan 039 status to reflect that the
spike remained Proposed, or explicitly clarify that only the PR was accepted
while the spike was not. Keep the audit history internally consistent without
changing unrelated plan records.

🪄 Autofix

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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: cc4a9713-ae07-46d9-a2a5-d8b26639b55a

📥 Commits

Reviewing files that changed from the base of the PR and between ce5fdf7 and 0c33b8d.

📒 Files selected for processing (6)

• plans/043-string-flag-value-guard.md
• plans/044-git-changed-files-z.md
• plans/045-ts-wrapper-rune-facts.md
• plans/046-baseline-config-once.md
• plans/047-vite-config-error-handling.md
• plans/README.md