v0.6.0 — Runtime decoupling, dispatch lifecycle & new skills

Added

• /spike — structured feasibility investigations: planner angles → executor fan-out → committed decision file at docs/spikes/<id>.md
• /research — imports external knowledge as a filtered feasibility list anchored to your project's actual constraints
• pmctl dispatch run --lifecycle detached + pmctl dispatch wait — dispatch returns immediately; poll for completion separately
• pmctl gate run persistent overrides — accepted-risk statements persist across gate cycles in .gate-overrides.md
• pmctl gate verify — verify a gate result independently from outside the gate run
• docs/sandbox-limitations.md — codex sandbox friction patterns and their workarounds

Changed

• Executor routing is now data-driven from adapter manifests — runner_kind in adapter.yaml drives router, guard, and install wiring
• pmctl gate run dispatches an independent subprocess instead of running in the main thread
• Write-guards consolidated from per-executor scripts into one manifest-driven hook

Removed

• claude-executor and codex-executor agent files retired — pmctl dispatch run is the sole dispatch path
• codex danger-full-access mode removed — workspace-write sandbox is the floor

Full details: CHANGELOG.md § 0.6.0