Fixes the background runon launch reply so a job the runner has already accepted returns a refreshed task handle with running status instead of a stale starting reply, and drops the input-capture and no-rerun warnings once acceptance is recorded.
Accepted background launches reply with the current remote phase and runner job ID; foreground calls keep their normal wait path.
Replies decided before acceptance (capture-deadline waits) correctly stay starting with the no-rerun note, and the race tests now assert both sides by gating runner acceptance.
Adds the release note and the slice descriptor for the land-runon-launch-reply-test-race benchmark.
Confidence Score: 5/5
The PR appears safe to merge; no new actionable issues were found.
Summary
Refreshes accepted background runon replies with the task handle and saved runner details.
Accepted background runon jobs now get an up-to-date launch reply.
The earlier unnumbered thread was manually resolved by ualtinok without an explanatory reply. The module-drain case retains its strict running check.