Bryan Helmkamp e75d8a2fb0 Fix attach hanging on Linux CI when engine exits before attach starts ... The attach loop's PID liveness fallback used `last_seq > 0` (store path) and `!progress_file_is_empty` (file path) to keep the engine "alive" when no launcher record could be found. These conditions are always true once events exist, so the loop never exited via the PID path after the launcher record was cleaned up by start_run or active_launcher_record_for_run. The store-based terminal status check (the other exit path) only read from the SlateDB DbReader, which may not see data still in the WAL or not yet visible via manifest poll. Adding a disk fallback to read status.json ensures the check works even when the store reader has a stale view. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>		2026-04-01 14:32:16 -04:00
..
crates	Fix attach hanging on Linux CI when engine exits before attach starts	2026-04-01 14:32:16 -04:00
packages/fabro-api-client	Prefix API routes with /api/v1	2026-03-30 16:17:06 -04:00