[Bug] Desktop: creating a second custom sidebar section is not easily discoverable

[w-y-a-t-t]

Summary

A user reported that Buzz Desktop (latest release, v0.5.2) doesn't make it easy to create more than one custom sidebar section for organizing channels.

Why this looks real

This lines up with the stated problem behind open PR #2947 ("feat(desktop): add sidebar categories and manual channel ordering"), which is not yet merged as of v0.5.2:

Buzz already supported encrypted custom sections and section reordering, but category creation was buried in a channel context menu and exact channel order was not persisted.

Searched open/closed issues for section, category, sidebar, folder, "more than one", "add section", "create category", channelSectionsSync, etc. — found no existing issue describing this specific creation-flow friction. Closest related items, which cover different gaps:

• Mobile: render synced custom sidebar sections / channel order (desktop-only today; mobile has stars only) #3363 — mobile doesn't render synced custom sections at all (desktop-only today)
• feat(cli): owner-authorized management of synced sidebar categories #3590 — no CLI/agent-automatable way to manage sections

Neither describes the in-app discoverability problem for creating a second section on Desktop itself.

Reproduction

Not yet confirmed first-hand — filing so it's tracked, reporter will follow up with exact repro (OS, Desktop version, and whether the second-section action is missing, disabled, or silently no-ops) in a comment below.

1. On Desktop, create one custom sidebar section and move a channel into it.
2. Attempt to create a second section.
3. Actual: not easily possible / not obvious how.
4. Expected: creating additional named sections should be as easy as creating the first one.

Related

PR #2947 appears to fix this directly (moves category creation to the visible Channels actions menu, adds full create/rename/reorder/delete support for multiple categories) but is still open (REVIEW_REQUIRED) and not in v0.5.2. If it merges, this issue can likely close as fixed by it.