hermes-scripts/ — the current Hermes scheduled/orchestration scripts. One historical file, v_restart.py, contains shell syntax despite its .py suffix; it is preserved verbatim for recovery reference and must be treated as a shell script, not compiled as Python.
browser/ — the dedicated ReynaFamilyBot Chrome launcher and LAN observer bridge source.
launch-agents/ — active Reyna/Hermes/MacMiniMCP/Kokoro/reMarkable LaunchAgent definitions with no credential values.
macmini-mcp/ — source, tests, package metadata, and service helper scripts for the current Node MCP and warm Kokoro setup. Dependencies, environment files, generated output, logs, and Git metadata are excluded.

Deliberately excluded

Browser profiles, cookies, Chrome session data, and passwords.
.env files, credentials, tokens, API keys, auth databases, SSH keys, and generated logs/media.
Third-party/inactive service definitions that contain or may contain credentials. In particular, legacy OpenClaw launch agents are not copied; if that legacy stack is retired, rotate its credential material rather than preserving it in Git.
Hermes configuration, session transcripts, and WhatsApp state.

Restore boundary

This folder is a debugging/reference snapshot, not an install script and not a declaration that these services should be restarted. The replacement target is the Reyna CLI single privacy host described in .hermes/plans/2026-08-03_113451-reyna-cli-single-privacy-host.md.

Current architecture captured

MacMiniMCP: Node HTTP/MCP service (historically LAN-bound/authenticated).
Kokoro: warm local TTS HTTP server, historically loopback-bound.
Browser: visible Mac-mini Chrome using the fixed Profile 1 / ReynaFamilyBot profile, with CDP loopback-only and a narrow trusted-LAN observer bridge.
reMarkable: native Reyna CLI LaunchAgents are included as the current service definitions.