handofflisted

# Session Handoff Wrap up an end-of-session: commit and push the session's changes, plus optionally write a focused handoff note for the next session. ## Default flow Always do these: 1. **Identify which projects/pipelines were modified** during the session (`git status` in each one that was touched). 2. **For each repo with uncommitted changes**, separately: - Review `git status` and `git diff` to inventory the changes. - Stage relevant files — prefer naming specific files over `git add .` to avoid sweeping in unrelated WIP. - Draft a commit message and confirm with the user. - Commit, then push (unless the user asks to hold off). 3. **Move completed `todo.md` items to `done.md`** if the session actually completed any. Add new tasks that emerged to `todo.md`. After step 3, **decide whether a handoff note is needed**. ## When to write a handoff note A note is worth writing **only** when the rest of the system doesn't capture what the next session should know. The rest of the system already gives you commits, `done.md`, `todo.md`, the per-iteration `/next` reports, `artifacts.yaml`, and `decisions.md` — most "where did I leave off" questions are answered by those. A note earns its keep when: - **Mid-stream work:** a script is half-written, or run but not yet propagated to docs. Commit + push captures the bytes; the note captures *what's incomplete and why*. - **Noticed but not acted on:** "Bacenjud hit-rate has a weird drop in 2022Q4 — n