A single visitor clicking merge and then adding one more file before it finished was enough to strand NearPDF's UI forever. Here's how two independent races — a worker response bridge with no per-call identity, and an await that let a screen check act on stale state — combined to cause it, and the regression test that proves both are actually fixed.