system-audit-reviewlisted

# System Audit Review Use this skill to produce decision-grade reviews rather than generic code commentary. Read [references/audit-protocol.md](references/audit-protocol.md) for the method and [references/audit-contract.md](references/audit-contract.md) for the machine-checkable report contract before starting the audit. ## Operating Model Three tiers, with an explicit split between what is machine-enforced and what is advisory: - **Brain (prose)** — this file and the protocol. Advisory: you follow it. - **Sensors (`scripts/probes/`)** — read-only scripts that *generate facts* as JSON. Enforced: evidence is real tool output, not recall, and `--reproduce` re-runs them to diff target-state fields. Six sensors cover layers 1-6, and each one can call EXTERNAL analyzers declared in `scripts/configs/detectors.json` (`node --check`, `tsc --noEmit`, `semgrep`, `gitleaks`) — adding a language or tool is one JSON entry, never a code change: `census` (footprint), `git_state` (`.git` as data), `config_drift` (config variant families, stale artefacts, schedulers; vendor trees excluded), `dep_surface` (manifests, tests, Python syntax), `sink_scan` (side-effect inventory), `scan_orchestrate` (gitleaks). Layer 7, negative space, has no sensor. A probe never assumes its containment and never reports full coverage after a truncated walk. - **Gate (`scripts/audit_gate.py`)** — scores your report against the contract AND reconciles it against the probe payloads. It reads ENUMS, NUMBERS, and