Ordinary updates now replace idle workers when target compatibility is unknown or incompatible, then reconnect through the existing application launcher. This includes standalone updates whose GitHub metadata has no worker protocol. Known-compatible workers continue running.
Active work and retained delivery defer replacement. Installation-wide admission fencing prevents new work or worker launches from racing replacement across workspaces. Failed installation resumes verified unchanged workers; process identity, ownership and ready-generation checks remain enforced. Worker protocol stays at 18.
One-time upgrade limit: already-running older updaters/workers cannot acquire this correction from publication alone. Affected installations must drain work and pending delivery, deliberately stop, externally install the complete release through their original installation method, and relaunch. A compatible npm upgrade may retain an old worker until that fresh launch. See the first-upgrade instructions, including the cross-installation scope of killall.
The exact source and four native qualification packages passed independent review. Linux and macOS amd64/arm64 qualification covered synthetic multi-workspace updates, active-work preservation, idle replacement, ready reconnection, rollback and authentic affected-version upgrade fixtures. The release workflow attaches native archives/checksums and publishes npm after its gates complete. This is publication, not deployment; real Telegram/WhatsApp delivery and the reported VPS installations were not exercised.