fix(deploy-progress): decouple deploys from the live progress stream (#1246)

* fix(deploy-progress): decouple deploys from the live progress stream

The deploy progress modal streamed compose output over a WebSocket, but
the deploy itself was coupled to that socket in two ways that could break
or silently abort a deploy:

- The deploy request was gated on the progress socket connecting, so any
  upgrade failure (a reverse proxy blocking WebSocket upgrades, or the
  admin-only stream rejecting a scoped deployer) left the modal stuck on
  "Connecting..." and the deploy never fired.
- The backend terminated the running compose process when that socket
  closed, so minimizing the modal, navigating away, or a network blip
  aborted an in-flight deploy.

Make the progress socket output-only: the deploy is owned by its request
and runs to completion (or the existing command timeout) regardless of
the stream. The modal now degrades to a "Live progress unavailable" state
and still reports success or failure from the request result. Connect
failures, drops, and a connect timeout all release the deploy instead of
blocking it.

Also route progress output per deploy: the frontend sends a correlation
id on both the connectTerminal message and the deploy request header, and
the backend keys progress sockets by that id so concurrent deploys from
different tabs or users no longer cross-stream each other's output.

Cap the in-memory parsed log rows so a very long deploy cannot grow the
modal's state unbounded.

* fix(deploy-progress): generate the deploy session id with a CSPRNG

The per-deploy correlation id keys which WebSocket receives a deploy's
live output, so a guessable id lets one authenticated client register a
victim's id and read its compose output. It was built from Math.random()
plus a timestamp, which is not cryptographically secure.

Generate it with crypto.getRandomValues (128 bits, hex). That is the one
Crypto member available in insecure contexts, so it still works over LAN
HTTP where crypto.randomUUID is unavailable.

* fix(deploy-progress): stop headerless ops bleeding into a keyed progress modal

Address review findings on the progress-stream routing:

- Only an id-less connectTerminal registration may become the id-less
  fallback socket. Previously every connectTerminal (including keyed deploy
  modals) set the fallback, so a headerless operation (bulk update, rollback,
  or a legacy client) resolved via getTerminalWs() into another user's keyed
  deploy modal. Keyed sockets are now excluded from the fallback, and a socket
  that adopts a session id is removed from it.
- The connect-timeout fallback now also flags the modal as "Live progress
  unavailable" instead of leaving it on "Connecting..." while the deploy runs.
- Log only a short prefix of the deploy session id in developer diagnostics,
  not the full capability value.

frontend/src/components/Terminal.tsx

@@ -7,11 +7,17 @@ import { buildXtermTheme } from '@/lib/terminalTheme';
 
 interface TerminalComponentProps {
   stackName?: string;
+  /** Correlation id sent on the generic `connectTerminal` handshake so the
+   *  backend streams the matching deploy's output to this socket. */
+  deploySessionId?: string;
   onReady?: () => void;
+  /** Fired when the socket fails to connect or drops while still mounted, so the
+   *  caller can stop waiting on a best-effort progress stream. */
+  onError?: () => void;
   onMessage?: (text: string) => void;
 }
 
-export default function TerminalComponent({ stackName, onReady, onMessage }: TerminalComponentProps) {
+export default function TerminalComponent({ stackName, deploySessionId, onReady, onError, onMessage }: TerminalComponentProps) {
   const terminalRef = useRef<HTMLDivElement>(null);
   const terminalInstance = useRef<Terminal | null>(null);
   const fitAddonRef = useRef<FitAddon | null>(null);
@@ -124,8 +130,9 @@ export default function TerminalComponent({ stackName, onReady, onMessage }: Ter
         ws.onopen = () => {
           if (mounted) {
             if (!cleanStackName) {
-              // Generic terminal mode - send connect action
-              ws.send(JSON.stringify({ action: 'connectTerminal' }));
+              // Generic terminal mode - send connect action with the deploy
+              // correlation id so the backend streams this deploy's output here.
+              ws.send(JSON.stringify({ action: 'connectTerminal', sessionId: deploySessionId }));
               onReady?.();
             }
             // For stack logs mode, the server starts streaming automatically on connection
@@ -142,10 +149,21 @@ export default function TerminalComponent({ stackName, onReady, onMessage }: Ter
 
         ws.onerror = (err) => {
           console.error('WebSocket error:', err);
+          if (mounted) onError?.();
+        };
+
+        ws.onclose = () => {
+          // Only surface unexpected closes. Intentional teardown sets mounted
+          // false before closing, so this skips minimize/navigation/unmount.
+          if (mounted) onError?.();
         };
 
       } catch (err) {
         console.error('Error initializing terminal:', err);
+        // A synchronous setup failure (e.g. WebSocket construction blocked by
+        // CSP) gives no onerror/onclose, so release the deploy gate now instead
+        // of waiting out the connect timeout.
+        if (mounted) onError?.();
       }
     };
 
@@ -195,7 +213,7 @@ export default function TerminalComponent({ stackName, onReady, onMessage }: Ter
       searchAddonRef.current = null;
       serializeAddonRef.current = null;
     };
-  }, [stackName, onReady, onMessage]);
+  }, [stackName, deploySessionId, onReady, onError, onMessage]);
 
   const handleDownload = () => {
     if (!serializeAddonRef.current) return;