distillation-planlisted

# Distillation Plan (Stage 2) ## Overview Turn the approved distillation spec into an implementation plan a zero-context engineer can execute. Document everything: the source (reference) → target file map, which files each task touches, the exact code, the keep-verbatim items to reproduce, the seam substitutions to make, and when to commit. Bite-sized tasks. Assume the implementer is a skilled developer who knows almost nothing about this project, the reference, or what's worth preserving. Everything they need to keep the gold and avoid leaking the reference's deps must be in the plan. <HARD-GATE> Do NOT dispatch implementers or write any port code until the plan is written and the user has approved it. This applies to EVERY port regardless of how small it looks. </HARD-GATE> **Save plans to:** `docs/code-distilling/<capability>/distillation-plan.md` ## Input The approved `distillation-spec.md`: the contract, the keep-verbatim list, the discard list, the seam→your-deps mapping, and the per-chunk modes. Every task in the plan traces back to a chunk in the spec. If the spec is missing or unapproved, go back to `distillation-spec` first. ## Scope Check If the spec covers multiple independent capabilities, it should have been split during the spec stage. If it wasn't, suggest splitting into separate plans — one per capability. Each plan should produce working code on its own. ## Source → Target File Map Before defining tasks, map the reference's files to your project's