Personal Hermes
:8642 healthy
Hermes 0.19.0 responded successfully. No state or executable changed.
R1 found a stale scheduled-task path left by the repository rename, repaired it through the product's supported bridge manager, and established verified recovery evidence before any runtime split.
The task still launched C:\Users\Gaem4090\hermes-game-assist\..., which no longer exists. Hermes itself remained healthy on both profiles.
Hermes 0.19.0 responded successfully. No state or executable changed.
Hermes 0.19.0 responded successfully with the existing game-assist profile.
The supported task manager now launches from the durable nagato-game-assist checkout.
The new read-only preflight can be rerun from the separation worktree without printing credentials or memory content.
HTTP 200 from :8642/health.
HTTP 200 from :8643/health.
HTTP 200, Hermes configured, observability healthy.
HTTP 200 with dependency checks green.
Launcher and working directory resolve to the durable checkout.
Checksums match and every copied SQLite database passes integrity check.
R1 did not touch the large personal conversation store. A fresh online backup of that store is mandatory immediately before R6.
%LOCALAPPDATA%\hermes\backups\runtime-separation-r1-20260725-001709A570E18E67F9B1282966E2D17C53228310F293895B3438F427363A5CE36625BFRESTORE.md plus full CHECKSUMS.sha256spikes/runtime-separation/evidence/r1-baseline.md on issue #137's worktreeThe execution cards define R5 as memory-provider selection and active-use proof, and R6 as live runtime cutover. Earlier prose saying R5 was the cutover was a typo and is corrected. R1-R5 are preparation or isolated work; R6 alone requires the maintenance-window go-ahead.