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

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

[github-actions]

Codex AI review

One actionable issue remains in the new conformance case: its forbidden-body canary is not observable during replay. No other issues found.

Reviewed commit 529310cf7ba0d3aa69b81adef13730ebb14ad047. Workflow run