fix(dag): enforce workflow tool ownership - #211
Merged
Conversation
This was referenced Aug 9, 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
1 participant
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.
Closes #210.
Establishes the parent-Session ownership boundary at the public
workflowtool seam:status,extend, and everycontroloperation require the durable workflow to belong toctx.sessionID.start.session_idis rejected when it differs from the calling Session.Dag.Servicerecovery calls and project-scoped HTTP API behavior remain unchanged.Regression coverage proves a foreign Session cannot read child Session IDs, attach a new workflow, extend a graph, publish control events, or mutate an existing workflow.
Validation: Core 90 + OpenCode DAG 401 + Schema 3 + TUI 50;
workflow-tool.test.ts34/34; SDK generated output unchanged; package and repository typecheck passed; lint 4850 warnings/0 errors.