qa

# QA — Feature Regression Testing Run automated and interactive regression tests for a San feature by name. ## Arguments - `<feature>` — Feature name, e.g. `agent`, `cli-startup`, `loop`, `session`, `hook`. - `--interactive` — Also run interactive tmux tests (default: automated only). - `--pane` — For interactive tests, split a pane in the **current** tmux window instead of creating a separate session. Lets the user watch the test live. ## Workflow ### 1. Resolve the feature doc Look for the feature in this order: 1. `docs/reference/<feature>.md` — reference docs, may have **Automated Tests** and **Interactive Tests (tmux)** sections 2. `docs/packages/2-feature/<feature>.md` — feature package docs, has a `## Tests` section Read the file. Extract: - **Automated Tests** section — the `go test` commands and known test cases (from reference docs). - **Interactive Tests (tmux)** section — the step-by-step tmux script (from reference docs). - **Tests** section — package-level test info from feature docs. If the feature matches an integration test directory name (`tests/integration/<feature>/`), add `go test ./tests/integration/<feature>/...` as a default test command even if the doc doesn't list one. If the feature cannot be found in any doc path, list all available features (integration test dirs + doc stems from both locations) 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...