Both tests take the global single-flight UPDATE_OP_LOCK; run concurrently by the test harness, one saw the other's lock and failed with 'another update operation is already running' instead of its expected refusal. A shared test mutex makes them mutually exclusive deterministically. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>