User requested a checkpoint and stopped all agents. Deployed artifacts remain the last verified releases; unfinished settings/categories/forums are preserved as WIP. See TODO/roadmap for verification and remaining release/updater work.
1.8 KiB
Global channel management
The additive Session.node_admin flag (field 4, default false) advertises permission for the connected Central account to manage this node's global channels. The client never grants this permission itself and clears it on disconnect.
The global sidebar offers text/voice creation, rename and explicit delete confirmation only when advertised. Guild and direct-message views remain outside this UI. Requests use existing ChannelCreate/Delete and ChannelEdit (0x0036); server broadcasts acknowledge success. Errors remain visible in the dialog; ten-second timeout reports uncertainty, and no channel list mutation is optimistic. Channel IDs are client-generated UUIDs, names are trimmed and limited to 100 characters without controls, and every Rust callback rechecks scope/capability.
Server settings and channel context menus
Design: retain the current theme tokens and left sidebar hierarchy. Clicking the server heading opens a compact menu; authorized node administrators can open real server settings (server-name editor plus channel/category management). Right-click on empty channel-list space or a channel opens a keyboard-accessible create menu; a category establishes the parent context. Right-click never joins a voice room. Menus dismiss with Escape or an outside click.
Categories are presentation containers, never voice/text subscriptions. Children retain their actual text/voice/forum kind, and collapsed categories hide children without leaving an active voice room. Parent IDs and server display names persist on the gateway; the native client waits for acknowledgements and fences operations to the session that authorized them. Guild rights and direct messages are not expanded by node-admin controls. Forum topic/reply content is handled separately.