browser/openspec/changes/add-scum-source-rcon-transport/proposal.md

Why

The SCUM UE4SS lifecycle now provisions a protected, loopback-only Source RCON listener, but Run's declared rcon adapter is still a placeholder that reports success without connecting to the listener. Operators therefore cannot actually send chat text or SCUM admin commands through the platform, and raw commands must not become a durable command-history or audit feature.

What Changes

• Add a typed SCUM RCON dispatch path for direct chat delivery and raw SCUM admin commands, with no secondary confirmation step and no persisted command/audit payload.
• Freeze a ready Windows UE4SS extension's safe loopback Source RCON connection metadata into a single-attempt Run job; reject unpublished, incompatible, or non-SCUM extension states before dispatch.
• Keep the raw command only in a bounded, one-time, in-memory Platform input broker. The signed active Run lease retrieves it once; database jobs, Run journals, browser responses, audit events, logs, and result messages contain no command text or RCON password.
• Replace Run's placeholder RCON adapter with a bounded Source RCON client that reads the generated protected config inside its scoped workspace, authenticates only to 127.0.0.1, and sends the command using standard framed packets.
• Add a server-management-console RCON panel for chat broadcasts/targeted chat and raw commands. It reports safe queued/succeeded/failed state without building a command history.

Capabilities

New Capabilities

• scum-source-rcon-command-dispatch: Platform authorization, one-time command delivery, safe browser contracts, and SCUM-specific dispatch constraints.
• run-source-rcon-execution: Run-side loopback Source RCON authentication, packet exchange, response classification, and failure handling.

Modified Capabilities

• None.

Impact

• platform/: domain/DTO/API contracts, command validation, transient input broker, fenced Run-only input endpoint, lifecycle/extension resolution, and focused tests.
• platform_web/: typed API client, schemas, and the existing server-detail management surface.
• plugins/: SCUM lifecycle capability declaration and manifest tests.
• Independent run/: protocol copy, Platform client, Worker dispatch, Source RCON adapter, and unit/integration tests.
• The UE4SS DLL source remains unchanged. No user-side compiler, generic remote socket, direct browser-to-RCON connection, Linux DLL substitute, raw command persistence, or command audit trail is introduced.