loose-endslisted

# Loose Ends Pre-merge sweep: produce a categorized list of work that's been deferred, flagged, or left incomplete during the current session, so the user can decide what to file as followups and what to clean up before merging. **Announce at start:** "Sweeping for loose ends." ## What counts as a loose end In ranked order of how often these actually surface: 1. **In-diff TODOs/FIXMEs** added or touched this session, especially bare `TODO` markers without an issue reference. 2. **Deferred conversational items** --- places earlier in this session where the assistant said "leave for later", "filed a follow-up", "punted", "out of scope for this PR", or similar. 3. **Dirty / unintentional worktree state** --- untracked scratch files, debug logs, modified files not part of the intended change. 4. **Sibling-repo work** touched but not committed/pushed there. 5. **Doc/spec drift** --- FDR/RFC/CLAUDE.md examples that the changes invalidated. 6. **Adjacent-improvement candidates** --- issues noticed mid-work that never became GitHub issues. ## Steps ### 1. Scan worktree and diff - `grit status` and `grit diff --stat-only` against the worktree (never the root git directory --- per CLAUDE.md). - `grit log <base>..HEAD --oneline` to enumerate this session's commits. Base is whatever this branch forked from (spinclass branches off the default branch). ### 2. Grep added/modified files for markers `rg search` for `TODO|FIXME|XXX|HACK` scoped to