Task · SKT-0067

Make the parallel-isolation test wait for observed dropped ticks

Description

The integrated gate failed TestRunParallelIsolation after its fixed 400 ms window expired with no reported dropped tick. A slow cycle can consume the queued pre-overrun ticker timestamp before the later timestamp exposes coalescing, so the assertion depends on scheduler timing rather than the isolation contract.

Acceptance Criteria

Definition of Done

Implementation Plan

Keep production scheduling unchanged. Replace the fixed observation window with cancellation after all existing evidence predicates hold, backed by a five-second deadline. Retain the integrated failure, exercise repeated focused and race runs, then review and gate the root-owned test change.

Implementation Notes

Test-only correction retains original isolation predicates and waits for observed success within five seconds; production scheduling unchanged. Failure retained in integrated-check.log. Twenty focused repetitions, ten race repetitions, zero CodeRabbit findings and full exact-source gate pass. Evidence in codex/scratch/wave-2026-09-14/: parallel-isolation-repeat.log, parallel-isolation-race.log, coderabbit-runner-test.ndjson, p3-exact-le-sha-check.log. Generation and inventory comparison are not applicable to test-only change.

Final Summary

Test-only correction retains original isolation predicates and waits for observed success within five seconds; production scheduling unchanged. Failure retained in integrated-check.log. Twenty focused repetitions, ten race repetitions, zero CodeRabbit findings and full exact-source gate pass. Evidence in codex/scratch/wave-2026-09-14/: parallel-isolation-repeat.log, parallel-isolation-race.log, coderabbit-runner-test.ndjson, p3-exact-le-sha-check.log. Generation and inventory comparison are not applicable to test-only change.

View the source file on GitHub