This is a source-backed product snapshot, reviewed against code at a53395d. It separates implemented behavior from planned work and release evidence. Source/test links below are inspection evidence; separately executed checks and their limits are recorded in the documentation refresh verification.
| Label | Meaning |
|---|---|
| Implemented | A concrete implementation exists for the stated scope; follow the linked tests/checklist for coverage |
| Partial | A useful subset exists, with the missing behavior stated explicitly |
| Not implemented | The proposed product behavior is not present in the inspected implementation |
| Needs runtime evidence | Source or test coverage does not establish target-platform/application acceptance |
| Deferred | Intentionally outside the current delivery scope, not silently complete |
Implementation and validation are separate axes. An implemented feature may still need runtime evidence. Detailed VT support belongs to the Protocol Checklist; future priority belongs to the Roadmap, and full proposed scope to the Next-Stage Product Plan.
| Area | Current implementation | Evidence / boundary |
|---|---|---|
| Streaming parser | Implemented incremental UTF-8, CSI and bounded string-family framing, cancellation/discard behavior | Parser source, property tests, fragmentation tests; arbitrary-input runtime evidence remains a separate gate |
| Screen model | Implemented SGR/cursor/editing, margins, wide-cell normalization, scrollback and alternate-buffer isolation | Screen, screen tests; individual requirements are tracked in the checklist |
| Resize | Partial: non-reflow row copying; soft-wrap markers exist | NormalBuf, ADR-0018; width changes do not preserve logical-line geometry through rewrapping |
| Unicode content | Partial: ordinary and wide characters; no complete combining/ZWJ grapheme model | Cell model, cell writer; zero-width input is currently discarded in the normal write path |
| Terminal replies | Implemented DSR/CPR, device attributes, DECRQM, DECRQSS and XTGETTCAP slices | Dispatch, status strings, capability queries, PTY reply drain; not a missing reply channel |
| OSC metadata and links | Implemented titles, OSC 7 directory metadata, OSC 8 cell-linked hyperlinks, OSC 133 shell markers | Parser modules, hyperlink registry; directory inheritance and command-navigation UI are separate planned work |
| OSC colors | Implemented 10/11/12 default-color set/query and 110/111/112 reset | Color handler/tests; OSC 4/104 palette manipulation is not the same feature and remains open |
| Keyboard and paste | Implemented traditional application cursor/keypad, function/editing/modifier encodings, bracketed paste and confirmation | Input, terminal tests; Kitty keyboard is not implemented |
| Mouse | Partial: 1000/1002/1003 tracking with 1006 SGR encoding | Input, pointer routing, ADR-0038; legacy encoding, horizontal wheel and pixel reporting remain separate gaps |
| Focus and synchronized output | Implemented session-owned 1004 focus reporting and 2026 synchronized-output presentation/recovery | Focus reporting, terminal source/tests; preserve behavior through session and screen transitions |
| IME | Implemented commit, transient preedit overlay, candidate placement, composition-key suppression and cleanup | Terminal tests, layout, host tests; this does not provide combining-mark support in normal screen cells |
| Optional protocols | Kitty keyboard/graphics, OSC 52 and OSC 4/104 are not implemented | Do not infer support from safe APC/OSC framing; consult the checklist for other partial SGR and protocol families |
| Area | Current implementation | Evidence / boundary |
|---|---|---|
| Windows PTY | Implemented ConPTY spawn, I/O, resize and owned shutdown path | Windows PTY, endpoint tests; code-page compatibility needs the planned N03 matrix, not a presumed non-UTF-8 host decoder |
| Tabs | Implemented application-owned terminal tabs and tab-qualified output routing | Tab manager, coordinator; one terminal per tab, not a pane workspace |
| Selection and history | Implemented selection/copy, soft-wrap-aware copying, scrollback controls and scrollbar | Selection model, pointer routing; resize currently clears pointer/selection state, and history capacity is not a user setting |
| Startup settings | Implemented TOML font, shell program/arguments, terminal palette and application keybindings | Configuration, example; read once at startup, no user-configuration reload |
| Application commands | Implemented registry, availability/dispatch and configurable shortcuts | Command module; command palette UI is not implemented |
| Widget HMR | Implemented optional Windows debug-development root-library reload | HMR integration, README recipe; distinct from settings reload |
| Rendering and text | Implemented wgpu terminal rendering, glyph atlas, damage updates, DirectWrite font selection/fallback, cursor and decorations | Terminal rendering, text backend; Unicode, box joins, modern decoration gaps and current performance evidence remain bounded follow-up work |
| Window appearance | Implemented Acrylic/backdrop fallback and widget rounded borders, shadows and clipping | Backdrop, terminal decoration, widget runtime; not a shipped liquid-refraction pipeline or user-selectable theme system |
| Desktop widget foundations | Layout, focus/actions/shortcuts, theme infrastructure, scroll containers and view macro are present | Widget capability plan separates existing foundations from later widgets and product integration |
| New product workflows | Pane splitting, scrollback search, named profiles, command palette, configuration hot reload and command-navigation UI are not implemented | Planned as N04–N09, rather than described as existing features |
| Native Unix runtime | Deferred: the Unix PTY backend is a stub | Unix PTY; running a shell through WSL/SSH on Windows is a different scope |
The repository contains focused unit/contract tests and parser property/fuzz infrastructure. That is not equivalent to a recorded Windows daily-use release. See Validation for exact commands and the evidence-record format.
- Windows quality gates run format, all-target/all-feature clippy, workspace tests and documentation checks on pull requests to
main. - Parser fuzz workflow configures Ubuntu corpus replay and scheduled/manual bounded campaigns.
These workflow files exist. Their remote run results were not verified in this documentation refresh; do not list CI as missing or claim it is passing solely from configuration.
Still required for a release claim:
- recorded parser fuzz replay/campaign results on a supported host, not only harness/corpus configuration;
- representative Windows application sessions for replies, mouse/focus, IME, resize, shell lifecycle and sustained output;
chcpand Kitty transport probes before asserting compatibility or a Harbor-specific failure;- comparable performance captures for the current code, including multi-session and visual-effect workloads as they land;
- actionable diagnostics, packaging and dogfood records, with unsupported behavior explicitly listed.
Historical memory captures remain historical. They do not establish current latency, memory, release readiness, or completion of later optimization work.
When behavior changes, update the relevant row and protocol requirement with source/test evidence. Update the roadmap only when execution priority or milestone status changes. Keep run results in reproducible evidence records rather than turning implementation summaries into unqualified "verified" claims. Preserve historical ADR/spec/ticket context; supersede decisions explicitly instead of rewriting history to match future plans.