Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.272,
Internal ChangesSection of the release
What
The background runner's failure-reporting path, covering runner:session and runner:stuck logging, gained new timing constants (500ms, 1000ms, 2000ms, and 3000ms) and an abort helper. These are used when retrying a failed attempt to post a failure result, and to detect when another runner has already taken over a session, logged as a "stale epoch" rejection.
Why
This makes background session failure handling more robust: retries are now timed explicitly, and a runner can tell when it's no longer the current owner of a session instead of continuing to report against it.
