Mission Proposal & Approval

The agent proposes a mission to the Person Server: a Markdown description of what it intends to accomplish, plus a list of tools it will use. Because the PS acts on behalf of a human, approval requires user interaction — the PS returns 202 with an interaction URL so the user can review and approve the mission. Once approved, the PS returns the mission blob (with approver, agent, approved_at, description, approved_tools, and capabilities) and an AAuth-Mission header containing the approver URL and s256 (SHA-256 fingerprint of the blob bytes).