Bryan Helmkamp 2b30689e77 Settle a worker's run at Petri's finish, not at the worker's exit ... A worker-backed run's in-memory managed run settled only when the worker process exited. GET /runs/{id} reads the stored summary, which the projector ends at Petri's own `run.finished` record, a moment before the worker stores Fabro's terminal lifecycle record and exits. The delete precheck prefers the managed run, so a delete issued in that window was refused with 409 "cannot remove active run". Against a real worker the window hit about six times in ten. The server sees both records before they are stored: `run.finished` on the coordinator log through the worker's records endpoint, and the terminal lifecycle record through the platform-records endpoint. The managed run now settles at either, ahead of the store, so the view never reports the run ended while the managed run still says running. The stream follower no longer reopens a settled run with the records that precede its terminal one, and the worker's exit keeps the settled status: it reaps the process, records a missing terminal record as it did, and takes the store's status only when the store ended the run differently. The mapping from Petri's finish to the run's status is the projection's own, shared with its fold. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-09-21 03:49:44 -04:00
..
it	Settle a worker's run at Petri's finish, not at the worker's exit	2026-09-21 03:49:44 -04:00
build_git_metadata.rs	refactor: organize crates into three layers	2026-07-23 17:59:34 -04:00