hatch

# Initialize Autonomous Agent Set up the autonomous agent for this project. This creates the per-project state directory, configures the project for session-based work, and optionally activates hermits. ## Plan ### 1. Check if already initialized Check whether `.claude-code-hermit/config.json` exists in the current project. That file (written at Step 5) is the authoritative "already initialized" signal — not the bare presence of the `.claude-code-hermit/` directory. A lone `state/hatch-resume.json` marker (written by a domain hatch before it delegates here), an empty `state/` tree, or a half-written tree left by an aborted prior run all count as **not** initialized. - If `.claude-code-hermit/config.json` exists: inform the operator that the agent is already initialized. Ask if they want to reinitialize (which resets templates but preserves sessions, proposals, config, and OPERATOR.md). Record the choice as `is_reinit` (true if operator opted to reinitialize). - Otherwise: `is_reinit = false`, proceed with initialization. ### 1.5. Pre-flight (silent — no operator interaction) Before the setup-mode gate or any file writes, gather context silently. Run all commands in parallel where possible: 1. **Auto-detect language and timezone**: - Language: `echo $LANG | cut -d_ -f1` (fallback: `en`) - Timezone: `cat /etc/timezone 2>/dev/null || timedatectl show -p Timezone --value 2>/dev/null || date +%Z` (fallback: `UTC`) 2. **Silent hermit detection + core scope detection*...