Skip to content

test(e2e): prove the owner peering lifecycle over the real transport (RIG-4365) - #1776

Draft
rigel-mintaka wants to merge 1 commit into
compass-forge/rig-4363-owner-peering-addressingfrom
compass-server/rig-4365-peering-e2e
Draft

rigel-mintaka wants to merge 1 commit into
compass-forge/rig-4363-owner-peering-addressingfrom
compass-server/rig-4365-peering-e2e

Conversation

@rigel-mintaka

@rigel-mintaka rigel-mintaka commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Owner peering T5: TestCommsPeerLifecycleTransport drives the peering lifecycle over the real TLS door and live agent sessions:

  • Unpeered co-member: OpenDM returns NOT_FOUND, identical to an unknown handle once the handle is redacted, and posts do not reach the peer agent.
  • One-sided approval: still NOT_FOUND.
  • Mutual approval: DM opens, posts reach both ways, and the peer can read DM history.
  • Qualified mentions: @owner/agent steers the peer, in both directions.
  • Revoke: NOT_FOUND on the co-member and on a third agent; nothing reaches either way, including into the existing DM.
  • Re-approve: delivery is restored.

Negative legs are proven by a canary that does arrive, never by a timeout. OpenSessionTailAs opens a tail as the agent owner, because another owner's agent session is invisible to admin.

Depends on

Testing

  • Local podman e2e: every leg passes except the two mention legs (DELIVER, want STEER).
  • go vet -tags podman ./e2e is clean, and golangci-lint is clean untagged.

@trunk-io

trunk-io Bot commented Oct 6, 2026

Copy link
Copy Markdown

Merging to main in this repository is managed by Trunk.

  • To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

@linear-code

linear-code Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

RIG-4365

RIG-4361

@rigel-mintaka
rigel-mintaka changed the base branch from main to compass-forge/rig-4363-owner-peering-addressing October 6, 2026 08:08
@rigel-mintaka rigel-mintaka changed the title feat(server): add owner peering approvals, RPCs and CLI (RIG-4361) test(e2e): prove the owner peering lifecycle over the real transport (RIG-4365) Oct 6, 2026
…(RIG-4365)

Unpeered, one-sided, mutual, revoked and restored peering, each checked on
OpenDM and on live delivery to the peer agent session.

Co-authored-by: Matt Wilkinson <matt@rigel.build>
@rigel-mintaka
rigel-mintaka force-pushed the compass-server/rig-4365-peering-e2e branch from 253e159 to 992e9e7 Compare October 6, 2026 08:11
@rigel-mintaka
rigel-mintaka changed the base branch from compass-forge/rig-4363-owner-peering-addressing to main October 6, 2026 08:11
@rigel-mintaka
rigel-mintaka changed the base branch from main to compass-forge/rig-4363-owner-peering-addressing October 6, 2026 08:11
@github-actions

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown

Compass engineering docs preview: https://compass-server-rig-4365-peer.compass-eng-docs.pages.dev

Deployed from compass-server/rig-4365-peering-e2e at 992e9e7.

@mattwilkinsonn
mattwilkinsonn added this pull request to stack #1826 October 7, 2026 00:28

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant