[howonlee]

Validate VULN-566 trust and cache follow-ups.

[linear]

VULN-566

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

This pull request updates repository approval documentation and adds Bats integration tests for retained Git directories and legacy startup caches. The tests cover CLI, Bash, Zsh, and Fish behavior. The follow-up documentation records validation, version history, and scope boundaries.

Changes

Repository Trust Follow-ups

Layer / File(s)	Summary
Retained Git directory trust docs/configuration.md, docs/security-vuln-566-followup.md, tests/trust_followup.bats	The documentation distinguishes replacing a common Git directory from replacing its contents. Integration tests check hook execution when the directory is retained and check that changing hook configuration produces no result.
Legacy startup-cache validation docs/security-vuln-566-followup.md, tests/trust_followup.bats	The documentation records old-cache behavior, version history, migration steps, and validation boundaries. Tests check whether a legacy startup marker appears before cache regeneration and is absent afterward.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Change: Other

Suggested reviewers: natoboram

Merge Risk: Minimal · up to d1fa0

The approval guidance and regression tests clarify existing trust and cache behavior; no merge-blocking issue is established.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly describes the pull request’s main change: tests that validate VULN-566 trust follow-ups.
Docstring Coverage		Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 2 functions across 1 files. (2 skipped: 2 unsupported.)

Finishing Touches

Generate docstrings

• Commit to this branch
• Create a new PR

Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{A rabbit checks the hooks at play
While Git keeps identity its way
The shells all test the cache anew
Old startup markers vanish too
The bunny hops through tests in view}

Recent review info

Run configuration

• Source mode: Auto
• Repository: coderabbitai/git-worktree-runner
• Branch: main
• File: .coderabbit.yaml
• Commit: fc8afc0
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Enterprise
• Run ID: 6fbfffd2-2d29-4ca7-8c0d-690dff1e3f73

Commits

Reviewing files that changed from the base of the PR and between fc8afc0 and d1fa00e.

Files selected for processing: 3

• docs/configuration.md
• docs/security-vuln-566-followup.md
• tests/trust_followup.bats

Included review availability: This review used your included allowance. Your plan provides up to 100 included reviews per hour; 98 remain after this review.