/click-path-audit — Behavioural Flow Audit

Find bugs that static code reading misses: state interaction side effects, race conditions between sequential calls, and handlers that silently undo each other.

The Problem This Solves

Traditional debugging checks:

• Does the function exist? (missing wiring)
• Does it crash? (runtime errors)
• Does it return the right type? (data flow)

But it does NOT check:

• Does the final UI state match what the button label promises?
• Does function B silently undo what function A just did?
• Does shared state (Zustand/Redux/context) have side effects that cancel the intended action?

Real example: A "New Email" button called setComposeMode(true) then selectThread(null). Both worked individually. But selectThread had a side effect resetting composeMode: false. The button did nothing. 54 bugs were found by systematic debugging — this one was missed.