qalisted

# QA — Feature Regression Testing Run automated and interactive regression tests for a San feature based on its doc in `docs/features/`. ## Arguments - `<feature>` — Feature number (e.g. `01`, `6`) or filename stem (e.g. `6-hooks`, `cli-startup`). Partial matches are fine. - `--interactive` — Also run the interactive tmux tests (default: automated only). - `--pane` — For interactive tests, split a pane in the **current** tmux window instead of creating a separate session. This lets the user watch the test live side-by-side. If only a number is given, zero-pad and match against filenames (e.g. `1` → `1-cli-startup.md`). ## Workflow ### 1. Resolve the feature doc ``` docs/features/<N>-<name>.md ``` Read the file. Extract: - **Automated Tests** section — the `go test` commands and known test cases. - **Interactive Tests (tmux)** section — the step-by-step tmux script. If the feature cannot be found, list all available features and ask the user to pick one. ### 2. Build the binary Always build first so tests run against the latest code: ```bash make build ``` If the build fails, stop and report the error — no point running tests against stale code. ### 3. Run automated tests Execute every `go test` command listed in the feature doc's **Automated Tests** section. Capture stdout/stderr and exit codes. Each command is a separate test group. Record results as: - **PASS** — exit code 0 - **FAIL** — exit code non-zero; include the failure output ### 4. Run interactive