3 people f8f2ef0440 feat(cli): add --visibility flag to channels update (#5119) ...

## Why
`buzz channels update` could already change name, description, and TTL,
but the SDK/relay/DB path for channel visibility was unreachable from
the CLI.

## What
- Add `--visibility open|private` to `buzz channels update`
- Pass the visibility value through to `build_update_channel`
- Add guard tests proving empty updates still fail and visibility-only
updates are accepted

## Risk Assessment
Low — this is limited to the buzz-cli update command and uses existing
SDK validation plus existing relay/DB handling.

## References
- Spike notes: `RESEARCH/SPIKE_CHANNEL_VISIBILITY_TOGGLE.md`
- Local validation: `cargo test -p buzz-cli`

Generated with Codex

Signed-off-by: Cameron Hotchkies <chotchkies@block.xyz>
Co-authored-by: Lazy Joe <dbd8c9941ba6dafebcef0abc015b65e75d52e7452f2ce483c9c3fd4d180f2504@buzz.block.builderlab.xyz>

2026-08-10 14:48:30 -07:00

..

commands

feat(cli): add --visibility flag to channels update (#5119)

2026-08-10 14:48:30 -07:00

agent_management.rs

…

client.rs

feat: Buzz entity links — rich preview cards + in-app navigation for repos, PRs, and issues (#4695)

2026-08-04 17:54:14 -04:00

error.rs

fix(cli): retry transient relay failures and raise timeouts (#2196)

2026-07-21 12:17:44 -04:00

lib.rs

feat(cli): add --visibility flag to channels update (#5119)

2026-08-10 14:48:30 -07:00

links.rs

feat: Buzz entity links — rich preview cards + in-app navigation for repos, PRs, and issues (#4695)

2026-08-04 17:54:14 -04:00

main.rs

…

validate.rs

…