Problem
context.test.parallel_js: multi-age cooperative nursery retains old-owner graph assumes one fixed 6,000-iteration allocation batch always completes at least the three successful cooperative collections required by the configured tenuring age.
Under a loaded 10-shard run, bounded 100 ms rendezvous attempts can time out often enough that the batch finishes with fewer than three successful collections even though the graph and terminal accounting remain correct:
src/context.zig:41475: collections >= runtime_gc_tenuring_age
full gate: 2,582 passed, 1 skipped, 1 failed, 0 leakedAn immediate isolated rerun passed in 1.423 s. The scheduler change in #1040 is inert in this witness because two workers fit below the automatic runnable-slot limit and no slot waiter exists.
Definition of done
- The witness drives bounded additional allocation batches until it actually observes the configured number of successful cooperative collections.
- Each batch preserves the old-owner child and exact worker result.
- The retry bound fails normally if the collector cannot make progress.
- Collection/timeout terminal accounting and promotion assertions remain exact.
- Repeated focused runs and the full sharded unit suite pass with zero failures and leaks.