senpi-qa

# Senpi QA QA the omo Senpi adapter (`packages/omo-senpi/`) and the task engine (`packages/senpi-task/`) by driving the REAL `senpi` binary. Unit tests never count as live QA here: `bun run test:senpi` is the package gate, the drivers in `packages/omo-senpi/scripts/qa/` are the harness proof. ## Golden rules - **Evidence lives at exactly one path.** Every artifact goes under `.omo/evidence/omo-senpi-adapter/<slug>/`. Pick it with `scripts/resolve-evidence-dir.mjs` and nothing else — a hand-typed path is how runs end up somewhere like `local-ignore/qa-evidence/`, which no reviewer reads and the PR cannot cite. - **The real agent dir stays untouched.** The live drivers build their own isolated `SENPI_CODING_AGENT_DIR` and deliberately IGNORE a caller-provided one, so `~/.senpi/agent` is never used as the sandbox. Report the driver's `realSenpiUntouched` / changed-path fields and the isolated agent-dir path; treat a whole-directory digest as supporting evidence, not proof by itself. - **No binary means SKIP, not silence.** When `senpi` is absent the live drivers report `SKIP` or `FAIL` in their final JSON rather than degrading to the real home. A `SKIP` is not a pass — say so in the evidence README. - **The captured JSON is the evidence.** No file on disk means the QA did not happen, which means no commit and no push. ## Resolve the evidence directory first ```bash ev="$(node .agents/skills/senpi-qa/scripts/resolve-evidence-dir.mjs \ --repo-root "$(g...