Remove SCUM server-management client path
This commit is contained in:
@@ -82,12 +82,11 @@ Server list surfaces expose runtime package actions through platform APIs, while
|
||||
- download the latest authorized run package.
|
||||
- push a self-update job to an online run endpoint when the endpoint reports `run.self-update`.
|
||||
- reset the current run key, which invalidates older run packages until regenerated.
|
||||
- generate and download plugin-declared client-manager packages, including SCUM-style companion managers.
|
||||
- reset the current client-manager key separately from the run key.
|
||||
- use plugin-declared remote access actions such as RCON through Platform bridge envelopes.
|
||||
- request dependency checks and typed dependency install jobs.
|
||||
- open live server log stream metadata and request historical log backfill jobs.
|
||||
|
||||
These screens show safe availability reasons, run online/offline status, job/build/dependency progress, artifact IDs, checksums, key generations, fingerprints, and redacted `secret://runtime-keys/.../current` refs. They must not render raw run/client-manager keys, FTP passwords, database DSNs, RCON passwords, host paths, direct run sockets, backend storage URLs, or large inline log bodies.
|
||||
These screens show safe availability reasons, run online/offline status, job/build/dependency progress, artifact IDs, checksums, key generations, fingerprints, and redacted `secret://runtime-keys/.../current` refs. They must not render raw run/client-manager keys, FTP passwords, database DSNs, RCON passwords, host paths, direct run sockets, backend storage URLs, or large inline log bodies. Log bodies are displayed verbatim when the plugin declares them; the browser does not redact or reinterpret them.
|
||||
|
||||
Manual UI smoke checklist:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user