[lilydoar]

What changed

Add one default-off recover-schedule-operations option for Create, Describe, Update and Delete. Recovery retains the schedule's identity and original window, observes uncertain effects, and fails when the outcome cannot be established.

Review: As a single unit in stack order.

Why

Retrying a whole iteration creates new schedule IDs and repeats unrelated work. A read-only retry cannot recover SDK Update's internal Describe or distinguish a committed write with a lost response from a write that never took effect.

Details worth reviewing

Merge after #527, including #518's SDK prerequisite. Each operation has a shared four-logical-call/five-second budget, including its initial call and probes; SDK retries are additional physical calls within that same context. Create/read/update also retain the original EndAt. These opt-in limits are candidate policy, not measured FI qualification thresholds.

A fresh State.Note witness establishes an uncertain update's effect; ambiguous updates are never replayed. Ownership assumes Omes' unique IDs are not reused by another writer; Delete has no atomic replacement fence. Existing NotFound compatibility is preserved without claiming an acknowledged mutation. This replaces the unpublished read-only retry experiment.