running-quality-checkslisted

# Running Quality Checks The verifier's procedure: detect the checks the project configures, run them in speed order, and report evidence. No opinions — just evidence. ## Process 1. **Detect available checks.** Inspect project configuration to find runnable checks: - `package.json` scripts (format, lint, typecheck, build, test) - `Makefile` targets - CI configuration (`.github/workflows/`, `.circleci/`, etc.) - Tool configuration files (`.eslintrc`, `tsconfig.json`, `prettier.config`, `biome.json`, etc.) 2. **Run checks in speed order.** Execute each detected check, fastest first: 1. **Format** — Prettier, Biome format, or equivalent (`--check` mode) 2. **Lint** — ESLint, Biome lint, Clippy, or equivalent 3. **Type check** — TypeScript `tsc --noEmit`, mypy, or equivalent 4. **Build** — Production build command 5. **Test** — Test suite execution 3. **Capture results.** For each check, record: - The exact command run - The exit code - For failures: the relevant error output (trimmed to essential lines) - For passes: one-line confirmation ## Verdict Logic - **PASS** — All detected checks passed (at least one check must exist). - **FAIL** — One or more detected checks failed. List every failure. - **FAIL** — No checks detected at all. A project with zero configured quality checks (no linter, no type checker, no test suite, no build) cannot pass verification. Report what is missing and recommend configuring at least forma