feat(headless): preserve governed tool execution ids - #884
Draft
haasonsaas wants to merge 1 commit into
Draft
Conversation
Contributor
|
This PR changes mirrored Maestro source files in the public repo, but it does not link the matching private source-of-truth PR. Add one of these to the PR body, then re-run the check:
Mirrored files touched:
|
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.
What changed
tool_execution_idto headlesstool_responsemessagestool_endWhy
A platform control plane can allocate a durable ToolExecution record only after Maestro emits a tool intent. Before this change, the controller could approve or complete the tool, but Maestro's terminal event still emitted
tool_execution_id: null, breaking durable correlation between runtime events, policy decisions, evidence, and receipts.This is the first protocol seam for evalops/platform#5204. It intentionally does not add Dex- or channel-specific behavior to Maestro.
Private source-of-truth PR: https://github.com/evalops/maestro-internal/pull/3172
Developer impact
Governed hosted-runner clients may return
tool_execution_idwith atool_response. Maestro echoes it on the terminaltool_end. Existing clients require no changes.Checks
cargo fmt --all --checkcargo test -p maestro-tui headless --locked(175 passed)cargo clippy -p maestro-tui --all-targets --locked -- -D warningsFollow-up boundary
Platform will consume this contract from a channel-neutral turn coordinator. Slack, Console Chat, scheduled work, and future channels remain separate projections over the same governed runtime; this PR does not implement that Platform coordinator.