Inspect managed link type, relative target, real target, ownership, and security-sensitive modes without reading credential contents.
Drive the installed tool through its public CLI at least twice. Confirm reported config/data paths and that repeated use does not recreate a legacy real directory or split state.
When a compatibility symlink is intentional, probe once with the environment override unset and confirm the reported legacy path resolves to the same real file.
On macOS, compare launchctl getenv VARIABLE with the shell value when bootstrap publishes it.
Run ./bootstrap.sh --doctor and report unrelated failures separately; run ./bootstrap.sh --dry-run --only symlinks to observe managed-link convergence without changing state.
Finish with git diff --check for the touched paths. Do not run the repository test suite as runtime verification.