wassuplisted

# Start-of-day briefing Read-only. **Never edit the ledger.** `/seeya` and `/hey-sync` do the writing. ```bash ROOT="${CLAUDE_PLUGIN_ROOT:-$PLUGIN_ROOT}" # Codex names it PLUGIN_ROOT BOARD="$ROOT/scripts/board.py" HEY="$ROOT/scripts/hey.py" ``` ## 1. One call for the card ```bash LC_TIME=C date "+%Y-%m-%d (%a)" python3 "$BOARD" brief ``` `brief` gathers yesterday's log, loose worktrees, notes, progress, the day's output and blockers in a single pass. **Do not fire the individual commands instead** — that costs ten round trips and floods the context for the same information. **Then paste what it printed, verbatim, in a fenced code block, as the first thing in your reply.** The user does not see tool output; if you summarise the card instead of showing it, they never see the card at all — which is the one thing they asked for. Reproduce it exactly: no re-headed markdown, no rebuilt table, no dropped section. Your judgement goes underneath it, in step 2. Scope: `current` is the project you are standing in, `all` is every registered one, and the default lives in `~/.hey/config.json`. `hey-ledger` has the rest of the conventions, but you do not need them to run this. With scope `all`, `brief` prints one card per project — paste each one. Only reach for these when the card raises a specific question: ```bash python3 "$HEY" context --date <yesterday> # which files were touched, in detail python3 "$HEY" carryover --days 3 # aged blockers, and items seen unfinis