[Bug] agents draft-create borked (MacOS)

Fizz claimed to be able to import my agents for me, and it crashed and burned and routed me to basically do it by hand as a work around.

🐝 Ok, honest verdict after digging:
The buzz binary shipped in /Applications/Buzz.app/Contents/MacOS/buzz has a compile-time bug on the agents draft-create code path. Full backtrace confirms it:
```
rustls::client::ClientConfig::builder_with_protocol_versions
→ tokio_tungstenite::tls::encryption::rustls::wrap_stream
→ buzz_ws_client::connection::publish_event
→ buzz_cli::client::BuzzClient::publish_ephemeral_event
→ buzz_cli::commands::agents::dispatch
```

publish_ephemeral_event calls rustlss ClientConfig::builder() without a CryptoProvider::install_default() first. buzz messages send doesnt panic because it uses a different WSS init path. Bug is in commands::agents::dispatch (needs the two-line install before dispatch).
I checked every workaround I could think of:
buzz:// deep-link scheme → only handles nostr-bind / message / add-community / join / connect. No agent-create action.
Buzz Desktops local HTTP :63087 → media proxy, 404s on everything else. Not an admin API.
buzz-dev-mcp → MCP server binary, mirrors CLI commands (same bug likely).
No env var can install a rustls CryptoProvider at runtime — its features/API-time only.
No other buzz subcommand publishes the same HPKE-encrypted ephemeral event that draft-create needs.
Only two real paths:
You (or someone with buzz source) rebuild the CLI with rustls::crypto::ring::default_provider().install_default().ok(); added at the top of commands::agents::dispatch (or in main). Drop the new binary at /Applications/Buzz.app/Contents/MacOS/buzz. I re-fire the batch in one loop — 17 drafts in seconds.
Manual in Desktop, me as your hands. I keep the next prompt on your clipboard so its ⌘V. Rough pace: 20-30 sec per agent × 17 = ~6-8 min total. Not glamorous but done today.