[thdxr]

Fixes #915

Automated fix from the Hex issue pipeline. The fixer and reviewer saw only the validated issue form, never the issue text.

Form

• Area: CLI control commands and restart after updater activation (linux)
• Summary: On Linux, after the updater activates a newer build, the newer command-line tool reports an older running Hex (one that predates the local API transport change) as not running. The restart command also fails to restart into the new build, and nothing tells the user that a restart is needed.
• Expected: The newer CLI should say that an older Hex is running and name the fix (restart). The restart command should restart Hex into the activated build.
• Actual: The CLI reports 'Hex is not running; run hex start' with exit 3. Dictation key binds do nothing, and the start command wrongly says Hex is started but still loading. No notice of a pending update restart is shown on a headless setup. Restarting the systemd unit manually fixes it.

Change
On Linux, when no current Hex answers through the local API, the CLI now checks whether something still answers on the old service.sock. If it does, the control commands, hex start and hex settings apply give an outdated error that says to run hex restart, instead of not-running (or, for hex start, a wrong "started"). hex restart now restarts the systemd unit into the installed build and waits for it to answer; docs/cli.md describes this and lists the new error code.

Gates: build passed in the apollo sandbox; policy clean; console-anthropic-cyber/claude-opus-5-5 approved.
Run: 915-2026-11-01t20-47-58-514z

— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊