fix(missions): a microvm mission needs no team, and two checks required one

Found by running one: the mission was created with runtime_kind='microvm' and
then refused to launch with a bare 400, because draft→running requires a
materializable team. Past that, `launch_phase` returns early when a phase has no
matching teams — so even with the launch allowed, the phase would have sat
`pending` forever while the log said only "no matching teams", and the executor
would never have been reached.

Neither check applies to this path: microvm_executor runs the agent CLI directly
in the VM, so there is no claw graph to materialise. Satisfying the checks by
attaching a team template would have provisioned claws that never run.

The repo checkout still happens — the VM needs the repository.

461 tests pass, clippy clean.

crates/cm-api/src/routes/missions.rs

@@ -854,7 +854,16 @@ pub async fn set_status(
                     .any(|v| v.as_array().map(|a| !a.is_empty()).unwrap_or(false))
             })
             .unwrap_or(false);
-        if prior.team_id.is_none() && prior.team_template_id.is_none() && !has_phase_teams {
+        // A microVM mission materialises no team — `microvm_executor` runs the
+        // agent CLI directly in the VM — so requiring one would reject the launch
+        // of a perfectly well-formed mission, and satisfying it would provision
+        // claws that never run.
+        let needs_team = prior.runtime_kind != "microvm";
+        if needs_team
+            && prior.team_id.is_none()
+            && prior.team_template_id.is_none()
+            && !has_phase_teams
+        {
             eprintln!(
                 "mission {id}: launch rejected — no team_id, no team_template_id, no config.phase_teams"
             );