Click-Path Audit

Curated by Skill Harbor: a behavioral flow audit that finds the bugs static code reading misses. Traditional debugging checks whether the function exists, whether it crashes, whether types line up. It never checks whether the final UI state matches what the button label promised, whether function B silently undoes what function A just did, or whether shared state has side effects that cancel the intended action. The motivating example: a "New Email" button called setComposeMode(true) then selectThread(null); both worked individually, but selectThread had a side effect resetting composeMode to false, so the button did nothing, and 54 other bugs found by systematic debugging had missed it. The method: first map every state store action to what it sets and what it silently resets (the critical reference), then audit each touchpoint handler call by call in order, checking six patterns: sequential undo, async races, stale closures, missing state transitions (button says Save but nothing saves), conditional dead paths, and useEffect interference. Each finding gets a severity, the exact trace with the conflicting call marked, expected versus actual state, and a specific fix. Includes scope control guidance (full app, single page, or store-focused audits, with a recommended parallel agent split) and positions itself after systematic debugging and before verification. Use when systematic debugging found "no bugs" but users report broken buttons, after modifying any shared state store, after refactors touching shared state, or before release on critical flows. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: the audit is expensive, scope it deliberately; examples lean Zustand and React, adapt the mapping step to your state solution; it finds interaction bugs, not API or styling issues. Skill Harbor never reviews the code, review it yourself before use.