Keep Run and Platform logs opaque
This commit is contained in:
@@ -6,6 +6,10 @@ boundary; this companion alone parses the SCUM login format and publishes the
|
||||
typed player snapshot used by the plugin page. Platform and Run never inspect
|
||||
or redact those log bodies.
|
||||
|
||||
The long-running companion stores only its typed snapshot sequence state in
|
||||
`snapshot-sequences.json` beside `config.yaml`. This keeps the `players/current`
|
||||
stream monotonic across process restarts; it contains no raw log records.
|
||||
|
||||
This plugin-owned fixture proves the Platform Client Manager and Game Client Bridge integration without adding SCUM behavior to Run. The command registers the deployed component, sends one heartbeat, claims at most one command, processes only `companion.diagnostics`, and uploads one typed `companion.health` snapshot.
|
||||
|
||||
Use it only with a dedicated non-production server instance whose bridge queue contains no shared or production work. The claim API cannot filter by command type, so this smoke command must never target a shared or production queue.
|
||||
|
||||
Reference in New Issue
Block a user