What problem does it solve? Static code review and systematic debugging often miss bugs where every function works individually but they cancel each other out at runtime. A button can have a wired handler, no crashes, and correct types, yet still do nothing because a later call silently resets the state an earlier call just set. ## Core Features & Use Cases - State Store Side-Effect Mapping: Builds a reference map of every Zustand/Redux/context action, documenting what each action sets and what it silently resets. - Touchpoint Handler Tracing: Walks every onClick/onSubmit/onChange handler call-by-call to detect sequential undo, async races, stale closures, dead paths, and useEffect interference. - Structured Bug Reports: Produces severity-rated findings with full state-change traces, expected vs actual behavior, and specific fixes. - Use Case: After a refactor of a shared Zustand store, audit all consumers to catch cases like a "New Email" button whose second call resets the composeMode flag its first call just enabled. ## Quick Start Audit the email page for click-path bugs by mapping the email store's side effects and tracing every button handler to its final state.
