Install Hermes for the default agent as the desktop app's self-updating runtime

Choosing Hermes as the default agent built it through mise: a pipx environment with no checkout, so `hermes update` had nothing to move, and the only Hermes that could update itself was the one Hermes Desktop set up. Both paths now run the same setup. omarchy-install-hermes-cli installs the hermes-desktop package and runs upstream's installer from it, pinned to the packaged release and started on main, exactly as Install > AI did; omarchy-install-ai-hermes is that plus opening the app. The terminal, the default agent and the app share one runtime, and it updates itself.

--check answers whether --now has anything left to do, not merely whether a hermes runs: choosing Hermes from the menu asks first and opens a terminal only on a no, so a yes has to mean no minutes-long step would run where nobody can see it. With the app installed that means the runtime's own command, its completion marker and the seeded packaged app; a finished runtime whose command is gone, somebody else's, or its own but unable to run gets it back from upstream's path stage without bootstrapping again. Either way the command has to be the one PATH finds, because omarchy-agent runs bare `hermes` and Omarchy puts mise's shims ahead of ~/.local/bin; a command in the way is named rather than installed over. The modes are named outright because the app's launcher used to call this command with no arguments to reconcile a mise copy; a default of --now would turn every launch into an install. --check still refuses to run the retired wrapper, since running it built Hermes through mise, and a machine whose migration is pending can still have it on PATH.

Provisioning no longer writes the wrapper, Remove Preinstalls no longer looks for it, and the wrapper, the environment it built and what proves them Omarchy's are known to the installer alone: --retire-mise is the migration's whole job, and --now runs the same removal once the runtime installer has saved the wrapper aside, so a user who chose Hermes before their migration ran is not left with mise's shim answering `hermes`. Only the wrapper proves the environment is Omarchy's, at its path or in that saved copy, so the environment goes first and the wrapper last, judged by mise neither having it installed nor still requesting it; a removal that leaves either behind, or a listing that cannot be read, mise missing included, stops with the commands to finish by hand and leaves the migration pending. The migration that once installed the wrapper is kept as a no-op for late updaters, and one whose default agent was Hermes is told to choose it again.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Codex XHigh <noreply@openai.com>

migrations/1787760281.sh

@@ -1,25 +1,3 @@
 echo "Install the Hermes CLI wrapper for existing installs"
 
-# Users who removed the preinstalls opted out of the mise wrappers, and Hermes
-# is one of them.
-[[ -f $HOME/.local/state/omarchy/preinstalls-removed ]] && exit 0
-
-# Hermes Desktop provides its own Hermes. The installer stands aside for it,
-# removing the mise copy and the Omarchy wrapper an earlier install may have
-# left beside the app. It also reports when the app has not finished setting
-# Hermes up, which is the app's to finish, not this migration's to fail on.
-if omarchy-pkg-present hermes-desktop; then
-  omarchy-install-hermes-cli || true
-  exit 0
-fi
-
-# Anything already answering to hermes that this installer did not write --
-# an official install, a hand-rolled wrapper, even a dangling link -- belongs to
-# the user and stays exactly as it is. The installer is asked rather than
-# matched against here, so there is one answer to who owns that wrapper.
-wrapper="$HOME/.local/bin/hermes"
-if [[ -e $wrapper || -L $wrapper ]] && ! omarchy-install-hermes-cli --owns; then
-  exit 0
-fi
-
-omarchy-install-hermes-cli
+# Nothing to install any more: the mise-backed wrapper this wrote was retired in favour of the self-updating runtime, and the migration that retired it clears any it had already written.

migrations/1790017600.sh

@@ -0,0 +1,9 @@
+echo "Retire the Hermes that mise built; Hermes now updates itself"
+
+# Hermes installs the way Hermes Desktop does now: upstream's installer makes a checkout under ~/.hermes that `hermes update` fast-forwards. The wrapper that built Hermes through mise had nothing an update could move, so it goes, with the mise environment it built. The wrapper, the environment and what proves them Omarchy's are known to the installer and nowhere else, so it is asked rather than matched against here; it leaves a hermes the user set up themselves, and a mise environment without the wrapper, as they are, and exits non-zero with the commands to finish by hand when the environment cannot be removed, which keeps this pending rather than done.
+omarchy-install-hermes-cli --retire-mise
+
+# Choosing Hermes again is what installs the runtime, and nothing else will.
+if [[ $(omarchy-default-agent) == "hermes" ]] && ! omarchy-install-hermes-cli --check; then
+  echo "Hermes is the default agent but is no longer installed. Choose it again under Setup > Default Agent, or run: omarchy default agent hermes"
+fi