auditlisted

# Audit Run the 16-category code audit. ## Arguments - `$ARGUMENTS` — batch number (1-2) or `all` for full audit **`all` means run BOTH batches** — all 16 categories. Run batch 1, then batch 2, then triage all findings together. Do NOT stop after batch 1. ## Batches There are 16 categories split into 2 batches of 8. Each batch spawns 8 parallel agents (one per category). `all` runs both batches sequentially. | Batch | Categories | |-------|-----------| | 1 | Code Quality, Documentation, API Design, Error Handling, Observability, Test Coverage (adversarial), Robustness, Scaling & Hardcoded Limits | | 2 | Algorithm Correctness, Extensibility, Platform Behavior, Security, Data Safety, Performance, Resource Management, Test Coverage (happy path) | ## Process ### Setup 1. **Archive previous audit**: If `docs/audit-findings.md` or `docs/audit-triage.md` exist, rename both with the version suffix (e.g., `audit-findings-v0.9.1.md`, `audit-triage-v0.9.1.md`). Each audit starts with fresh files. 2. **Enable audit mode**: `cqs audit-mode on --expires 2h` — prevents stale notes from biasing review (no `-q` flag exists; the subcommand takes only `on`/`off` + `--expires`) ### Per-Batch 3. **Create team**: One team per batch (`audit-batch-N`) 4. **Spawn teammates**: One per category. Use `model: "fable"` for every auditor (per the 2026-06-11 model split: review/audit-finder lanes → fable) — the 2026-06-10 review/fix campaign showed Fable at or above opus quality on exactly thi