keel-handover

# /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 **5 blocks** (or exceeds ~200 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> — <one-line status>` (time = when the block was first created). **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). - **(b) Tried, didn't work** — approaches that failed + the reason, so they aren't retried. This is the highest-value section — don't skip it. - **(c) Latest updates** — the most recent concrete changes. - **(d) Next steps** — prioritized, for the next session. 3. **PLAN.md** (if the project uses it): flip the phase statuses that changed this session, refresh _Current focus_, regenerate the diagram block from the table (see `/keel-p...