fix(console): give .content a horizontal gutter

[brettchien]

Brett flagged: no left/right padding on the console — content runs edge-to-edge.

Root cause

.content (console/src/styles.css) has been display:flex; flex-direction:column
with zero padding since the very first commit. Every top-level section
(.chat-wrap, .config-wrap, .deploy-wrap, ...) only carries a bottom
margin — nothing ever set a horizontal gutter. Pre-existing, not something
the ADR #83 drill-down slices introduced; just more visible now that the
layout changed.

Fix

.content { padding: 16px 18px; } — horizontal inset matches the topbar's
own padding: 12px 18px, so left/right edges line up visually with the
topbar content.

Verification

• tsc --noEmit — clean
• vitest run — 107/107 passing
• vite build — clean

🤖 Generated by Orca ('ecs-claude').

[brettchien]

Pushed a second commit addressing your three follow-ups:

1. MANAGING banner → right column, above Agent chat: #identity moved into a new .drilldown-side wrapper next to #chat (was a full-width strip below the row).
2. Agent chat too small: the chat-log's fixed 120–340px height bumps to 240–560px for this panel specifically (scoped so it doesn't affect the per-agent console chat, which reuses the same .chat-wrap/.chat-log classes).
3. Adjustable 2-column split: drag handle between the drill-down content and the chat column, 280–900px range, width persisted across reloads (src/splitPane.ts).

tsc/vitest (112/112)/vite build all clean; verified interactively with Playwright (identity renders above chat, drag grows the column live) — screenshots eyeballed for regressions.

[brettchien]

Third commit, addressing your four follow-ups on the per-agent view:

1. Remote + Compose not relevant per-agent: hidden alongside the Fleets screen whenever a fleet is selected (same condition #config/#fleet-detail already toggle on).
2. Files removed from agent console: .ac-files was a permanent stub — every real endpoint reports no fs capability today, so it only ever showed a "pending" placeholder. Deleted fileBrowser.ts, its wiring, the dead render.ts helpers + tests, and the CSS. Left Source.fsList/fsRead/fsCapability alone (backend contract, not UI).
3. Chat input fixed at 2 lines: was resize: vertical with only a min-height floor — now resize: none.
4. Debug drawer top hidden / Close unreachable: .debug-drawer was top: 0, but the topbar sits above it in z-index on purpose (so it stays visible) — that meant the drawer's own header rendered underneath the topbar, invisible and unclickable. Now anchors to a live-measured --topbar-h so it starts right at the topbar's bottom edge.

tsc/vitest (102/102 — 10 fewer from the deleted file-browser tests)/vite build all clean. Verified interactively with Playwright: Remote/Compose hide on drill-down, .ac-files is gone from the DOM, the textarea computes resize: none at 2 rows, and a real mouse click on the Debug drawer's Close now lands on the button and closes it.

[brettchien]

Fourth commit — the two items I could actually confirm and fix from this last round:

1. Same agent double-connected (management + roster): confirmed this is real. agentConsole.ts's guard only checked a roster entry's name against agents.toml's own management: true flag — but the persistent "Agent chat" connection dials whatever remote.toml points at, a separate config. A roster entry can reach the identical physical agent without ever being flagged management, and nothing stopped a second console (a second live ACP session) from opening against it — which is exactly what your screenshot showed (garbled/mismatched turns between the two panels talking to the same orca process). Fixed by comparing urls, not just names: a roster row now gets the same disabled "console above" treatment whenever its url matches the active management connection's url, whether or not agents.toml flagged it. Guarded in both the render (so the row doesn't look clickable) and the open() handler (belt-and-suspenders against a render/connect race).
2. Roster row didn't look clickable: button.row-open only went link-styled on :hover — at rest it was plain text. Now link-colored + underlined by default.

On the other three:

• [⚙] "not working": tested against current HEAD with a real synthetic mouse click — it opens the drawer correctly. My best guess is this was the same topbar/z-index bug fixed two commits ago (the drawer's own header rendering invisibly under the topbar) — nothing looked like it happened even though the drawer did slide in. Should be resolved by this branch; flag me again post-deploy if it's still stuck.
• Compose "blank area at the bottom": measured it — the box height (612px) exactly matches its content (head + grid + padding), no CSS stretch/overflow bug. The blank space is just the page ending inside a viewport taller than the content — ordinary scrolling-document behavior, not a sizing bug. If you want the whole app to fill the window edge-to-edge (a fixed-height app-shell instead of a naturally-scrolling page), that's a legitimate ask but a bigger structural change touching every section — let me know if that's actually what you want before I take it on.
• Start/Stop/Configure/Restart actions: checked the backend contract — today Source only exposes scaleDeployment(name, 0|1), i.e. Start/Stop. There's no Restart or Configure RPC yet. Before I build UI for buttons that don't do anything: is Restart okay as scale-off-then-on (not a true zero-downtime restart, just what's achievable with what exists), and should Configure open the existing Compose/deploy flow scoped to that agent (reuse, not a new inline editor)? Say the word and I'll scope + build it.
• "hard to understand how to use the compose panel": what specifically trips you up — the two-column layout (author on the left vs. deploy on the right), the field order, or something else? Happy to take a pass at clearer copy/labels once I know what's confusing.

tsc/vitest (103/103)/vite build all clean.

[brettchien]

Fifth commit: deploy panel now takes over the left column instead of appearing as a stray block below.

Two things were wrong:

1. `deploy.ts` set `#drilldown-row.hidden = true`, meaning to hide both columns while the form took over full-width. But `.drilldown-row { display: flex }` is unconditional — same bug as `.debug-drawer[hidden]` from two commits back (author rule beats the UA `[hidden]` rule at equal specificity), just not caught there yet. The row never actually hid, so the form landed as an extra block underneath the still-visible roster+chat — exactly your screenshot.
2. Even with that fixed, hiding the whole row was the wrong target — it'd drop Agent chat too, breaking "chat stays visible at every depth."

Moved `#deploy-wrap` inside `.drilldown-main`, a sibling of `#config`/`#fleet-detail` — it's just another depth now. Open hides whichever of those two is showing; Cancel calls back into `updateScreen()` to restore the right one. Added the same `[hidden]` override to `.deploy-identity` (the "new fleet" step-1 form had the identical bug) and to `.drilldown-row` itself as insurance.

`tsc`/vitest (103/103)/`vite build` clean. Verified both `+ New fleet` and `+ Add instance` land in the left column with identity + Agent chat still visible on the right, Cancel restores correctly either way.