upstream-watch: track W8 (mention gate regression) and W9 (key in agent shell) - #5
Merged
Conversation
…in agent shell) W8: since desktop v0.5.12 (#5681), the mention gate requires kind:10100 fields nothing publishes, making relay-hosted agents un-mentionable regardless of the W1 badge tradeoff. Fix in progress: #5878. W9: buzz-acp puts BUZZ_PRIVATE_KEY/BUZZ_AUTH_TAG in reach of the agent's shell, which this deployment relies on to reply. #2883 has a live repro of the key leaking into a channel transcript. Fix in progress: #5288. Also notes #4223 as a second blocker on W1's owner-only clear-when, specific to closed relays with direct-member agents (our shape).
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.
Registry upkeep only - no config/behavior change, docs/upstream-watch.md only.
W8 - mention gate regression, no publisher exists
block/buzz#5681 (merged, shipped desktop v0.5.12+) tightened the @-mention
send-boundary gate to require kind:10100
channel_ids/respond_tofields.Nothing in the upstream repo publishes those fields - block/buzz#5869 confirms
this makes any relay-hosted/headless agent (ours included) structurally
un-mentionable, independent of the W1 badge tradeoff. Fix in progress:
block/buzz#5878 (
buzz agents set-directory), open, not merged.W9 - BUZZ_PRIVATE_KEY reachable from the agent's own shell
block/buzz#2883 (open):
buzz-acpputsBUZZ_PRIVATE_KEY/BUZZ_AUTH_TAGinthe MCP shell tool's environment. This deployment gives the agent unit a
shell specifically so it can reply (see README). A comment on that issue has
a live repro: an agent answering a benign question ran
env | grepand thekey was printed into the channel transcript. Fix in progress:
block/buzz#5288 (isolates the key, adds a typed
buzz_send_messagetool -would also let us drop the shell workaround).
Also noted under W1
block/buzz#4223 (open): on a closed relay with the agent as a direct member
(our shape), NIP-OA owner attestation never gets recorded, so even after
#5484 merges,
owner-onlywould still not resolve an owner for us. Sameroot cause 403s NIP-AM turn-metric events for our shape - worth checking
before bumping
buzz-agent-toolspast the rev that added them (#4950).nix flake check --no-build .passes.