main=2904fea7d593c687393b7ad2434de03d590871cd pr_head=0df1ba9eaefa23c18c535514cbf0ece4a67aae75 merge_base=b5a226e49c52ecab4ddc2d678a7012d97e651a6a
PASS  issue #17490 is closed as completed by merged PR #19652
PASS  #19652 is on main as d0d0608b6b (fix(server): a remote update points the service unit at the runtime it committed (#19652))
PASS  at the PR's merge-base the server-start prune passed no unit reference (the bug the PR targets)
PASS  main passes the service definition's program as a prune reference in both prune call sites
 ✓ |t3| src/cloud/pr23250Proof.test.ts > PR 23250 claim > pruning keeps the runtime the service definition starts though state names only B and C 8ms
 ✓ |t3| src/cloud/pr23250Proof.test.ts > PR 23250 claim > control: without the service definition the launcher runtime is pruned 4ms
      Tests  2 passed (2)
PASS  on main, pruning after A->B->C keeps launcher runtime A (named only by the service definition) and removes the unreferenced runtime; the control without the definition prunes A
⎯⎯⎯⎯⎯⎯⎯ Failed Tests 1 ⎯⎯⎯⎯⎯⎯⎯
      Tests  1 failed | 1 passed (2)
PASS  with main's unit reference removed, the retention case fails (runtime A is pruned): main's reference is what fixes #17490
 ✓ |t3| src/serviceLauncher.test.ts > service state persistence > commits and repoints systemd after a protocol-3 local upgrade only after the trial reports prepared 2927ms
 ✓ |t3| src/serviceLauncher.test.ts > service state persistence > commits and repoints launchd only after the trial reports prepared 2776ms
 ✓ |t3| src/serviceLauncher.test.ts > service state persistence > commits and repoints Task Scheduler only after the trial reports prepared 2808ms
      Tests  3 passed | 27 skipped (30)
PASS  main repoints systemd, launchd and Task Scheduler definitions at the committed runtime after an update
VERDICT: CLOSE (already-fixed) - main retains the runtime the service definition starts and repoints it on update (#19652, #22253/#25870)
exit=0