session-start

# 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. When adopting `<text>` as this session's task, write it **verbatim** as the `## Task` first line — no elaboration, reordering, summarization, or truncation — so the collision guard's exact same-task comparison stays valid on a routine's re-entrant call. 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 resume prompt (step 9's "continue the current task or start a new one" ask — the collision guard already made the resume/defer decision non-interactively), 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–3 run unchanged; the collision guard runs next. On a live-state collision (the `On collision — live` branch below) it aborts before step 4 — no session is created, renumbered, or otherwise mutated. On a recovery-state collision (the `On collision — recovery` branch below) it archives the crashed session and proceeds to step 4 as a new session. **Collision guard (runs imme...