Joseph Doherty
bf73985481
The Server-032 change made event-channel overflow wait EventChannelFullModeTimeout before faulting, instead of faulting instantly. Two pre-existing overflow tests were not updated and left EventChannelFullModeTimeout at its 5s default, which races the 5s TestTimeout: ReadLoop_WhenEventQueueOverflows_FaultsClient and ReadLoop_WhenClientFaults_KillsOwnedWorkerProcess. Pin it to 50ms in both so overflow faults promptly. EnqueueWorkerEvent_WhenChannelFullPastTimeout_FaultsWithRichDiagnostic wrote 6 events into a 4-slot channel, but the worker client faults while reading the 5th and its read loop then stops — the 6th event is never drained and the test's pipe write for it blocks forever on a full OS pipe buffer, hanging the test host. Write exactly 5 (4 to fill plus 1 to overflow) as the test comment already intends, and bound the post-fault event drain with TestTimeout so a future regression fails instead of hanging. No production change: the Server-031/032 WorkerClient logic is correct — these were test-only defects. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>