Open (create or attach) a mission

Open (create or attach) a mission: the investigation-level grouping over nodes, jobs, commands, and artifacts, with an org-unique human-readable name. Use one per question you are answering ("serve llama-70b under $X"), and open it FIRST - before the first create_node or submit_job - then pass mission: "<name>" on create_node / run_command / submit_job / submit_jobs / export_file: their work and cost roll up on the mission's page and get_mission, telemetry arrives labeled by mission (query_metrics / query_logs / search_traces), starter charts draw automatically, and save_chart adds the views worth keeping. The response's url is the human's window on the work - hand it over early, not with the final report. The page is org-private (sign-in, workspace visibility): the url discloses nothing outside the org. Create-or-attach by name: reconnecting (or a fleet of parallel agents) reuses the same name and lands in the same mission. Names are permanent org-wide handles - pick a meaningful one. Missions are optional and never required; they never cap or gate anything (workspaces are policy; missions are reporting). Declare the verdict with finish_mission when the question is answered. If the org cannot start paid work right now (no credit, an unpaid invoice, a suspended org), the response carries a warning naming the blocker and its cure - surface it to the human WITH the url, so they fix billing before watching an empty page.