handofflisted

# Handoff Use Git as the transport and exact refs as the boundary. Handoffs are Markdown-only and depend on no hidden session state. ## Package A committed package contains: ```text .hyperflow-handoff/<slug>/ task.md handoff.md ``` `task.md` is the complete single task artefact copied from `.hyperflow/tasks/<slug>.md`. `handoff.md` contains a small table: status (`planned`, `built`, `reviewed`), source branch, build branch, base ref, head ref, created/updated dates, result, checks, and commit list. Legacy v5 packages using `HANDOFF.md`, `STATUS`, or nested `artefact/` directories are archive-only. `list` and `status` may report their paths, but `pickup` and `review` require the user to manually create the current `task.md` plus `handoff.md` layout with exact refs. Never delete, rewrite, or claim to resume legacy data automatically. ## Commands ### `create <slug>` Require the planned task file and a resolvable committed base. Copy the task into the package, record the exact base ref and intended build branch, set `planned`, and commit the package as its own conventional task commit so another session can fetch it. Do not include unrelated changes. ### `list` / `status [slug]` Read only. Show status, branches, base/head refs, result, and whether the package is awaiting build or review. ### `pickup <slug>` Require `planned`, verify the base ref exists, and preserve the package's scope. Check out or create only the recorded build branch when safe, then invoke `di