fix(terminal): pass cols/rows upfront on start_claude to avoid DA1 echo

When spawning claude through the terminal-server, the pty was born at
the default 80x24 from claude-bridge.js and only got resized after the
first frame arrived. During that startup window claude sends a DA1
query ("\x1b[c" — device attributes) to detect terminal capabilities,
and the xterm.js response ("\x1b[?1;2c") was landing back in the
prompt as literal input before the process was ready for it.

Visible symptom: the Oracle terminal (and every other agent terminal)
started with "0?1;2c0?1;2c" sitting in the input line on first frame.

Fix: pass cols/rows in the start_claude options payload so the pty is
created at the right size on first spawn. The claude-bridge already
destructures `cols = 80, rows = 24` with defaults, so this lines up
cleanly — no bridge changes needed.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: DavidsonGomes

dashboard/frontend/src/components/AgentTerminal.tsx

@@ -154,12 +154,23 @@ export default function AgentTerminal({ agent, workingDir, accentColor = '#00FFA
               }
             } else {
               // Start Claude with --agent <agent>
+              // Pass cols/rows up-front so the pty is born at the right
+              // size — otherwise claude's DA1 (\x1b[c) / cursor-position
+              // queries during startup can echo back into the prompt as
+              // literal text ("0?1;2c0?1;2c") before the first resize
+              // message arrives.
               setStatus('starting')
+              const fit = fitRef.current
+              if (fit) {
+                try { fit.fit() } catch {}
+              }
               ws.send(JSON.stringify({
                 type: 'start_claude',
                 options: {
                   dangerouslySkipPermissions: true,
                   agent,
+                  cols: term!.cols,
+                  rows: term!.rows,
                 },
               }))
             }