Task · GCI-0128

Preserve freshness-first rejection for malformed legacy carry records

Description

loop17 independent review found a minor robustness regression outside the supported-state bounded-label proof: T1 projects legacy metric payloads before carry freshness validation. An expired Assistant metric missing category raises KeyError instead of being discarded. Supported stale/future/invalid-timestamp records and all current schema records still behave correctly. No live occurrence observed. Root deliberately retained this minor residual in the reviewed bounded-projection candidate instead of widening its accepted scope.

Acceptance Criteria

Definition of Done

Implementation Plan

loop18: fail-first real T1 malformed expired-state reproduction, freshness-first fix, supported dedup and immutability checks, independent review and exact-SHA gate.

Implementation Notes

loop18: implementation attempts1, review-repair rounds0. Real T1/publication fail-first12 malformed rejected-state cases; repaired6test classpasses; supported projected carry remains7not14 and loadedstateimmutable. Independent exactpatch reviewPASS and CodeRabbitcomplete0findings. Landed d60ed418144d47ba5b965724e563f79120c187cf (only2ownedfiles), gate0 and CI37765227990 requiredleaves success. Root integrated13a884e741703c7b0968f2353174876845a0fbf2 composed justcheck0 (2428passed,2skipped,23189subtests) and CI37765790586 success. Freshcorruptpayload outside supportedcontract remains intentionally unnormalized.

Final Summary

Freshness rejection now precedes legacy payload projection. Real T1/native remote_write reproduction distinguishes rejected malformed state from fresh supported carry; independently reviewed exact patch landed, exact CI and composed gate green.

References

View the source file on GitHub