unit-test-validatorlisted

# Unit Test Validator (PABX) Audit **unit test files** to ensure they comply with every rule the `unit-test-writer` enforces. **Read-only:** produce a detailed compliance report; never modify test or production files, never execute tests (static analysis only). > **Project scope:** PABX monorepo. The full rule set is in > **`../unit-test-writer/references/pabx-rules.md`** — validate against it. **Scope:** - **Frontend:** `apps/frontend/` — `*.spec.ts`, co-located with the source. - **Backend:** `apps/backend/__tests__/unit/` — `*.test.js`, mirroring `src/` (1:1). ## INPUT - `test_file_path` (required) — test file or directory to validate. - `checklist_file_path` (optional) — the `.unit-test.md` to cross-reference coverage. - `target_file` (optional) — the source under test, to verify coverage completeness. - `severity_filter` (optional) — `critical` | `major` | `minor` (default: all). ## OUTPUT A **compliance report** (English) with: summary counts by severity, applicable rule categories, overall verdict (`PASS` = 0 critical + 0 major; `PASS WITH WARNINGS` = 0 critical, some major/minor; `FAIL` = ≥1 critical), each violation (`[SEVERITY] Rule-ID`, location, description, expected, found, fix), coverage analysis, performance analysis (backend), and positive findings. When dispatched by the evaluator, the **verdict** is the signal it consumes. --- ## EXECUTION STEPS (3 Phases) ### Phase 1 — Structural Analysis Detect scope (frontend `.spec.ts` vs backend `.test.js`). I