706f33d424
The shared checkout serves every profile, but hermes update migrated only the active profile's config.yaml. Siblings kept their old _config_version until their (correctly restarted, post-#91378) gateway hit a config shape the new code couldn't read — the last unabsorbed substance from the Phase-2 restart-swarm audit (#20438 earliest, 2026 field repro on #79048: sibling at v33 vs v37). _migrate_sibling_profile_configs(): per sibling home, scope config reads/writes via the context-local HERMES_HOME override (ContextVar — never os.environ), check version, run the NON-INTERACTIVE safe migration; prompt-requiring settings stay for the profile's own next interactive session (same contract as gateway-mode). Broken profiles are skipped without blocking the sweep; override always reset. Sabotage-verified; live E2E in a fresh process with real drifted config files: v12→v38 and v25→v38 on disk, provider preserved, the documented #81946 personality-reset migration correctly applied to siblings too, never-configured profile untouched, active home untouched, second run idempotent.