Observation
The copied grpc-js files remain green when run in isolated deterministic shards, but the combined range at positions 3979–3989 can leave test-outlier-detection.test.ts pending at Should uneject a server after the ejection period.
Current evidence:
- positions 3979–3984: 43 passed, 1 todo, 0 failed/unsupported
- position 3985 alone: 26 passed, 0 failed/todo/unsupported
- positions 3986–3989: 72 passed, 4 todo, 0 failed/unsupported
- positions 3979–3989 combined: batch-only pending async failure at position 3985
Scope
- identify state/timer leakage across sequential corpus files
- make per-file timer, gRPC server, virtual clock, and async lifecycle teardown deterministic
- retain bounded lifecycle breadcrumbs in any pending failure
- add a permanent multi-file regression for this exact boundary
Tracked from #66 and discovered while validating #253. This is a harness isolation issue, not an assertion failure in position 3985 itself.