brief

# Session Brief Provide a concise executive summary of recent session activity. Designed for morning check-ins, phone/channel consumption, and quick status updates. ## Always-On Delivery Rule If `config.always_on` is `true`, deliver all operator-facing output per `CLAUDE-APPEND.md § Operator Notification`. The terminal is unmonitored in always-on mode. For the push-fallback branch, condense the brief to a single line (per § Operator Notification push format): include whichever of open proposal count and active heartbeat alerts are present and non-zero; omit zero or unavailable fields. Example: `Brief: 16 proposals open, 1 alert — open CC to view`. In interactive mode, output to terminal. This applies to all flags below. ## Dispatch Before composing any brief, determine the dispatch mode: 1. Read `session_state` from `.claude-code-hermit/state/runtime.json` (live state — always in main). 2. Resolve the active flag (`--morning`, `--evening`, "brief today"/"daily summary", or no flag). Live files (SHELL.md, `alert-state.json`, `proposals/`) are read fresh on this turn; a value held in context from before a compaction is stale. **Dispatch decision:** - `--morning` → dispatch (mode: `morning`) - `--evening` → dispatch (mode: `evening`) - "brief today" / "daily summary" / "what happened today" → dispatch (mode: `daily`) - No flag + `session_state` is `in_progress` → **no dispatch** — summarize the live SHELL.md in main (Plan step 1a) - No flag + `session_state` is `idle` → ...