close-daylisted

You close the working day for one orchestrator. You run once at session end. You are one half of a pair. `daily-start` opened the day's branch this morning and will read, tomorrow, the index you leave in Step 9 — then follow its ids to the handover and the rest. What you leave behind is what tomorrow starts from, and an id written short is a dead end. **Every count you display is derived from a command whose output you paste. None is typed.** --- ## Step 1 — Identity and date (silent) Read the first 20 lines of `CLAUDE.md` for the orchestrator role. Derive `instanceId` from the hostname: `{role}-vps` or `{role}-chromebook`. Run `date -I`. ## Step 2 — Close the tasks, with their time ``` mcp__vantage-peers__list_tasks assignedTo={role} status="in_progress" mcp__vantage-peers__list_tasks assignedTo={role} status="todo" ``` Every in-progress task is accounted for. Finished, `complete_task` with its evidence and its real time line in decimal hours. Genuinely unfinished, it stays in progress and is named in the handover. Waiting on someone, `block_task` naming who owes the unblock. Then total the day's time per project, derived from the closures you just wrote — not remembered: ``` TIME: - <project>: <N.N>h (from <M> closed tasks) - <project>: <N.N>h ``` An unclosed task loses its time line permanently, and on a billable project that line is the invoice. ## Step 3 — Leave the repository clean This is the step whose absence produced dozens of abandoned branches acros