Bradley Axen d23795b05f feat(relay): add channel metadata to operator-listener notifications ...

Operator listeners (kgoose) read the mention's kind:39000 channel metadata
before they can start a run, to tell a DM from a channel and, for Buzz
sessions, to read the session markers in `about`. The delivery access check
already reads the channel row, so return it and send it with the
notification instead of making the listener ask for it.

v2 notifications gain an optional `channel` object: `id`, `name`,
`channel_type`, `visibility` and `about` (omitted when empty, like the
39000 tag). The whole object is omitted for a channel-less event, or when
`about` exceeds 16 KiB so the body stays within the listener's size cap;
the listener then falls back to reading the channel. The access predicate
is unchanged, moved from an EXISTS subquery to a LEFT JOIN so its columns
can be selected.

Co-authored-by: claude00 <fb8b76a01257932b8ca35060862c29bd09b2137638573731c2d5074fc02c5385@buzz.block.builderlab.xyz>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Bradley Axen <baxen@squareup.com>

2026-10-14 20:27:50 -07:00

..

src

feat(relay): add channel metadata to operator-listener notifications

2026-10-14 20:27:50 -07:00

tests

buzz-db: admit every fenced-table writer in app code (#8219)

2026-10-14 10:58:12 -04:00

Cargo.toml

fix(push): isolate push enqueue and stop workers on rollback (#8216)

2026-10-09 13:48:06 -07:00

TESTING.md

refactor(schema): fan desired-state schema out to one file per table (#8131)

2026-10-08 08:47:44 -04:00