A batch service has shared counters, one-time setup and callers that may leave before work starts. Match each request to a small invariant before choosing an operation. An atomic value protects one state transition; a mutex can protect a larger critical section; a context tells work when its caller has canceled. These mechanisms answer different questions. The fresh inputs include zero updates and closed or canceled boundaries. Do not replace completion with a sleep, and do not count a callback that never ran. The checks also revisit the ordinary path, so a cancellation fix must preserve successful work. The browser cannot prove the absence of data races; you are practicing explicit coordination contracts and observable results.