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 if functions exist, crash, or return the right type. 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 have side effects that cancel the intended action?

How It Works

For EVERY interactive touchpoint in the target area: