admin343/run
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify live relay run logging

Browse Source
This commit is contained in:
npc0-hue
2026-09-01 14:23:58 +08:00
parent c8f5213954
commit 65da73eff0
8 changed files with 19 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+3 -3
View File
@@ -8,11 +8,11 @@ Do not rebuild the old all-in-one WebSocket model. Keep these workloads separate
- Control: hello, heartbeat, version, capabilities, capacity.
- Job: claim, ack, progress, result, cancel, reconcile.
- Logs: local spool, batch upload, sequence acknowledgement, retry.
- Logs: current supervised stdout/stderr live relay through `/api/v1/run/logs/relay`; no local durable log spool, cache, resend backlog, or sequence-ack dependency.
- Artifacts: chunks, checksums, resume, throttling.
- Game client bridge: optional in-game command/snapshot channel.
Artifact transfer must not block control heartbeats, job result reporting, or log upload.
Artifact transfer must not block control heartbeats, job result reporting, or current live log relay.
## Structure Rules
@@ -30,6 +30,6 @@ Run must not contain game-specific lifecycle logic. Do not add hardcoded game na
If a lifecycle flow needs "install if missing", "stop before update", "validate via SteamCMD", or "start with game-specific arguments", run should execute the plugin-declared action through generic capabilities. Fix missing generic capabilities in run when necessary, but keep the game policy and concrete commands in the plugin action assets.
Run should supervise plugin-declared start commands generically: hide started process windows when the operating system supports it, capture the supervised stdout/stderr streams, and upload those streams through log ingest. Do not replace plugin-declared process output with game-specific file inspection.
Run should supervise plugin-declared start commands generically: hide started process windows when the operating system supports it, capture the supervised stdout/stderr streams, and push only current observed output through live log relay. Do not persist supervised process output in a local log database/cache, do not wait for platform delivery acknowledgement, and do not replace plugin-declared process output with game-specific file inspection.
Do not introduce per-game runtime files such as `scum_deployment.go`. Prefer generic action execution, dependency helpers, process supervision, and manifest-declared capability checks that any plugin can use.