Windows parity: Terminal cursor, glyph appearance and real-backend resize need qualification #736

Current reconciliation - 2026-11-09

Use the 2026-10-13 narrowed scope below: terminal TextPattern and OSC 7 retention are not macOS parity requirements; wheel/selection work belongs to #748. The original implementation description is historical, not a claim that current main still uses only the old glyph renderer. PR #921 configures macOS-derived terminal fonts; PR #959 refines configured cmd detail and DPI-correct tab/header geometry. PR #963, merged at fd8d1516430877e4bce3a6466695d29402ed5120, qualifies real input into the automatically restored selected pane after close/reopen with focusRepaired=false. These changes are included in Windows beta31.

Still open / Partial: matching visible cursor/caret geometry and glyph appearance, complete real-backend PTY resize qualification, and paired visual/device evidence. The bounded restored-pane input and 12-stage stress evidence are not error-free resize or glyph proof; retained PTY warnings and historical failures are not erased.

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

Is your feature request related to a problem?
Parity row Terminal VT state and rendering (Loop terminal workspace) in investigation/ui-parity-matrix.md is Partial.

macOS: Incremental VT parsing, complete Unicode text, styles, cursor, resize and scrollback with matching visible output.

Windows today: Ghostty VT parsing, Unicode glyphs and resize from live pane bounds; beta25 Dev Box terminal readability passed.

Gap: Wheel scrollback and selection scrolling, a visible cursor, native UIA TextPattern/glyph parity and OSC 7 working-directory retention remain; live PTY resize negotiation against a real backend is not demonstrated.

Describe the solution you'd like
Implement wheel scrollback, cursor rendering, TextPattern and OSC 7, then a live resize check with a real backend.

Describe alternatives you've considered
N/A

Additional context
This is an implementation gap: work remains in the product before the row can be validated. See also Clipboard/selection. Parity status and the beta25 Dev Box review are recorded in #719.