React batched state log

A production symptom appears first: flaky tests, stale state, slow UI, late cleanup, or growing memory. This shows up in React forms, counters, analytics events, and logic that reads state immediately after updating it.

Expecting state variables to mutate immediately like plain objects.

Fix the root scheduling, cleanup, or concurrency pattern instead of adding arbitrary waits.

try {
  await operation();
} finally {
  cleanup();
}

The console lane proves the visible order: 0 -> render count: 1. The active line and queues show why source order changed.

Reproduce the symptom with a small test, apply the safer pattern, then verify the flaky, slow, or leaking behavior disappears.