Task · CFO-0078

Diagnose intermittent DNS lifetime-cardinality integration assertion

Description

Loop17 P67 local gate at cf7b7f56b0790f0a85147ecf0b42202d55d1997d failed TestRegisteredDNSLifetimeCardinalityBudget/default_many_zones after10.04s: total19642 want20904 points9821 max9999 folded0. Fresh independent exact-SHA gate passed DNS in8.154s and sibling exact-SHA gates also passed. The first result is a genuine assertion failure, not classified infrastructure; no DNS source or assertion was changed. Determine why expected complete counts are intermittently missing without masking a real scheduler/cardinality defect. Outside loop17 admission envelope.

Acceptance Criteria

Definition of Done

Implementation Plan

Loop18 bounded race/count mismatch attribution in isolated worktree, test-only correction if supported with full assertions preserved; red/green and count30 race, security review before landing, composed gate.

Implementation Notes

Loop18: implementation attempts1; authentic diagnostic red incomplete periodic snapshot14668/20904, exact synchronous final20904. Correction preserves complete-delivery/cardinality/sticky/window/warning assertions. Race count30 passed; guarded security and CodeRabbit clean. Landed594ce5c, exact CI37203796221 ci-success green; composed78f4d46 just check and integrated review green. No image/package changes or new signals, packaging gate not applicable.

Final Summary

Fixed test synchronization by final synchronous OTLP export and independent churn-prefix witnesses, not count relaxation. Verified authentic red/green, race count30, just check, guarded review, exact CI and composed gate.

View the source file on GitHub