test(e2e): agent-loop leg driving comms tools through the real server (RIG-2733) - #627
Open
rigel-mintaka wants to merge 2 commits into
Open
test(e2e): agent-loop leg driving comms tools through the real server (RIG-2733)#627rigel-mintaka wants to merge 2 commits into
rigel-mintaka wants to merge 2 commits into
Conversation
… (RIG-2733) Add `go/e2e/legcomms_test.go` — the comms analog of the legs-3/4 spawn leg. A canned turn issues the native `comms_post_message` tool so the agent's loop runs the real PostMessage against the live Server; the test then asserts the resulting message fans out on the comms bus authored by the agent itself, not the human trigger. Closes the RIG-2733 gap for the comms tool family: before this, only `agents_spawn_peer` had an agent-loop-through-real-server e2e. Forge legs stack behind a fake-GitHub-TLS harness (follow-up). Co-authored-by: Matt Wilkinson <matt@rigel.build>
|
Compass engineering docs preview: https://compass-rig-2733-comms-e2e-l.compass-eng-docs.pages.dev Deployed from |
…(RIG-2733 review) Review-loop follow-up on #627 (both findings low, non-blocking): clarify that settleReply is intentionally not transcript-asserted (the comms fan-out + author assertion is the stronger proof of record), and that the home-channel-default branch has no wire-Message field to assert against (F9 removed the container; GetTopicId is an id, not the scripted name) — so body+author is the ceiling. Co-authored-by: Matt Wilkinson <matt@rigel.build>
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.
Add
go/e2e/legcomms_test.go— the comms analog of the legs-3/4 spawn leg.A canned turn issues the native
comms_post_messagetool so the agent's loopruns the real PostMessage against the live Server; the test then asserts the
resulting message fans out on the comms bus authored by the agent itself, not
the human trigger.
Closes the RIG-2733 gap for the comms tool family: before this, only
agents_spawn_peerhad an agent-loop-through-real-server e2e. Forge legs stackbehind a fake-GitHub-TLS harness (follow-up).
Co-authored-by: Matt Wilkinson matt@rigel.build