mission-bootstraplisted

Create a VantagePeers mission and its full IRP task chain (T0 plan, T1..Tn execute, T(n+1) verify, T(n+2) ship) with sequential `dependsOn` wiring, in one call instead of the 8–15 raw MCP calls Pi does by hand today. **Canonical source**: VantageRegistry (`get_skill_content name=mission-bootstrap`). The local `.claude/skills/mission-bootstrap/SKILL.md` in each workspace MUST be a byte-exact mirror of the VR canonical content. End of hand-copy — fetch from VR, do not edit locally. PRINCIPLE 1 — ONE MISSION, FULL CHAIN: a mission is useless without its task chain. This skill refuses to create a mission with fewer than 3 tasks. If the caller only has a single deliverable in mind, they want a task (call `dispatch-task-create`), not a mission. PRINCIPLE 2 — DELEGATE TASK CREATION: every individual task is created via the `dispatch-task-create` skill, never via a direct `create_task` call. That skill auto-injects the `VERIFICATION:` + `TESTS:` blocks the `enforce-task-quality` hook requires, and the signature block the `enforce-signature` hook requires. This skill is a chain orchestrator, not a task author. PRINCIPLE 3 — DEPENDENCY CHAIN IS LAW: tasks must be linked T0 ← T1 ← T2 ← ... ← T(last) via `add_task_dependency`. No fan-out, no skipped links, no orphan tasks. Verify and ship tasks always depend on the last execute task. PRINCIPLE 4 — `description` AND `brief` ARE TWO DISTINCT PARAMS, BOTH REQUIRED. `mcp__vantage-peers__create_mission` accepts two textual params with di