Skip to content

chore(acp): trace channel delivery boundaries - #6991

Open
jamesjlopez wants to merge 1 commit into
block:mainfrom
jamesjlopez:fix/acp-channel-delivery-diagnostics
Open

chore(acp): trace channel delivery boundaries#6991
jamesjlopez wants to merge 1 commit into
block:mainfrom
jamesjlopez:fix/acp-channel-delivery-diagnostics

Conversation

@jamesjlopez

Copy link
Copy Markdown

Summary

  • add structured relay traces for the channel subscription, relay receipt, and harness-forwarding boundaries
  • add a websocket-level regression test proving a matching channel-subscription event reaches the harness queue

Why

This diagnostic change supports investigation of #3105 without changing delivery behavior.

Verification

  • cargo fmt --check
  • cargo test -p buzz-acp channel_event_is_forwarded_from_matching_subscription -- --nocapture
  • cargo test -p buzz-acp
  • cargo clippy -p buzz-acp --all-targets --all-features -- -D warnings

Signed-off-by: James Lopez <james.j.lopez@gmail.com>
@jamesjlopez
jamesjlopez requested a review from a team as a code owner August 28, 2026 16:03
@github-actions

Copy link
Copy Markdown

🔐 Codex Security Review

Status: review required for the current range.

The current range is 86b9142a09f2af3ba2fff7effa6a6cd53b40f51c...bf253bcdfefb64e7fa9bcc402268f8675fe0a084.
A new review must complete for this exact range. When manual authorization
is required, a Block organization member must comment exactly
@buzz-security-review bf253bcdfefb64e7fa9bcc402268f8675fe0a084 to authorize a new review.
Any previous review applies only to its recorded range.

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