# Self-Test Cases

Test cases for `/self-test`. The agent walks this file, verifies each case by
reading the actual code and/or running checks, and writes structured results to
`.ay/retros/agent-findings.json` ({test_id, description, status, evidence, ts}).

Format:
- One test case per `## T-NN <description>` heading.
- Under each heading, a `Check:` block lists the concrete things to verify.
- The agent decides `pass | fail | skip` per case and records evidence
  (a `file:line` reference, command output, or a short quote).

Edit these to describe what YOUR project must satisfy. The three below are
examples -- replace them.

## T-01 CLI entry point is wired
Check:
- `bin/` contains an executable entry script
- `package.json` "bin" (or equivalent) points at a file that exists
- The entry script has a shebang and is chmod +x

## T-02 Install is non-destructive
Check:
- The installer never overwrites an existing user config without merging
- Re-running the installer is idempotent (no duplicate entries created)
- Existing user keys/settings are preserved after install

## T-03 Docs match reality
Check:
- The command/feature count claimed in the README matches the actual file count
- Every command referenced in the docs has a corresponding file on disk
- No dead links to files that were renamed or removed