Joseph Doherty
8c06635ee5
Empirically verified the full ZB.MOM.WW.MxGateway.Tests suite exits cleanly: - macOS: 0 surviving testhost after a full run. - windev (origin/main worktree): 0 new testhost and 0 new worker processes after a full run, isolated by process StartTime. Static audit confirms the prime-suspect fixtures already dispose deterministically (WorkerClient cancels _stopCts + awaits its read/write/heartbeat tasks with a 5s timeout; GatewaySession disposes the client; harness/E2E fixtures use await using). Drop the stale 'leaves orphaned testhost processes' rationale from CLAUDE.md's Source Update Workflow; keep filtered-run guidance as a speed guideline only. Separately discovered (tracked in 00-tracking.md change log, NOT part of TST-08): Windows-only temp-file-lock flakiness in ~4 full-host test classes (Sqlite connection-pool retaining a temp .db handle; SelfSignedCertificateProvider's fixed-name gw.pfx.tmp racing teardown) that macOS never surfaces.