brieflisted

# 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 (≤200 chars, no markdown): include whichever of yesterday's/today's cost, open proposal count, and active heartbeat alerts are present and non-zero; omit zero or unavailable fields. Example: `Brief: 16 proposals open, yesterday $0.42, 1 alert — open CC to view`. In interactive mode, output to terminal. This applies to all flags below. ## Flags ### --morning (routine mode) **Delivery:** After composing the brief, deliver it to the operator (see Always-On Delivery Rule above). Emphasize forward-looking content: - Read `.claude-code-hermit/cost-summary.md` for cost context. Include: "Yesterday: $X.XX (12.3K tokens) across N sessions" — read the Date, Cost, and Tokens columns from the trend table for yesterday's row. - Pending proposals needing review - OPERATOR.md priorities - If `config.always_on` is `true`: what happened overnight (activity since evening routine) - If `config.always_on` is `false`: frame as "here's where things stand" rather than "what happened overnight" - What's queued (NEXT-TASK.md, open proposals) - If auto-memory seems sparse (new inst