Review round on cron cancel / missed-run policy:
- Receipt recovery, the external-worker waiter and finish_completed_run
read only completed/failed as "the firer booked this attempt". A
cancelled agent run was replayed (job marked failed, repeat spent,
failure notice sent) and a cancelled detached worker was reported as a
worker that died without terminalizing. One FIRER_FINISHED_STATES set
now drives all four readers.
- live_inflight_execution skips the due scan's `missed` rows, so a
missed note booked while a long run is live no longer hides that run
from the dashboard.
- Stopping a ladder re-run passes ladder_rung, like every other terminal
path, so it does not spend a second repeat slot.
- A run whose claim vanished because the job was removed (marker
written, claim dropped) books `cancelled` with the reason at the
first claim check and on the post-run claim-loss path, not
"Fire claim ownership lost".
- request_cancel publishes a private temp file with link(), so
overlapping requests never share a temp path or overwrite the first
reason.
- Monitoring: cron_health knows `cancelled`/`missed` as terminal
statuses, and the shared cron-run metric reports `cancelled` instead
of `failed`.
- Dashboard history: a cancelled agent run's session row carries
"CANCELLED · <reason>".
- A capped missed count keeps its "counting stopped at 1000" note after
the catch-up branch books one fewer than it counted.