monorepo-unit-test-validatorlisted

# Monorepo Unit Test Validator (PABX) Audit **unit test files** across the PABX monorepo (excluding backend/frontend) to ensure they comply with every rule the `monorepo-unit-test-writer` enforces. **Read-only:** produce a compliance report; never modify test/production files, never execute tests (static analysis only). > **Project scope:** PABX monorepo apps (not backend/frontend). The full rule set is in > **`../monorepo-unit-test-writer/references/pabx-rules.md`** — validate against it. **Scope:** any `apps/{app}` except backend/frontend. Stacks: `node-express`, `node-worker`, `python-fastapi`. ## INPUT - `test_file_path` (required) and `app_name` (required). - `checklist_file_path` (optional) — the `.unit-test.md` for coverage cross-reference. - `target_file` (optional) — the source under test. - `severity_filter` (optional) — `critical` | `major` | `minor` (default: all). ## OUTPUT A **compliance report** (English): summary counts, detected stack, 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`, stack, location, description, expected, found, fix), coverage/performance analysis, and positive findings. When dispatched by the evaluator, the **verdict** is the signal it consumes. --- ## EXECUTION STEPS (3 Phases) ### Phase 1 — Structural Analysis Detect the stack (`node-express` / `node-worker` / `python-fastapi`). Inventory t