docs(power): "When to use each" table has AtMostOncePerRetry and AtLeastOncePerRetry use cases swapped

[TrickSumo]

Problem

The "When to use each" table in advanced-patterns.md has the use cases completely reversed:

Current (wrong):

Semantic	Use When	Example Operations
AtMostOncePerRetry	Operation is idempotent	Database updates, API calls with idempotency keys
AtLeastOncePerRetry	External deduplication exists	Queuing systems, event streams

Why This Is Wrong

AtMostOncePerRetry is designed for non-idempotent operations. The SDK waits for the START checkpoint before executing, so if Lambda crashes mid-step, the step is skipped on replay rather than re-executed.

AtLeastOncePerRetry is designed for idempotent operations.

Source

The SDK's own JSDoc in src/types/step.ts confirms:

// At-least-once per retry (default) - safe for idempotent operations
{ semantics: StepSemantics.AtLeastOncePerRetry }

// At-most-once per retry - for non-idempotent operations
{ semantics: StepSemantics.AtMostOncePerRetry }