Clarify live relay run logging

protocol/artifact.md

@@ -1,6 +1,6 @@
 # Run Artifact Contract
 
-Artifacts move files and large payloads between platform and run without blocking logs or control.
+Artifacts move files and large payloads between platform and run without blocking current live logs or control.
 
 ## Implemented Routes
 
@@ -34,9 +34,9 @@ Run stores unacknowledged `ArtifactChunkUploadRequest` payloads in the local art
 - Transfers must be resumable.
 - Transfers must be checksummed.
 - Artifact concurrency must be limited.
-- Artifact transfer must not block control heartbeat, job ack/result, or log upload.
-- Artifact transfer is lower priority than control, job lifecycle metadata, and durable log ingest.
-- Slow or retrying artifact chunks must not prevent log spool acknowledgement cleanup or terminal job result submission.
+- Artifact transfer must not block control heartbeat, job ack/result, or current live log relay.
+- Artifact transfer is lower priority than control, job lifecycle metadata, and current live log relay.
+- Slow or retrying artifact chunks must not delay live log relay or terminal job result submission.
 - Control, job, and log routes must reject artifact chunk payloads or transport details rather than accepting them through lightweight channel payloads.
 
 Run artifact queues use owner-only atomic JSON entries and retain chunks until an exact transfer/artifact/index acknowledgement covers them. A low-priority uploader retries pending chunks independently of control, jobs, and logs.

protocol/control.md

@@ -24,7 +24,7 @@ Control is the lightweight high-priority channel between run and platform.
 - Control payloads must be small.
 - Control events wake Run only; they must not carry job assignments or execution input.
 - Control must not carry logs, artifact chunks, or long job result bodies.
-- Control must have priority over job execution, log upload, and artifact transfer.
+- Control must have priority over job execution, current live log relay, and artifact transfer.
 - Heartbeat capacity summaries must remain metadata-only and must not mention or carry heavy channel payloads.
 
 ## Deferred Channels

protocol/log-ingest.md

@@ -18,9 +18,9 @@ channel. Game plugins own durable log storage and analysis.
 
 - `LogBatchIngestRequest`: run ID, session token, server instance ID, stream ID, source, sequence range, compression metadata, checksum, and bounded entries.
 - `LogEntry`: sequence, timestamp, level, line, parser metadata, and redaction state.
-- `LogBatchIngestResponse`: accepted sequence range, latest acknowledged sequence, duplicate flag, retry hint, and server time.
+- `LogBatchIngestResponse`: accepted sequence range, latest stream metadata sequence, compatibility duplicate/retry fields, and server time.
 - `LogStreamCursorRequest`: stream ID, sequence cursor, and limit.
-- `LogStreamCursorResponse`: ordered entries, next cursor, and latest acknowledged sequence.
+- `LogStreamCursorResponse`: compatibility ordered entries, next cursor, and latest stored metadata sequence.
 - `LogStreamEventResponse`: safe browser event containing server ID, stream metadata, latest sequence, and one log entry.
 
 Autonomous lifecycle output uses

protocol/protected-request.md

@@ -33,6 +33,6 @@ diagnostics without forwarding handler errors or response bodies. These errors
 affect only the current request.
 
 Management-program stdout and stderr are bounded, redacted, and sent to the
-durable log channel with source `management-program` and streams
+live log relay with source `management-program` and streams
 `management-program.stdout` / `management-program.stderr`. They are not file
 execution logs and are never embedded in job result content.