feat(simulate): add what-if engine for state diff and effect sequence - #353
Merged
Merged
Conversation
Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
joshua-temple
enabled auto-merge (squash)
June 25, 2026 15:09
Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
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
2 participants
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.
Adds cascade simulate, a what-if engine that needs no Docker and no GitHub access. Given a manifest and current ci.state plus a hypothetical action, it replays the real orchestration logic (internal/promote) in record-only mode against a temp clone of the manifest, then prints a before and after state diff plus an ordered effect sequence (run, skip, gate).
The engine is action-agnostic via an Action interface; this lands the command, the state-clone, the diff and effect renderers, and one wired action (promote) end to end. The remaining actions follow in #312.
No on-disk state is mutated and no git or network call is made: the manifest is copied to a temp file, the transition is computed against the copy, and the copy is discarded. Additive only; schema_version, generator output, and cascade verify are unaffected.
Verification: go build ./... and go test ./... and golangci-lint run ./... all green; unit, golden-file, and end-to-end engine tests included.
Closes #311.