ultra-test

# ultra-test — Phase 3.5 Project-level quality audit before `/ultra-deliver`. Auditors are orthogonal; each writes a JSON gate result; the skill aggregates into `.ultra/test-report.json`. This is **not** for running unit tests (that is `/ultra-dev`). This is the pre-ship gate. ## Authority failure boundary The completed-task precheck requires MCP `task.list`. If it is unavailable or returns an authority error, stop the audit. Never fall back to `.ultra/tasks/tasks.json`. For `LEGACY_STATE_MIGRATION_REQUIRED`, instruct `ultra-tools migrate --from=4.4 --to=4.5 --source-dir <project-root>`. ## Prerequisites - `task.list` returns ≥1 task with `status=completed` - Repo has test files (Step 0 pre-check) ## Workflow ### Step 0 — Pre-Execution 1. Detect project type from config (`package.json` / `Cargo.toml` / `go.mod` / `pyproject.toml` / …) 2. `task.list { status: "completed" }` → confirm ≥1 task delivered 3. Find test files (suffix `.test.*`, `.spec.*`, `test_*.py`, `*_test.go`) Block with instructive error if any precheck fails. ### Step 1 — Anti-Pattern Detection Detect fake / meaningless tests that waste CI time. | Pattern | Example | Severity | |---------|---------|----------| | Tautology | `assert True`, `expect(true).toBe(true)` | CRITICAL | | Empty test | function body is just `pass` / `{}` | CRITICAL | | Core-logic mock | `jest.mock()` on domain/service/state files | CRITICAL | Use Grep with language-appropriate regex; count matches per file. **Gate**: any CR...