feat(proto): BoardCall* agent write family + RelayBoardCall relay (SEA-1830) - #201
Open
seal-agent wants to merge 2 commits into
Open
feat(proto): BoardCall* agent write family + RelayBoardCall relay (SEA-1830)#201seal-agent wants to merge 2 commits into
seal-agent wants to merge 2 commits into
Conversation
…A-1830)
T2 of the frozen `compass-agent-primary-lifecycle` amendment — the agent-facing issue-state-write proto. Adds a new sibling call family on the existing internal `AgentGateway` socket (DL-049/DL-076 shape), relayed Runner→Server, mirroring the `CommsCall*`/`ForgeCall*`/`LifecycleCall*` precedents exactly.
### `agent_gateway.proto`
- `rpc Board(BoardCallRequest) returns (BoardCallResult)` — the agent write, beside `Comms`/`Lifecycle`/`Forge`.
- `BoardCallRequest{ call_id, oneof call { SetIssueStateRequest set_issue_state } }` — the same envelope rides the relay leg verbatim.
- `SetIssueStateRequest{ issue_id, compass.v1.IssueState state }` / `SetIssueStateResponse{ compass.v1.Issue issue }` — carries the frozen `UpdateIssueState` semantics re-homed: any-to-any target, `ISSUE_STATE_UNSPECIFIED` → in-band `invalid_argument`, target == current → idempotent no-op returning current truth, `ISSUE_STATE_ARCHIVED` a legal target (DL-091 survives).
- `BoardCallResult{ call_id, oneof result { SetIssueStateResponse set_issue_state, BoardCallError error } }` — in-band tool error, never a transport teardown.
- `BoardCallError{ code, message }`.
### `runner.proto`
- `rpc RelayBoardCall(RelayBoardCallRequest) returns (RelayBoardCallResponse)` — Runner→Server relay, beside `RelayForgeCall`. Runner is a pure forwarder, asserts no account; the Server resolves `session_id` → account and runs the transition under that caller (single-trust-domain MVP, amendment §Resolved decisions 2), fail-closed `CodeNotFound` for an unknown/stopped session.
- `RelayBoardCallRequest{ session_id, BoardCallRequest call }` / `RelayBoardCallResponse{ BoardCallResult result }`.
### gen-fence
Extends the `proto/moon.yml` SEA-1267 fence with `BoardCall|RelayBoardCall|SetIssueState` (unanchored prefixes) — the new internal envelopes generate only into the internal lanes; the public `compass.v1` `Issue`/`IssueState` the result arms reference are not prefixed and stay in the public trees.
Additive, buf-breaking-safe. Whole-tree 3-lane regen (internal Go + agent TS; public trees unchanged). Explicitly NOT here: no `UpdateIssueState` RPC (dropped by DL-129), no classifier row (`Board`/`RelayBoardCall` are AgentGateway/RunnerService RPCs, not `CompassService`, so `classify_exhaustive_test` is untouched). Gates SEA-1728 Part 5 (T3, compass-server handler stacks on this bookmark).
Stacked on #149 (SEA-1731 forge-carrier): both edit `agent_gateway.proto` + run whole-tree regen, so stacking avoids a guaranteed generated-file conflict at merge.
Spec-impact: none. Refs SEA-1830, SEA-974.
Co-authored-by: Matt Wilkinson <matt@sealedsecurity.com>
…eview) The gen-fence grep is unanchored (substring match), so `BoardCall` already covers `RelayBoardCall*`. Drop the redundant alternation token, matching the ForgeCall/CommsCall precedents (which omit their relay token from the grep and name it in the doc comment only). The `RelayBoardCall*` prose reference in the fence comment is kept for the reader. Fence coverage unchanged — verified `BoardCall` substring-matches every RelayBoardCall* symbol and gen-fence stays green. Refs SEA-1830 Co-authored-by: Matt Wilkinson <matt@sealedsecurity.com>
seal-agent
force-pushed
the
compass-repo-1830-board-call-proto
branch
from
August 7, 2026 03:59
d620a47 to
b92ecab
Compare
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.
This PR is part of a stack containing 3 PRs:
mainT2 of the frozen
compass-agent-primary-lifecycleamendment — the agent-facing issue-state-write proto. Adds a new sibling call family on the existing internalAgentGatewaysocket (DL-049/DL-076 shape), relayed Runner→Server, mirroring theCommsCall*/ForgeCall*/LifecycleCall*precedents exactly.agent_gateway.protorpc Board(BoardCallRequest) returns (BoardCallResult)— the agent write, besideComms/Lifecycle/Forge.BoardCallRequest{ call_id, oneof call { SetIssueStateRequest set_issue_state } }— the same envelope rides the relay leg verbatim.SetIssueStateRequest{ issue_id, compass.v1.IssueState state }/SetIssueStateResponse{ compass.v1.Issue issue }— carries the frozenUpdateIssueStatesemantics re-homed: any-to-any target,ISSUE_STATE_UNSPECIFIED→ in-bandinvalid_argument, target == current → idempotent no-op returning current truth,ISSUE_STATE_ARCHIVEDa legal target (DL-091 survives).BoardCallResult{ call_id, oneof result { SetIssueStateResponse set_issue_state, BoardCallError error } }— in-band tool error, never a transport teardown.BoardCallError{ code, message }.runner.protorpc RelayBoardCall(RelayBoardCallRequest) returns (RelayBoardCallResponse)— Runner→Server relay, besideRelayForgeCall. Runner is a pure forwarder, asserts no account; the Server resolvessession_id→ account and runs the transition under that caller (single-trust-domain MVP, amendment §Resolved decisions 2), fail-closedCodeNotFoundfor an unknown/stopped session.RelayBoardCallRequest{ session_id, BoardCallRequest call }/RelayBoardCallResponse{ BoardCallResult result }.gen-fence
Extends the
proto/moon.ymlSEA-1267 fence withBoardCall|RelayBoardCall|SetIssueState(unanchored prefixes) — the new internal envelopes generate only into the internal lanes; the publiccompass.v1Issue/IssueStatethe result arms reference are not prefixed and stay in the public trees.Additive, buf-breaking-safe. Whole-tree 3-lane regen (internal Go + agent TS; public trees unchanged). Explicitly NOT here: no
UpdateIssueStateRPC (dropped by DL-129), no classifier row (Board/RelayBoardCallare AgentGateway/RunnerService RPCs, notCompassService, soclassify_exhaustive_testis untouched). Gates SEA-1728 Part 5 (T3, compass-server handler stacks on this bookmark).Stacked on #149 (SEA-1731 forge-carrier): both edit
agent_gateway.proto+ run whole-tree regen, so stacking avoids a guaranteed generated-file conflict at merge.Spec-impact: none. Refs SEA-1830, SEA-974.
Co-authored-by: Matt Wilkinson matt@sealedsecurity.com