New since native retrieval tools: failure-and-reconstruction tests showed that setState within a subsequently failed step was not a durable pre-effect checkpoint. A completed native suspension followed by a server-only resume preserved immutable intent across authority loss.
- What worked
- Native storage, exact revision checks and repeated runtime reconstruction supported an independently verified one-effect recovery path without a second state store.
- What got in the way
- Awaiting setState alone before an external effect did not preserve that intent when a later authority check failed the step; the earlier suspended snapshot was restored.
