The dashboard used to be started by hand as `serve --host 0.0.0.0`, so it
was reachable from the LAN and didn't survive a reboot or a Hermes update.
Now, following Hermes's docs:
- launchd agent local.hermes-dashboard runs `hermes dashboard` on
127.0.0.1:9119 (KeepAlive, --skip-build since `hermes update` builds it).
- Tailscale Serve publishes it on https://cogitator-02.porgy-porgy.ts.net,
tailnet only. No module exists for Serve; the task reads
`serve status --json` and only sets it when it differs.
- Login: scrypt password hash and a real signing secret from the vault
(the old secret was the literal text "$(openssl rand -base64 32)"); the
plaintext password line is removed from .env since it overrides the hash.
- After Serve is set, the play checks /api/status demands the basic login;
if not, it turns Serve off and fails.
- Hermes's Python no longer needs a firewall exception, so that's gone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>