Repository navigation
Preflight prepared local retry reports without payload effects - #1050
Conversation
|
|
Exact This remains a pure helper. The resulting main run will supply full Quality Cycle attribution, separately from #1049's still-running original |
|
Resulting-main qualification is complete on original 42128433218, attempt 1, exact
The incorporated remote author branch was deleted after exact-head/ancestry, dependent-PR and active-run checks; API absence is verified, with local source history retained. This completes the pure report validator's Quality Cycle. Workflow continues the guarded writer in draft #1051; the bound bridge, SDK/native/installed adoption and release remain unchanged. The failed writer preflight remains attributed to its original head and will receive an actual append-only legacy-retry corpus control rather than a policy exception. |



Prepared local retry contract 2 must distinguish malformed supplied overrides before authority lookup and validate completed result structure without fetching its external payload. The existing outcome normalizer resolves completed envelopes, so it cannot serve as that pure preflight.
This adds an internal shape validator with the accepted error precedence: invalid or misplaced override first, then closed outcome fields/types. It validates existing inline/reference metadata without storage access, decoding, a callback or clock sampling. Callers still own the two-phase dispatch and original role/claim/contract/snapshot authority; the helper is not wired into legacy routes or capability advertisement.
Validation: ECS and configured PHPStan pass. Focused PHP 8.4.27 / PCOV 1.0.12 checks pass 18 tests / 305 assertions across the report helper, policy primitive and unchanged v1 policy tests. The two new production helpers have 118/118 executable lines covered; exact container/name and stopper cleanup was independently verified. The normal PR pipeline adds current-head source attribution. #1049's original resulting-main Quality Cycle remains separately tracked.
Workflow owns the next guarded preparation/outcome transaction slice. Server retains its matching original-claim and distinct receipt boundary on Server #1034. A future preparation writer must atomically store explicit local contract 2 from actual installed-role admission, and outcome handling must read that original authority plus snapshot 2. No writer, new capability, protocol bump, SDK/native adoption, installed experiment or release is enabled by this PR.
Continues central #219.