Skip to content

refactor: make self-update launch readiness explicit - #6695

Merged
atomantic merged 2 commits into
mainfrom
claim/issue-6694
Sep 9, 2026
Merged

refactor: make self-update launch readiness explicit#6695
atomantic merged 2 commits into
mainfrom
claim/issue-6694

Conversation

@atomantic

Copy link
Copy Markdown
Owner

Summary

Make self-update launch readiness explicit: launchUpdate returns a refusal or a started result with a separate completion promise. The shared handoff awaits launch, observes completion, and preserves existing update errors, socket events, and lock handling. executeUpdate remains a compatible adapter for callers awaiting the full result.

Test plan

  • All 100 tests passed across the six focused server suites: self-update launcher, executor, update routes, app updater, preflight parity, and app sockets.
  • Fake process handles verify pending completion, refusal, spawn failure, progress, callback compatibility, and later failure reporting. No live update scripts were executed.

Closes #6694

@atomantic
atomantic merged commit 2e83895 into main Sep 9, 2026
7 checks passed
@atomantic
atomantic deleted the claim/issue-6694 branch September 9, 2026 05:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[cognitive-load-update-launch-phases] Make self-update launch readiness explicit in the executor contract

1 participant