Bump block/buzz to pick up messages search --before - #3362

What this does

Moves the block/buzz pin from c8d736642e1c to 0e6037c74d67 (block/buzz#9382). That one pin, the buzz-audio-client git dependency in src-tauri/Cargo.toml, also picks the revision that scripts/build-buzz-cli.mjs builds the bundled buzz CLI from. So the bundled CLI gains buzz messages search --before and --before-id, for paging back through an author's messages.

Two commits:

1. The bump. Two lines: the rev in src-tauri/Cargo.toml and the matching source line in Cargo.lock. Nothing else in the lock file moves, and --locked builds accept it.
2. A build-folder fix in scripts/build-buzz-cli.mjs. All revisions used to share one Cargo build folder, target/buzz-cli-build. Cargo treats a git checkout as unchanging, so after a pin bump it trusted the old revision's build and staged the old CLI under the new revision's name. This bump hit that: on a machine that had built the old rev, the staged buzz had no --before. Each revision now builds in target/buzz-cli-build/<rev>. The cost: the first build after each bump compiles the CLI from scratch (a few minutes), and each revision's build folder stays on disk until someone deletes it, as the target/buzz-cli/<rev> install folders already do. docs/releases.md explains why, and tests/integration/buzz-cli.test.mjs checks that two revisions get different folders.

What the bump brings in

The range has 88 block/buzz commits. Only two things from block/buzz ship in Buzz Desktop: the buzz-audio-client crate and the bundled buzz CLI, plus the in-repo crates it builds with (buzz-core, buzz-sdk, buzz-ws-client, buzz-persona).

Huddle audio client (crates/buzz-audio-client, one change)

• feat: send a User-Agent on relay WebSocket upgrades buzz#9246: the audio WebSocket upgrade now sends User-Agent: buzz-audio-client/<version> when the caller didn't set one. Buzz Desktop sets no User-Agent on the audio socket (src-tauri/src/relay/huddle/audio.rs), so huddle audio connections now carry this header. No API change; the desktop code compiles unchanged.

Bundled buzz CLI

• buzz-cli: add --before and --before-id to messages search buzz#9382: messages search --before <unix ts> (sent as the filter's until) and --before-id <event id> (requires --before; resumes after that event so events from the same second aren't repeated or skipped). --before-id with --query is a usage error. Without the new flags the filter is unchanged.
• NEXUS-4336: Wait for desktop-provider socket ownership proof buzz#9270: desktop pairing. Before sending credentials or requests to Buzz Desktop, the CLI checks that the socket it connected to belongs to the same OS user. It now retries that check on the same open connection within the existing 5-second limit, instead of failing on the first miss. A wrong user or a failed lookup still fails at once. The macOS lsof lookup now caps its output and checks the exit status. CLI-side only: the desktop provider protocol is unchanged.
• fix(cli): preserve attachments across successive edits buzz#9226: messages edit keeps a message's attachments across successive edits, and adds --clear-attachments. It asks the relay for the current effective edit first. Against a relay without that lookup (added in Buzz Relay 0.3.0), messages edit now refuses with "upgrade the relay before editing" instead of dropping attachments.
• feat: send a User-Agent on relay WebSocket upgrades buzz#9246: the CLI's relay WebSocket upgrades also send a User-Agent.
• Shared crates: fix(relay): saturate filter limits instead of casting buzz#9230 (filter limits saturate instead of casting) and fix(media): revoke private channel attachment reads buzz#9077 (media read checks and SDK builders, mostly relay-side).
• test: fix timing-dependent unit tests in buzz-cli, buzz-agent and buzz-admin buzz#9273: test-only timing fixes.

Not shipped in this app (no effect on Buzz Desktop)

• Mobile app: about 45 commits (iOS gallery and video, Solo chats, Activity, notifications, pickers).
• Relay and server: about 28 commits (cross-node delivery, filter fixes, DM rules for agents, invite previews, NIP-FI policy, single-community mode, database pool recovery, Buzz Relay 0.3.0 release).
• CI, release tooling, docs and the old desktop client in block/buzz: about 10 commits.

Testing

Run by an agent on macOS (Apple Silicon):

• cargo fmt --all --check: pass.
• cargo clippy --workspace --locked --all-targets -- -D warnings: pass.
• cargo test --manifest-path src-tauri/Cargo.toml --locked: 1121 + 24 passed, 0 failed, with 15 tests skipped for local reasons that have nothing to do with the bump. The 21 relay::huddle::audio tests pass. Skipped: the media-conversion tests (media_preparation, converted_spool), because this machine's Homebrew ffmpeg can't load libx265, and window_state::tests::onboarding_snapshot_is_kept_until_next_launch_restore, which crashes the test process (SIGSEGV) on this machine with the old pin too. CI runs the full suite on Linux.
• node scripts/test-buzz-cli.mjs (stages the CLI the way a desktop build does, then runs it): pass. The staged buzz messages search --help lists --before and --before-id.
• Build-folder fix, from an empty Cargo target folder with no cache clearing in between: node scripts/build-buzz-cli.mjs --dev at the old rev staged a CLI without --before-id. Then, at the new rev, Cargo recompiled buzz-cli in its own folder and the staged CLI listed --before-id. Before the fix, the same sequence on a real machine reported Fresh buzz-cli and staged the old binary.
• node --test tests/integration/buzz-cli.test.mjs tests/integration/dev-commands.test.mjs: 63 pass.
• Desktop pairing against a running Buzz Desktop: buzz auth desktop list with the new CLI reports an existing pairing as accepted. That path runs the new same-user socket check on macOS.
• Live paging through that pairing, read-only: an author search with --since … --before <now> --limit 5, then a second page with --before <last created_at> --before-id <last id>. Page 2 started right after page 1's last event, with no overlap and nothing newer than the cursor. The old CLI rejects --before as an unknown argument.

Not tested:

• A live huddle. Audio is covered only by the existing relay::huddle::audio unit tests, not by a real call.
• Pairing a new CLI from scratch (buzz auth desktop pair), which needs a person to click Allow.
• messages edit against a live relay (it writes).
• Windows and Linux builds; CI covers Linux.

buzz-review-completed

🤖 Generated with Claude Code