True caches whose schema belongs to the writing install move into the
runtime dir's cache: the model catalog, OpenRouter metadata, local
endpoint probes, the Nous recommended list, and the uv self-update stamp
(that one silenced a SECOND install's update for a week). Media and
session artifacts stay in HERMES_HOME — audio_cache and friends are
profile state with a cache-shaped name.
Deleted the $HERMES_HOME/node_modules/.bin agent-browser rung: no
installer has written it for several releases, and doctor now asks the
one resolver where managed Node lives.
Docs: the installer list said Node v22 while the pins say 26 (the drift a
second source invites), and never mentioned gh. Added a managed-runtimes
note explaining that Hermes pins its own copies, never shadows a
user-installed tool, and keeps two installs separate.
Regression baseline: tests/hermes_cli/ diffed against stashed HEAD — the
same 55 pre-existing failures, no new ones (the 3 that differed all
reproduce on HEAD or pass 3/3 in isolation).
