Windows parity: Loop workspace chrome: loop bar, tab bar, split controls and pane headers #772

Current reconciliation - 2026-11-09

Later delivered chrome slices supersede the old source-only description: PR #910 aligns focused agent identity/control order; PR #959 supplies configured cmd shell detail, measured pane-header metrics, DPI-correct tabs and selected-tab preservation under constrained width. Its last-opened-panel priority is an explicitly approved Windows policy, not a claimed macOS responsive rule.

PR #963, merged at fd8d1516430877e4bce3a6466695d29402ed5120, qualifies actual selected-pane restoration across close/reopen with no focus repair. #959 and #963 are included in Windows beta31. Still open / Partial: all four whole chrome boxes, paired matching tab/pane/panel states, real Restart/final-unsplit close and W2-W6 outcomes where not separately qualified, rendered high-DPI/mixed-monitor and complete physical input. Bounded restoration is not all-terminal parity; local receipts retain their original source identities rather than becoming merge-head executions.

The original report, acceptance criteria and historical evidence below are preserved; the dated scope/progress above supersedes obsolete missing-feature claims.

Visual and functional parity work item, from the 2026-10-13 side-by-side review.

• Comparison: macOS reference Run A (app at 09eda11a, Dark, 2x) against the Windows testing-gaps run (installed 0.1.78-windows.beta26, 2560x1440 at 100%).
• Ground truth: macOS is the reference. Only platform chrome may differ: the title bar, window buttons, menu-bar location and native file pickers.
• Evidence limits:
  • File names below refer to the two local evidence bundles. The next macOS ground-truth run will attach captures.
  • Difference IDs (D1, E2, …) refer to the review report.
  • The reviewer opened the paired images it cites. Some surfaces could not be reviewed; they are listed under "Captures needed" in the ledger entry.
• Done when: every acceptance box is met and shown with paired screenshots in the PR. Before/after Windows captures go next to the macOS capture, and a reviewer from a different model vendor confirms them. A UIA readback or green unit test alone does not satisfy a visual criterion.

Evidence:

• macOS: 721-toolbar-workspace-loop-panel-shown-after-Loop-menu-Show-Loop-Panel;
• Windows: tg720-loop-workspace-1440, tg722b-workspace-two-tabs-split;
• differences G2–G6, B5;
• source: TerminalSurface.zig:2085, 2165, 7169-7173.

Acceptance criteria:

• The loop bar shows the type bar in the correct colour, a semibold title, a state pill, a divider, the age, "Restart session" and "Show in graph". It has no Stop button and no raw backend id.
• Tabs are full-width equal pills named by backend or shell ("Copilot CLI ⌘1", "Shell ⌘2"), with the shortcut right-aligned, and are followed by three icon buttons (split right, split down, new tab).
• Pane headers read "• agent focused … copilot cli" / "• shell … ⌘] to focus". No "zmx session" or "backend:" text.
• The loop-panel toggle is a toolbar icon.