refactor: derive worst-tone from GROUP_TONE in WorkspaceLifecycleToolCall

The header summary pill computed its tone with hardcoded "danger"/"warn"/"muted" literals that duplicated the existing GROUP_TONE mapping (already used for the dot chips just below). Pick the most severe non-empty OutcomeGroup and map it through GROUP_TONE so the group->tone relationship is single-sourced. Behavior-preserving: GROUP_TONE.failed/blocked/settled equal the prior literals.

Author: mux-bot[bot]

src/browser/features/Tools/WorkspaceLifecycleToolCall.tsx

@@ -239,7 +239,11 @@ const HeaderBadge: React.FC<{ rows: TaskWorkspaceLifecycleTargetResult[]; execut
   }
 
   const counts = summarizeOutcomeGroups(props.rows);
-  const worst: Tone = counts.failed > 0 ? "danger" : counts.blocked > 0 ? "warn" : "muted";
+  // Pick the most severe non-empty group and map it to its tone via GROUP_TONE so the
+  // group→tone mapping stays single-sourced (the dot chips below read from it too).
+  const worstGroup: OutcomeGroup =
+    counts.failed > 0 ? "failed" : counts.blocked > 0 ? "blocked" : "settled";
+  const worst: Tone = GROUP_TONE[worstGroup];
   const chips: Array<{ group: OutcomeGroup; n: number; label: string }> = [
     { group: "settled", n: counts.settled, label: "done" },
     { group: "blocked", n: counts.blocked, label: "blocked" },