Add Buzz transport stack (member release, ships relay-unconfigured) - #67
Merged
Merged
Conversation
Ports the deferred Buzz transport (NIP-29 group chat over Nostr): the relay client, dispatcher, durable per-(event,agent) inbox delivery, org-scoped authentication identity, the buzz CLI (send / test-send / discover-channels), send-buzz.sh, and the agent-manager integration (shared per-org WebSocket, eviction/teardown). Adds @noble/hashes + @noble/secp256k1. Ships RELAY-UNCONFIGURED as its finished state: the framework consumes a relay URL, keys, and channel/sender config that the operator provides (BUZZ_RELAY_URL / BUZZ_PRIVATE_KEY / buzz.json) and never deploys a relay, mints keys, or changes membership — with those absent the adapter stays inactive. No default relay exists. The setup runbook says plainly: choosing Buzz means picking and configuring your own relay and keys. Additive over member main; the merged Slack transport and side-run fallback are untouched (the buzz-only carrier hunks were applied; the org-path, channels-prose and side-run-revert hunks were not). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WHgtUKEyT27odfUsRhjgoT
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 387d4a3112
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
…t runtime gate, runbook scaffold) - relay-client: on a socket close BEFORE the AUTH challenge, rejectAllPending() cleared the auth-wait timer without settling waitForAuthChallenge()'s promise, so connectAndRun() hung forever and the reconnect loop died. Give the pending auth-wait a reject callback and invoke it on closure. Casualty test proves a close-before-challenge reconnects instead of suspending. - relay-client + cli/buzz: native WebSocket is unavailable on older Node (engines allows >=20). Gate loudly with a clear 'requires Node 20.10+' message before the reconnect loop and at the CLI connect point, matching the Slack transport's convention — fail-loud, never retry-forever-silent. Test covers the gated path. - runbook: step 4 documented a 'cortextos add-agent --buzz-channel' flag that does not exist; rewrite to the real create-agent + author-buzz.json steps. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WHgtUKEyT27odfUsRhjgoT
…ode 22+ The gate messages said 'Node 20.10+', but native WebSocket is only default-on from Node 22 — a member on Node 21 would read the requirement, believe they satisfy it, and still hit the gate. Fix both the relay-client warning and the cli/buzz error to Node 22+. Feature-detect logic (typeof WebSocket) unchanged; prose only. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WHgtUKEyT27odfUsRhjgoT
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.
Summary
Adds the Buzz transport (NIP-29 group chat over Nostr) to the member framework — the transport deferred from earlier releases. Additive over the current base; the Slack transport and all prior behavior are unchanged.
Census: 22 files, +2,743 / −1.
Choosing Buzz means picking and configuring your own relay and keys. The framework consumes a relay URL, an authentication identity, and channel/sender configuration that you provide (
BUZZ_RELAY_URL/BUZZ_PRIVATE_KEY/buzz.json); it never deploys a relay, mints keys, or changes membership. With those values absent the adapter simply stays inactive — no default relay exists, and you should not invent one. Seedocs/runbook/buzz-adapter-setup.md.Included
wss://-only), dispatcher, and durable per-(event, agent)inbox delivery (dedup + independent acks; a failed target never rolls back siblings).cortextos buzz send | test-send | discover-channels, andbus/send-buzz.sh.@noble/hashes,@noble/secp256k1(pure JS; no build hooks).Discipline
.github/scripts/leak-guard.sh), so a real key elsewhere is still caught.Local gates
tsc --noEmit: 0 errors🤖 Generated with Claude Code