refactor: type broker request payloads - #247
Merged
Merged
Conversation
ejgallego
force-pushed
the
codex/broker-request-types
branch
5 times, most recently
from
September 2, 2026 15:02
7577d93 to
7154d1b
Compare
ejgallego
force-pushed
the
codex/broker-request-types
branch
3 times, most recently
from
September 2, 2026 20:02
52440c9 to
4e649ea
Compare
ejgallego
force-pushed
the
codex/broker-request-types
branch
from
September 2, 2026 20:32
4e649ea to
e6c1c94
Compare
ejgallego
marked this pull request as ready for review
September 2, 2026 21:19
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.
This PR replaces the broker-wide optional-field request record with a small routing envelope around a tagged operation payload, making invalid operation shapes unrepresentable after decoding while keeping the daemon wire format flat and rejecting unrelated fields.
Broker failures, cancellation acknowledgements, and target Lake helper exchanges remain typed across internal boundaries. Handle operations take workspace and backend routing from the handle itself, while the public CLI and MCP operation surface remains unchanged.