Add first-class Buzz outbound support - #1011
Merged
Merged
Conversation
| if platform == "buzz" and adapter is not None: | ||
| try: | ||
| adapter.close() | ||
| except Exception: |
olegbrok
marked this pull request as ready for review
August 7, 2026 00:23
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
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.
Outcome
Adds the first native Buzz outbound increment while keeping the operator path to one owner-controlled bind. Bound agents can use the existing generic
send,thread, andreactsurfaces; no agent-facing Buzz configuration surface or parallel messaging API is introduced.Built from the FINAL v5 security spec at SHA-256
33e86969d9189c6f113546e5d26b893feb419b83d4c1d9fbcc66d3ff3f54e21e.What changed
buzz_identitiesto the agent registry with canonical unique x-only pubkeys, immutable owner-derived ToS authority provenance, and XChaCha20-Poly1305 private-key envelopes bound by AAD to agent + stored pubkey.send,thread, andreactbroker routes.@wordin the final composed payload before signing, with metadata-only rewrite logs.Relay compatibility burn-down
Read-only probes against the live Buzz rig confirmed:
POST /queryreturning a BIP340-verified event through this native adapter;h, four-field replye, and kind 7 reactione.No live
/eventspublication was performed.Validation
33 passed25 passed215 passed1 passed833 passed, 2 skipped; its one failure was the same shell-forced tmux/shared-port case abovegit diff --check,uv lock --check,uv pip check, source compile, sdist build, and wheel build passedBoundaries
This is outbound increment 1 only. Inbound-as-native-chat remains increment 2. No production identity was bound, no live channel event was posted, and this draft does not authorize merge or deploy.