ux-auditlisted

# ux-audit — Scenario Audit Loop > Part of **super-ux** — see [system-map.md](references/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](references/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. **Full context:** when `docs/ux/foundation.md` exists, audit each scenario WITH its chain — load the traced story's acceptance criteria (Given/When/ Then) as additional checks, and note whether the implementation actually serves the job and journey stage, not just renders the elements. A flow whose buttons all exist but whose job outcome is unreachable is PARTIAL at best. When `docs/ux/flows.md` exists, also verify the code implements the flow diagram: every node reachable, every edge (including error edges) wired, screen states from the flow's table present — unimplemented nodes/edges are findings on the traced scenarios. #