VNOX-Client/docs/maintenance/forum-client.md
loki5512344 f04691c3cd
chore(client): checkpoint deployed features and unfinished server management
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.
2026-11-01 15:31:21 +01:00

36 lines
2.3 KiB
Markdown

# Forum client interaction contract
A forum is a channel containing separately addressable topics. It is not a text
channel with a different icon. Gateway owns the topic list, creation, history and
replies; the client displays successful results only after acknowledgement.
The matching LNEx specification must define the wire payloads and capability
before implementation of network commands.
The main panel has two views: a topic list with title, author and reply count,
and an opened topic with its title, opening message and chronological replies.
Creating a topic requires a title and first message. Opening a topic fetches its
history. Returning to the list preserves unsent input within the same server;
disconnecting or changing server clears forum data and pending operations.
Loading, empty, denied and failed requests have explicit visible states. Failed
requests keep input, and provide retry instead of claiming success.
Use existing Theme colors and font scale, left-aligned topic rows, the current
focus styles and normal sentence-case actions. Navigation remains in the sidebar.
The forum panel has no voice controls or membership side effects. Selecting a
category is navigation only. Only an explicit voice-channel selection may request
voice membership; arbitrary callbacks for categories or unknown channel kinds
must be rejected. Browsing a forum does not disconnect an existing voice session.
Forum commands require the advertised server capability and an authenticated
session. Old servers receive no new forum packets. Requests carry correlation
IDs and the selected forum/topic context; stale responses cannot switch the
current topic or replace another server's data. Node and guild visibility and
write permissions are enforced by Gateway, with errors surfaced in the forum.
Retries use a new request ID; creation/reply input clears only on matching success.
Pagination is bounded by the server contract and must not silently truncate a
thread without a way to fetch further results.
Regression checks cover wire encoding/dispatch, request correlation, failed
creation preserving drafts, stale results after selection/session changes,
capability gating, topic/reply history, and category/forum navigation without
voice capture. GUI checks use an isolated virtual display and profile only.