Pilot Handoff

nav-pilot (since v6.16.0) dispatches a Navigator task doc to Pilot  as a labeled GitHub issue for autonomous execution. One-way handoff: Navigator authors the spec, Pilot executes it.

"Dispatch TASK-42 to Pilot"
→ resolves the task doc (explicit TASK-XX or the active task)
→ shows a pre-flight confirmation (--dry-run prints the gh command without running)
→ gh issue create --label pilot --title <H1> --body-file <doc>
→ records the issue URL into the doc's ## Refs and flips status to 🚀 Dispatched

Triggers: “dispatch TASK-XX to Pilot”, “hand off to Pilot”, “queue for Pilot”.

When Pilot executes a task autonomously, it sets the PILOT_EXECUTOR environment variable. As of v7.0.0 this is a single policy point in the hook runtime: all of Navigator’s interactive/blocking gates (workflow gating, completion gate, and the rest) are unconditionally disabled under it, so an unattended run can never stall waiting for human input.

Full page (config, the pilot block in .nav-config.json, examples) lands in Phase 2.