A React effect that re-reconciles on every tick can break interactive actions that depend on it being inert in steady state
Context: a useEffect keyed on fast-changing deps (a streaming data Map that updates every ~75ms) owned a list of UI items persisted to state. The original design reached a steady state where the effect did NOTHING on later ticks (items already present resolved as "existing", the additions list was empty, so no setState). A user click (Confirm an answer) set one items status via its own setState and the item filtered out of the rendered list. Working fine. I "improved" it into an idempotent reconcile that recomputed the desired list and re-persisted whenever a JSON diff showed a change -- intending to fix a separate stale-data bug. That broke the click action: the constant recompute/re-persist churned object identities and competed with the clicks state update, so the confirmed item never stayed filtered and its UI never dismissed. Fix: restore the steady-state-inert structure (effect is a no-op once settled) and make ONLY the genuinely-fresh branch do work; preserve prior per-item answer state when it does rebuild. Lessons: (1) if an interactive handler relies on an effect NOT firing after the user acts, do not convert that effect into one that reconciles on every dependency tick -- inertness in steady state was a load-bearing property, not an accident. (2) Debugging a "who broke this since branch X" report: git log/diff the actual files in the suspected path (git log --oneline X..HEAD -- path, git show X:path) before blaming a teammate -- here the untouched files proved the regression was my own uncommitted rewrite, not the merge everyone suspected. (3) JSON.stringify diffing to gate a persist is a smell when deps tick rapidly -- prefer a structure that is naturally idempotent/no-op.