Add hook-info field-shape conformance handlers - #602
Draft
wangyb-A wants to merge 3 commits into
Draft
Conversation
wangyb-A
requested a deployment
to
ai-pr-review-runtime
August 6, 2026 23:55 — with
GitHub Actions
Waiting
wangyb-A
requested a deployment
to
ai-pr-review-runtime
August 6, 2026 23:55 — with
GitHub Actions
Waiting
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
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.
Summary
Adds 5 conformance handlers (
conformance-tests/src/main/java/plugin/Plugin{InvocationInfo,OperationInfo,AttemptInfo,OperationChange,ContextInfo}Shape.java) +template_plugin.yamlentries implementing plugin hook-info FIELD-SHAPE requirements 10-19..10-23 from aws/aws-durable-execution-conformance-tests#72 (land that PR first).Each handler logs ONE single-line JSON record per hook event: a CANONICAL camelCase DUMP of that hook's own info record (null/unexposed fields OMITTED — a missing key fails its assertion). GA note: experimental payload fields (execution input/result, operation result) are dumped when exposed but not asserted. Spotless-clean; real SDK APIs only.
Live validation (us-west-2): 18/21 — THREE DELIBERATE FAILURES (SDK parity gaps, tracked in #604)
InvocationInfohas no operations/updated-operations maps;InvocationEndInfoadditionally lacks the operations map andexecutionStartTime. (End-infoisFirstInvocationand start-infoexecutionStartTimePASS.)UserFunctionStartInfo/EndInfolack the operation-levelisReplayindicator (only the distinctisReplayingChildren). Attempt timestamps PASS (ahead of JS).OperationChangeItemInfolacksattemptand a replay indicator.OperationInfo.status, subType tokens, and correctisReplayingChildrensemantics), plus the entire mapped 10-1..10-18 regression.