browser/openspec/changes/implement-log-ingest-pipeline/proposal.md

Why

The run job channel can now execute lifecycle work, but server and process logs still have no durable ingest path. This change adds the first log pipeline so run can spool logs locally, upload bounded batches, and receive sequence acknowledgements without mixing log traffic into control, job, or artifact channels.

What Changes

• Add typed run log ingest protocol payloads for log entries, batch ingest requests, batch acknowledgements, and stream cursors.
• Add platform API routes that accept durable log batches, validate stream identity and sequence continuity, acknowledge accepted ranges, and expose bounded query by stream cursor.
• Extend platform service behavior to append log batches to existing log stream metadata, track latest acknowledged sequence, and reject duplicate or out-of-order batches.
• Add a run-side local spool/WAL abstraction that stores unacknowledged batches and removes only acknowledged sequence ranges.
• Extend the run-side platform client with typed log batch ingest calls.
• Add platform service/API tests and run spool/client tests covering retry, acknowledgement, duplicate/out-of-order rejection, and query behavior.

Capabilities

New Capabilities

• log-ingest-pipeline: Durable run-to-platform log batch ingest, acknowledgement, local spool retention, and stream cursor query workflow.

Modified Capabilities

• None.

Impact

• Affects platform/ and run/ only.
• Adds Go protocol/DTO/domain/service/API/spool code and tests for log ingest.
• Updates run/platform protocol and route documentation.
• Does not implement artifact transfer, browser live tail, external log backends, AI log analysis, frontend pages, billing, cloud host sales, or direct plugin/run access.