[HeftyKoo]

An upgraded CLI can find a still-running 0.4.0 host that has no maintenance interface. The old updater reports a generic error before --force can restart it; it also exits without restarting when the installed CLI already matches npm stable.

This change lets explicit force recover an older macOS service only after launchctl confirms its PID, serializes legacy maintenance, waits for the old process to exit, and verifies the replacement PID/version. npm installation completes before stopping the service, so installation failures preserve the running host. Update-capable authorization failures remain errors.

Manual npm checks allow 15 seconds per request and retry transient failures once. Force reinstalls the current stable version without permitting downgrades.

Prepare terminal-host 0.4.3 with matching release metadata, installer pin and bilingual upgrade guidance. Extension 0.4.1, DSH 0.4.0 and connector protocol 1 remain unchanged.

Validation:

• pnpm release:audit.
• Historical 0.4.0 host reproduced HTTP 401 in isolation; new diagnostics identify it without stopping the process when force is absent.
• Regression coverage includes PID mismatch/replacement, concurrent legacy maintenance, old-process exit, npm failure, same-version reinstall and transient registry failures.