test: add replay identity conformance case

[zhongkechen]

Summary

• add the general conformance suite and handler for requirement 11-1
• emit a named WAIT on the first invocation and a named STEP at the same replay position
• enable replay-visible canary logging and prove the mismatched step body never executes
• make replay-identity diagnostics identify checkpointed values as expected and emitted values as current

Dependencies

• stacked on fix(core): validate replay operation identity #698, which adds replay operation-identity validation
• implements feat: require replay operation identity validation aws-durable-execution-conformance-tests#111

Testing

• python3 packages/aws-durable-execution-sdk-python-conformance-tests/scripts/discover_suites.py
• python3 packages/aws-durable-execution-sdk-python-conformance-tests/scripts/build_examples.py
• focused state tests: 4 passed
• focused execution tests: 3 passed
• hatch run dev-core:typecheck
• Ruff check and format verification for changed Python files
• git diff --check

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[github-actions]

Codex AI review · Finding arf_v1_qk6nurjxyn6fmk3nrrncxxiaaq

[P2] Make the step-body canary replay-visible

This step inherits the durable context's replay-aware logger, so this INFO record is suppressed while replaying. If a regression executes unexpected_step before rejecting the identity mismatch, the canary remains absent and requirement 11-1 cannot detect the forbidden execution. Cast step_context.logger to the concrete Logger and emit through with_is_replaying(lambda: False) so the execution metadata is preserved while the canary remains visible.

[github-actions]

Codex AI review

One conformance-test reliability issue remains: the forbidden step-body canary can be suppressed during replay, weakening requirement 11-1.

Reviewed commit cd186ca793a12ec9d5fe7f95c1aae1d321b31691. Workflow run