keel-handoverlisted

# /keel-handover — write the session block Add a new **session block** to the TOP of `HANDOVER.md`'s "Session blocks" section (rules.md §1.4). Newest first; never edit past blocks. Steps: 1. Read the current `HANDOVER.md`. If it already has **3 blocks** (or exceeds ~150 lines), run `/keel-distill` first to rotate the oldest block out (critical facts → `LESSONS.md`, raw block → `docs/handover-archive.md`). 2. Write this session's block: `### <YYYY-MM-DD HH:MM> — @<git user.name> — <one-line status>` (time = when the block was first created; the `@<git user.name>` attributes the session's author so multi-user handovers stay legible — read it from `git config user.name`; single-user projects still get it, at zero cost). **One block per SESSION, not per day:** if THIS session already wrote a block (a mid-session handover, or /keel-compact re-running this), UPDATE that block in place — keep its original HH:MM. A NEW session always adds a NEW block, even on the same day — same-day sessions must stay distinguishable. The block contains: - **(a) Completed** — what was done, dated; link decisions to their ADR/docs; include one-liners for TASKS.md items finished this session (then delete them from TASKS.md). **Multi-user exception** (`.claude/project-owner` exists and you are NOT the owner): do not delete your finished items — MOVE each to a TASKS `## Review` section (create it if missing) as `- [x] <id> ... (@you) — evidence: <how the d