cmux NEXT updater: the update log stays on disk (notice level)
The 2026-10-20 slow Restart to Update (cx-p00l3, companion #22919) left no trace of why its first install failed: every UpdateLogBuffer line logged at info level, which the unified log does not keep. Lines now log at notice level; per-chunk download and extraction progress stays info. Also updates the UpdateWindowHandoff / UpdaterService docs for the relaunch-time hide in #22919.
High tier (CmuxNextUpdater): needs an approving review from a collaborator.
Changelog
none
Observed / Not run
- Fleet compile + SilentBackgroundUpdateTests, UpdateCheckFeedbackTests (cmux-ci, Xcode 26.6).
- Not run: a live update with
log showreading the notice lines.
š¤ Generated with Claude Code
![View with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/view-with-codesmith-dark-v3.svg)
![Autofix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/autofix-with-codesmith-dark.svg)
Need help on this PR? Tag @codesmith-bot with what you need.
Summary by cubic
Keeps the update log on disk after the app quits so a failed Restart to Update leaves a trace.
The 2026-10-20 slow update (cx-p00l3, companion #22919) left no record of why its first install failed: every UpdateLogBuffer line logged at info level, which the unified log does not retain. Update log lines now log at notice level; per-chunk download and extraction progress stays info. The UpdateWindowHandoff and UpdaterService docs now describe the hide as happening when Sparkle commits to the relaunch (updaterWillRelaunchApplication).