ux-audit — Scenario Audit Loop

Part of super-ux — see system-map.md for the whole pipeline and the four sync rules. Start any audit by running the linter (python3 docs/ux/lint.py) — it catches structural drift for free before the code-tracing passes.

Verify that the code actually delivers every scenario in docs/ux/scenarios.md: every step reachable, every button present, every state handled, every error honest. Output: a versioned report in docs/ux/audits/ plus updated audit statuses in the base.

Format contract: scenario-format.md (ux-contract v4) — report structure, verdicts (PASS / PARTIAL / FAIL / BLOCKED), severities.

Precondition: docs/ux/scenarios.md exists. If it doesn't, stop and run the ux-scenarios skill first — there is nothing to audit against.