[Bug]: Wait for callback create_wait_strategy failed at runtime

[wangyb-A]

Expected Behavior

create_wait_strategy currently fails at runtime with

AttributeError: 'WaitDecision' object has no attribute 'should_continue'

Python: https://github.com/aws/aws-durable-execution-sdk-python/blob/main/packages/aws-durable-execution-sdk-python/src/aws_durable_execution_sdk_python/waits.py#L81

WaitDecision WaitStrategyConfig are dead code should be removed

WaitForConditionConfig= parameters for theoperation(wait_strategy,initial_state,serdes).
WaitStrategyConfig= parameters for the exponential-backoff strategy

Actual Behavior

See above

Steps to Reproduce

SDK Version

1

Python Version

3.14

Is this a regression?

No

Last Working Version

No response

Additional Context

No response

[yaythomas]

Defect 1: type mismatch makes the built-in wait strategy unusable

create_wait_strategy returns a function producing WaitDecision (attribute should_wait). wait_for_condition consumes WaitForConditionDecision (attribute should_continue). Wiring the built-in strategy into WaitForConditionConfig fails on the first poll attempt:

AttributeError: 'WaitDecision' object has no attribute 'should_continue'

Confirmed against the released SDK (1.7.0). JS and Java return the correct decision type.

Python has no working built-in wait strategy for wait_for_condition today.

Defect 2: exhaustion semantics diverge from JS and Java

The max-attempts branch in create_wait_strategy (waits.py L81) returns no_wait(), which wait_for_condition treats as success. JS throws Error and Java throws WaitForConditionFailedException at the same point. Once Defect 1 is fixed, this branch becomes reachable and executions that exhaust polling attempts would complete successfully with partial state. Both defects must be fixed together. Fixing only the type mismatch converts today's loud failure into a silent wrong result.