Missions and outcome verification

Use a mission for an outcome that needs dependency-aware steps, checkpoints, budgets, retries, or a durable wait. Mission completion is not inferred from a model summary: supported provider outcomes use exact read-only actions to inspect current state, and successful evidence is linked to the mission. Consequential compensation actions require an unexpired owner approval for the exact arguments, persist a durable receipt, and use a fresh read-back before they are marked successful. Ambiguous outcomes are reconciled rather than blindly replayed.