hatch3r-handoff-resume

# Handoff Resumption ## Quick Start ``` Task Progress: - [ ] Step 0: Detect ambiguity (P8 B1) - [ ] Step 1: Locate the handoff (direct id or pick from list) - [ ] Step 2: Validate (integrity, injection scan, schema) - [ ] Step 3: Drift check (git_ref, expiry, hatch3r_version) - [ ] Step 4: Surface content under user-tier markers - [ ] Step 5: Transition status to `resumed` ``` ## Step 0 — Detect Ambiguity (P8 B1) Before any work, scan the invocation for unresolved questions in scope, intent, acceptance criteria, target environment, or irreversibility. If any are found, ask the user via the platform-native question tool per `agents/shared/user-question-protocol.md`. Do not proceed under silent assumption. Default path, not an exception. Triggers for THIS skill: which handoff id (direct vs pick-from-list), branch checkout policy when drift detected, expiry handling (extend vs archive), auto-advance from `resumed` to `in-progress`, and trust posture for the user-tier body. ## Fan-out Discipline (P8 B2) Fan-out scales with task size; token cost never justifies serializing independent work (`rules/hatch3r-fan-out-discipline.md` P8 B2; `agents/shared/efficiency-patterns.md`). Emit `sub_agents_spawned: { count, rationale, task_structure }` in your output. ## Step 1: Locate `readHandoff` / `listHandoffs` (`src/content/handoffs/index.ts`) are CLI-internal helpers, not agent call targets — locate handoffs with your platform file tools: 1. If `<id>` was provided: `Read` `.hatch...