Uh oh!
There was an error while loading. Please reload this page.
Run CLI workflows on Yieldstar - #38
Closed
djgrant wants to merge 2 commits into
Closed
Conversation
- Emit reconciler.drift.detected as a durable step before a drift-update decision, restoring event parity with the synchronous reconciler. - Emit a durable update skip lifecycle event when a resource has no update operation instead of returning silently. - Remove an unreachable dryRun check after the provider mutation. - Read store snapshots in one round trip in YieldStarStateBackend and treat a store deleted mid-read as resource absence, instead of listing every store before each get, update, and delete. - Return the committed store version from YieldStarStateBackend.update rather than a locally computed revision. - Test orphan deletion through the registry and drift repair with events on the durable path. - Document resuming a crashed deployment with the same execution ID to release deployment coordination through replay.
djgrant
changed the base branch from
yieldstar-integration-review-1
to
yieldstar-integration-build-1July 22, 2026 07:58
This was referenced Jul 22, 2026
djgrant
commented
Jul 22, 2026
CollaboratorAuthor
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 freeto 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.
Stacked on #37.
Problem
PR 37 left CLI deploy and destroy on the synchronous reconciler, while durable Yieldstar execution existed only as an embedded deploy generator. Destroy had no first-class durable workflow, and the old mutation path still carried its own step runner, renewable leases, refresh fallback, and separate state documentation.
Approach
NodeYieldstarRuntimein@notation/coreto wire Yieldstar 0.5.0'sWorkflowRunner, SQLite heap, stores, scheduler, timers, and resident event loop.deployAppanddestroyAppontodeployWithYieldstaranddestroyWithYieldstar, with the CLI printing resumable execution IDs and using one.notation/workflows.dbstate path.Result
CLI deploy and destroy now remain resident across Yieldstar timer wake-ups. Reusing an execution ID after a crash replays completed provider calls from the durable heap, including delete calls completed before state removal. Embedded callers retain the generator boundary and can supply their own Yieldstar runtime.
Checks
CI=true pnpm build— 13/13 tasks passed.CI=true pnpm typecheck— 11/11 tasks passed.CI=true pnpm test:once— 75 passed, 4 skipped.