espalier-migratelisted

# Espalier Migration Runner ## When to Use - "Migrate to Espalier" / "Upgrade my Espalier install" - "Upgrade my harness to the latest version" - "Rename harness/ to espalier/" - "/espalier-migrate" ## When NOT to Use - Fresh project with no existing `harness/` or `espalier/` dir → use `/espalier-init` instead. - Already fully up to date — `/espalier-migrate` detects this itself and exits cleanly with no changes. ## Instructions You are running a migration of an existing install to the current Espalier version. Up to SIX migrations may apply, always in this order: 1. **v0.1.x → v0.2.x** — typed `harness/changes/{type}/{slug}/` layout, `/harness-fix` lane, squash-merge decision. Mechanical: `scripts/migrate-v0.1-to-v0.2.sh`. 2. **v0.3.x → v0.4.0** — `harness/` → `espalier/` directory + skill rename (`harness-run` → `espalier`, `harness-{coding,…}` → `espalier-*`). Mechanical: `scripts/migrate-v0.3-to-v0.4.sh`. 3. **v0.4.x → v0.5.0** — doc-drift detection: drift hooks, the `/espalier-prune` + `/espalier-doctor` skills, the post-merge dispatcher, `.doctor-cadence`. Mechanical: `scripts/migrate-v0.4-to-v0.5.sh`. 4. **v0.5.0–v0.5.2 → v0.5.3** — appends the `## Editing Discipline` section to the coder sub-agent (`espalier/agents/harness-coder.md`). Mechanical: `scripts/migrate-v0.5.2-to-v0.5.3.sh`. 5. **v0.5.x → v0.6.0** — Stage 1 grilling: installs the `espalier-grill` skill, refreshes the four changed pipeline templates (which also date-prefix chan