feat(flow): persist versioned plans, checkpoints, and recovery decisions - #63
Merged
Merged
Conversation
Record versioned intent, authority, accepted checkpoints, and explicit recovery choices in locked immutable local snapshots. Refuse stale evidence and unsafe reopen; prove interruption boundaries and portable locking in CI. Closes #49 Roadmap-Step: FLO-Q03
Inspect the empty coordination file through metadata instead of reading it through a second handle while Windows holds a byte-range lock. Select stable explicitly for the macOS and Windows portability jobs. Roadmap-Step: FLO-Q03
This was referenced Sep 26, 2026
This was referenced Sep 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Flow previously kept execution history in memory, so a host restart lost the distinction between prepared, interrupted, and accepted work. This adds a durable coordinator for prepared process steps and the state foundation required by #31.
flow.run-*/v1contracts for plans, state, checkpoints, artifacts, authority, validation, recovery, and snapshots; advance the provisional contract set to 0.7.0.Validation (current review head
948eb4dfeb17e701bae61978bd6d593d28ee85e8):--allow-dirtybefore publishing the identical tree).948eb4dfeb17e701bae61978bd6d593d28ee85e8: Rust 1.85.0, Rust stable, repository validators, macOS durable state, and Windows durable state. Both Linux jobs also passed documentation, examples, and clean package verification.Limits: this is a trusted local, single-writer store. Windows guarantees process-crash consistency, not power-loss durability. Digests are correlation evidence, not authentication. V1 never repairs/prunes state or repeats uncertain effects automatically. General scheduling, downstream invalidation, real adapters, and the public CLI remain later checkpoints. ADR-0011 is proposed for maintainer review.
Rollback: revert this implementation while preserving run workspaces and artifacts. Older state or code never authorizes repeated provider effects; resolve uncertain work before restoring a prior workspace.
Closes #49. Parent #3; suite roadmap #11. After merge and green default-branch CI, #31 is next.