[giscebot]

Summary

• preserve a deferred executor restart when a later refresh sees the newly installed release as noop;
• keep the original deferred service plan actionable while refreshing the installed version metadata;
• cover the production sequence end to end: deferred update, drained job, noop refresh and completion restart.

Production incident

During the v0.88.0 rollout, webhook ingress and dashboard loaded the new version while the executor kept its pre-release process. The recorded completion state was later replaced by a noop plan with executor_reload_pending=false, so the completion pass no longer had an executor restart to apply.

The production executor has been restarted manually after confirming an empty queue. This PR prevents the pending restart from being lost on future releases.

Validation

• regression confirmed RED before the implementation;
• 36 passed in tests/test_autoupdate.py;
• 694 passed in the full Python suite;
• git diff --check clean.

Refs #299

TASK: TASK-85718

[pilipilisbot]

Post-merge sync: #337 is integrated as bb4a8eb73b22b1c6662a6f421227dadd07fbaf89. I checked the merged diff: the noop refresh retains the pending executor decision/service plan while updating installed-version metadata, and the regression covers deferred update → drained job → noop refresh → completion restart. Dashboard and Python 3.11/3.12 checks passed on the PR head.

There is no dedicated github-agent-bridge-pr-337 worktree to clean up. This confirms merge, not release/deployment: the #299 rollout checklist still needs its #337 item reconciled after deployment, and the seven-day observation epoch should start only from the verified final deployment timestamp. No production action was taken here.

[giscebot]

Review follow-up: he revisat el commit ce4678f ja fusionat. No hi veig cap finding bloquejant: record_update_plan() conserva la decisió diferida i el service_plan només quan el refresh és noop i hi ha un reload de l’executor pendent, mentre actualitza la versió instal·lada.

Validació local: 36 passed a tests/test_autoupdate.py i git diff --check net. La suite completa local s’ha aturat al 72% per no deixar processos penjats; els checks CI de la PR (dashboard, Python 3.11 i 3.12) consten verds. Això valida el canvi de codi; el rollout i la nova finestra d’observació continuen sent passos operatius separats.