fix: enforce cross-file replay conformance vector - #27
Open
rksharma-owg wants to merge 1 commit into
Open
rksharma-owg wants to merge 1 commit into
rksharma-owg wants to merge 1 commit into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The
cross-file-fork-replay-mixed-identityexecution-grain vector uses a file-shaped input (filesplusexpected) to describe fork/replay accounting. The metric runner only handled invocation-shaped vectors, so the conformance job raisedKeyError: 'invocations'and stopped at 21/22 vectors.Root cause
The vector was added with an intentionally different shape, but the runner dispatched every execution-grain vector through the single-file invocation path.
Fix
Dispatch file-shaped replay vectors to a focused fixture-level checker that enforces the published unique-turn, replay-prefix, child-new-work, attempt-retention, and unstable-identity disclosures. Existing invocation-shaped vectors continue through the reference implementation path.
Testing
Fork exact-head validation passed at
19d8ce667c1cb2114a09f67ec189ded43a25c015:spec-conformancereference-implementationhealthcheckPython 3.9 and 3.11lab-suitesdk-gatedocumentation-consistencyWorkflow run: https://github.com/rksharma-owg/AgentMeasure/actions/runs/36085957579
Compatibility
The change only adds dispatch and validation for the existing cross-file vector shape. Existing metric vectors and reference implementation behavior are unchanged.