session-startlisted

# Session Start ## Operator Notification Notify the operator per the channel policy in CLAUDE.md (§ Operator Notification). ## `--task` flag (non-interactive autonomous start) If invoked as `session-start --task '<text>'`: use `<text>` as the task and bypass interactive prompts/questions only. Operator notifications in step 8 still follow the channel policy above. Skip the NEXT-TASK.md presentation (step 6), the "What should I work on next?" / "What should I help with?" prompts (steps 9b/10), the Tags prompt (step 11), the step-12 first-step confirmation, and the "After confirming the plan with the operator" plan-confirmation prose in the task-source paths. Do not ask for plan confirmation. Steps 1–4 run unchanged; create the session via `claude-code-hermit:session-mgr` and proceed autonomously. When starting a new session: All state lives under `.claude-code-hermit/` in the project root. 1. Read `.claude-code-hermit/config.json` for agent identity settings (`agent_name`, `language`) 2. If the SessionStart hook output above includes "---Upgrade Available---", mention it to the operator. Do NOT block session start. 3. **Read `state/runtime.json`** for lifecycle state **(fresh read — re-read the file(s) now; do not reuse a value cached in context from before compaction)**. This is the single source of truth — never parse SHELL.md `Status:` for decisions. - **Advisory lock check:** Try to acquire `state/.lifecycle.lock` non-blocking. If held by another process (hermit-s