6 Commits
Author SHA1 Message Date
npc0-hue e73fe765c3 Recover log streams stuck on straddling spool segments
A segment that the platform already acknowledged could still be extended by
the next tailed line, so its checksum covered entries stored under a different
batch. The platform then rejected the same body every second while
RejectStreamAfter skipped it, because it only quarantined segments that start
after the platform latest. Every newly allocated line was quarantined by the
following recovery pass, so live log ingest never resumed.

Quarantine pending segments that reach beyond the acknowledged range, never
extend a segment the platform already stored, and log the gap recovery so a
stalled stream is diagnosable from the spool alone.
2026-09-16 13:34:45 +08:00
npc0-hue 330b1c0130 Keep run logs opaque and streamline transfers 2026-09-03 16:40:05 +08:00
npc0-hue 40b704d60f Keep Run startup independent from log backlog 2026-08-31 18:13:38 +08:00
npc0-hue 4277791cb7 Recover managed process log sessions 2026-08-31 12:16:44 +08:00
npc0-hue d5f4d34e07 Prioritize fresh process log sessions 2026-08-31 05:11:54 +08:00
npc0-hue 8e02a316fa init 2026-08-26 09:56:43 +08:00