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. - **If the repo has convention-guard scripts (`source/diagnostic/*.py` that exit non-zero on a violation), run them and confirm green before committing.** These are the project's own drift/lint guards (e.g. a canonical-spec or superseded-citation check); a red guard means this session introduced a NEW violation to fix first. Run at the checkpoint, not as a blocking commit hook — in a shared repo a repo-wide guard can go red for another session's change, so read the `[FAIL]` line and only act on your own. - 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 syst