handoff-worklisted

# Handoff Work A handoff transfers state across machines, sessions, or people without stranded work, leaked secrets, or missing context. An unfinished task on a remote branch is recoverable; work stranded on a local disk or in `git stash` is lost. ## State persistence and hygiene Perfectionism that waits for tests to pass before committing strands work when switching environments. Commit in-progress work with a descriptive WIP message and push to a remote tracking branch. `git stash` is host-local storage. It does not transfer across machines and creates false confidence that progress was saved. Audit untracked files before staging (`git status -u`). Staging everything by reflex risks committing `.env`, local credential tokens, sqlite stores, or heavy build artifacts. Add newly introduced environment variable names to `.env.example` without secret values. A commit without a successful `git push` leaves the successor stranded. Remote tracking confirmation is the completion proof of persistence. ## Environment and resumption Document any non-committed prerequisite the successor needs to run: updated packages, new configuration flags, or background daemons. Open [resumption brief template](references/resumption-brief-template.md) to format the handoff document or message. Use `write-high-signal-update` for status updates without state transfer. Use `drive-to-delivery` when the deliverable is completed and ready to land.