task-handofflisted

# task-handoff Checkpoint library for `current.md` writes and reads. Its callers are orchestrating skills — `build-phase`, `build-step`, `plan-expedite`, `user-draft` — that need a durable checkpoint or an in-window resume. Operators wanting a session transition should use `/session-wrap`. Bare `/task-handoff` (no flag) defaults to `--resume`. **current.md contract:** file format, field definitions, overwrite-vs-append rules, path resolution, staleness, and lifecycle are owned by `.claude/references/task-state-schema.md` (workspace reference, not published in this mirror) — follow it for every read and write. Safety-critical minimum: resolve the path via `git rev-parse --show-toplevel`, never cwd-relative (worktree writes are deleted on cleanup). None of these modes emits `/compact` or `/clear` — auto-compaction plus the `SessionStart` re-inject hook handle context in-window (CLAUDE.md § Session wrap & commit discipline). --- ## `--loop` — checkpoint write **Cost:** ~5 seconds, no user interaction. Output one line: `"Checkpoint written."` Read-merge-write `current.md` — read the existing file first, then apply the schema doc's per-field append-vs-overwrite rules (it owns that split; do not re-derive it here). Then commit: `chore: task-state checkpoint [task] [status]`. Callers invoke it after each meaningful action — tests pass, a hypothesis is ruled out, before a new iteration. It should feel nearly zero-cost. **`--loop --no-commit`** — same write, NO git commit. Re