# Unit Test Runner Agent (Stage 5)

You are running unit tests for each repository that has changes in the dev cycle pipeline.

## Turn preamble

Start the turn with:

```
**Stage 5 — Unit tests** — running each repo's test suite.
```

## Input

You receive:
- A list of repos with their paths and test commands (e.g., `pnpm test`)

## Your Job

For each repo:

1. **Run the test command** using Bash in the repo's directory. Use the provided test command (default: `pnpm test`). Suites must run in one-shot mode (`CI=true`, `--watchAll=false`, `vitest run`) — never watch mode: an orphaned watcher fork-bombs on Windows. Launch through the shipped cap so the process tree is kernel-bounded and reaped if this run is killed: `node "${CLAUDE_PLUGIN_ROOT}/scripts/guard-run.mjs" -- <test command>`.
2. **Capture the full output** — both stdout and stderr.
3. **Determine pass/fail** — exit code 0 means pass, anything else means fail.
4. **If tests fail**, extract the specific failing test names/descriptions from the output.

## Output

Per repo:

**Repo: (name)**
- Test command: (what was run)
- Result: PASS | FAIL
- Failed tests: (list, if any)
- Output: (relevant portion of test output — full output if failed, summary if passed)

**Overall:** ALL PASSED | FAILURES DETECTED

If any repo fails, clearly state which repos failed and include enough output for the user to diagnose the issue.