@oh-my-pi/pi-tui 15.7.6 → 15.8.2

package/CHANGELOG.md

@@ -2,14 +2,51 @@
 
 ## [Unreleased]
 
-## [15.7.6] - 2026-06-01
+## [15.8.2] - 2026-06-03
+
+### Added
+
+- Added `PI_NO_SYNC_OUTPUT=1` to disable DEC 2026 synchronized-output wrappers for terminals whose implementation is buggy or visually worse, while keeping the renderer's autowrap guards active during paints ([#1765](https://github.com/can1357/oh-my-pi/issues/1765)).
 
 ### Fixed
 
-- Fixed native Windows + Windows Terminal freezing the editor on the wrap keystroke, on `/plan`/`/resume`/model-switch/status-line toggles, and on any other offscreen structural mutation until the next prompt submit. The `15.7.5` `#1635` fix routed every viewport-saturating pure-append and structural mutation through `deferredMutation` (a literal no-op) whenever `isNativeViewportAtBottom()` returned `undefined` — which it always does under `WT_SESSION` because the kernel32 probe can't see WT host scrollback. The deferral was only ever meant for the *confirmed-scrolled* case; an unknown viewport now falls back to a non-destructive `viewportRepaint` instead, so the live UI keeps updating without emitting `\x1b[3J` and without yanking a possibly-scrolled reader. Confirmed-scrolled frames (probe returns `false`) still defer.
+- Fixed terminal resizes that land in the same render frame as streamed output splicing a phantom blank row into native scrollback and offsetting every later row by one. A height shrink (or width change carrying an append) with content overflowing the viewport fell through to the differential emitter, whose scroll math is anchored to the pre-resize viewport top and hardware-cursor row — both invalidated by the terminal's own resize reflow. Geometry-changed frames now rebuild native history when the viewport is at (or possibly at) the bottom, and defer non-destructively for a reader confirmed scrolled into history.
+- Fixed Ghostty/kitty/Alacritty-style ED3-risk terminals freezing the prompt after a deferred shrink; focused keyboard input now uses the same explicit user-input viewport opt-in as autocomplete and can repaint immediately instead of waiting for a resize.
+- Deferred eager live scrollback rebuilds under WSL fronted by Windows Terminal (`WT_SESSION` present in a Linux environment) so foreground streaming no longer emits ED3 (`CSI 3 J`) and yanks a reader scrolled into Windows Terminal's host scrollback; deferred rewrites still reconcile at the next prompt-submit checkpoint ([#1610](https://github.com/can1357/oh-my-pi/issues/1610)).
+- Fixed tmux (and screen/zellij) pane history gaining a complete duplicate copy of the transcript every time a deferred offscreen edit was followed by another render. Multiplexer panes never receive a destructive scrollback clear, so the dirty-scrollback rebuild path only appended the full transcript on top of preserved pane history — repeatedly. Live frames inside multiplexers now keep repainting the viewport and leave history reconciliation to explicit checkpoints, which also removes the O(transcript) write amplification per frame.
+- Fixed tmux pane viewports corrupting and pane history duplicating when a resize coincides with rendering: a resize racing a streamed append reached the stale-anchor diff emitters (phantom rows in the pane), a forced render racing a resize replayed the whole transcript into preserved pane history, and the prompt-submit checkpoint did the same after any deferred offscreen edit. Geometry-changed frames inside multiplexers now repaint the viewport in place, and forced-render geometry replays plus checkpoint replays are disabled there — tmux reflows its own pane grid and its history cannot be cleared, only duplicated.
+- Fixed terminal resize events whose dimensions net out unchanged by render time (rapid SIGWINCH round trips during a window drag, coalesced into one 16ms frame) being invisible to the renderer. The terminal reflows its buffer on every resize event — rows move between the viewport and scrollback and can be evicted at the scrollback cap — so diffing against the pre-resize screen splices blank phantom rows into the viewport. The renderer now tracks the resize event itself, not just the dimension delta, and routes such frames through the geometry-change repaint/rebuild paths.
+- Fixed Termux terminal resizes (screen rotation or software-keyboard toggles) displacing or hiding output after the viewport height changed. Content-bearing resizes were routed to the differential emitter, whose scroll math is anchored to the pre-resize viewport, so appended rows landed too low; pure height changes were treated as no-ops, exposing blank rows that later appends could fill without growing native scrollback. Termux resizes now repaint or rebuild at the new geometry like every other non-multiplexer terminal.
+- Fixed the turn-end teardown frame freezing on ED3-risk terminals (Ghostty/kitty/Alacritty/iTerm2): disabling eager scrollback rebuild now takes effect only after the in-flight frame is classified, so the loader/status removal still paints instead of deferring and leaving a stale spinner until the next keystroke.
+- Fixed non-WT ConPTY terminals on Windows (Tabby, Hyper, VS Code, conhost) clearing scrollback and yanking the viewport to the top whenever streaming output or a prompt-submit rebuild arrived while the user was scrolled up. The kernel32 viewport probe describes the ConPTY pseudo-console buffer — which is pinned to the visible grid, invisible to host-UI scrollback — so it reported "at bottom" no matter where the user had scrolled, and the [#1635](https://github.com/can1357/oh-my-pi/issues/1635) fix only distrusted it under `WT_SESSION`, which Tabby and other ConPTY hosts never set. The probe is now removed entirely: every Windows host is treated as viewport-unobservable, live mutations defer destructive rebuilds (no `\x1b[3J`, no viewport movement), and native scrollback reconciles at the prompt-submit checkpoint where the Enter keystroke has already pinned the host viewport to the bottom ([#1746](https://github.com/can1357/oh-my-pi/issues/1746)).
+- Fixed emoji-presentation symbols (a default-text symbol followed by variation-selector-16 `U+FE0F`, e.g. `⚠️`, `ℹ️`, `❤️`, keycaps) measuring as 1 cell instead of 2 in the native width engine on macOS. The native scanner now keeps `UnicodeWidthStr` as the source of truth for multi-codepoint graphemes and applies only the local macOS Hangul Compatibility Jamo character-width delta, preserving VS16/keycap sequence widths without reintroducing jamo cursor drift.
+- Deferred eager live scrollback rebuilds on macOS Terminal.app and iTerm2 so assistant/tool streaming no longer emits ED3 (`CSI 3 J`) while their native viewport position is unobservable, preserving readers scrolled into terminal history ([#1300](https://github.com/can1357/oh-my-pi/issues/1300)).
+- Fixed width-shrink reflow leaving old-width rows in native history so later appends no longer undercount scrollback growth or duplicate wrapped content.
+- Fixed hiding overlays after terminal reflow so stale dialog rows are scrubbed from native scrollback on non-multiplexer terminals.
+
+### Removed
+
+- Removed `shouldTrustNativeViewportProbe` and `ProcessTerminal`'s kernel32 `GetConsoleScreenBufferInfo` viewport probe. No Windows environment can answer "is the user's viewport at the bottom" truthfully — under ConPTY (every modern host) the pseudo-console buffer is pinned to the visible grid so the probe always read "at bottom", and under legacy conhost the window tracks the output cursor rather than the buffer tail so it always read "scrolled up" — so the probe and its trust gate are gone; `ProcessTerminal` no longer implements the optional `Terminal.isNativeViewportAtBottom`.
+
+## [15.8.1] - 2026-06-02
 
 ### Fixed
 
+- Deferred eager live scrollback rebuilds on VTE terminals so GNOME-style Linux terminals do not flash or erase readable scrollback during streaming ([#1719](https://github.com/can1357/oh-my-pi/issues/1719)).
+
+## [15.8.0] - 2026-06-02
+
+### Fixed
+
+- Deferred eager live scrollback rebuilds on POSIX terminals where xterm ED3 (`CSI 3 J`, erase saved lines) can disturb scrolled-up readers during streaming, while keeping direct user-input and checkpoint rebuilds explicit ([#1682](https://github.com/can1357/oh-my-pi/issues/1682)).
+- Fixed TUI shutdown placing the parent shell prompt one row below short rendered content instead of directly on the next line ([#1620](https://github.com/can1357/oh-my-pi/issues/1620)).
+- Stopped painting inline color swatches for 4-digit hex runs in Markdown rendering. The `#RGBA` CSS form collides with hashline `#TAG` snapshot tags (4 hex digits, e.g. `#6C5E`), which were sprouting spurious RGB swatches in prose and codespans. Only `#RGB`, `#RRGGBB`, and `#RRGGBBAA` qualify now.
+
+## [15.7.6] - 2026-06-01
+
+### Fixed
+
+- Fixed native Windows + Windows Terminal freezing the editor on the wrap keystroke, on `/plan`/`/resume`/model-switch/status-line toggles, and on any other offscreen structural mutation until the next prompt submit. The `15.7.5` `#1635` fix routed every viewport-saturating pure-append and structural mutation through `deferredMutation` (a literal no-op) whenever `isNativeViewportAtBottom()` returned `undefined` — which it always does under `WT_SESSION` because the kernel32 probe can't see WT host scrollback. The deferral was only ever meant for the *confirmed-scrolled* case; an unknown viewport now falls back to a non-destructive `viewportRepaint` instead, so the live UI keeps updating without emitting `\x1b[3J` and without yanking a possibly-scrolled reader. Confirmed-scrolled frames (probe returns `false`) still defer.
 - Removed the hard-coded 20-result cap on `@`-prefixed fuzzy file completion in `CombinedAutocompleteProvider.#getFuzzyFileSuggestions`. The dropdown now honors the existing `maxResults: 100` ceiling already configured for `fuzzyFind`, so projects with many files sharing a common stem (e.g. `@controller`, `@test`) surface all relevant matches instead of being silently truncated. ([#1652](https://github.com/can1357/oh-my-pi/issues/1652))
 
 ## [15.7.5] - 2026-06-01
@@ -50,6 +87,7 @@
 - Fixed slash-command autocomplete repainting when a Windows Terminal session cannot report native scrollback position; live input renders can now bypass the unknown-viewport deferral without weakening background scrollback protection. ([#1550](https://github.com/can1357/oh-my-pi/issues/1550))
 
 ## [15.6.0] - 2026-05-30
+
 ### Added
 
 - Added autocomplete triggering for internal URL scheme tokens such as `local://` and `skill://` while typing in the editor
@@ -96,6 +134,7 @@
 - Fixed full TUI redraws clearing terminal scrollback with `CSI 3 J`, preserving manual scrollback inspection while active sessions continue updating. ([#1295](https://github.com/can1357/oh-my-pi/issues/1295))
 
 ## [15.2.3] - 2026-05-22
+
 ### Added
 
 - Added `SettingsList#setItems` to replace the entire settings list with a new items array while automatically clamping selection to a valid index
@@ -123,6 +162,7 @@
 - Restored the `Key` runtime helper on `@oh-my-pi/pi-tui` to mirror upstream `@mariozechner/pi-tui`'s surface. `Key.enter`, `Key.escape`, `Key.tab`, … return the canonical key-name strings; modifier methods (`Key.ctrl(k)`, `Key.shift(k)`, `Key.ctrlShift(k)`, etc.) build precisely-typed `KeyId` literals like `"ctrl+c"`. Pure runtime convenience for typed key-id construction — plugins built against the upstream package surface that import `Key` (e.g. `@plannotator/pi-extension`, `@juicesharp/rpiv-ask-user-question`) load again now that the specifier shim remaps them onto this package.
 
 ## [15.0.1] - 2026-05-14
+
 ### Breaking Changes
 
 - Increased the minimum required Bun version for the TUI package from >=1.3.7 to >=1.3.14
@@ -156,6 +196,10 @@
 - `SlashCommand.getArgumentCompletions()` may return a `Promise`; results are now awaited and non-array returns are ignored (ports pi-mono `a1e10789`)
 - Fuzzy `@` autocomplete now follows symlinked directories via `ScanOptions.follow_links` plumbed through the native walker (ports pi-mono `780d5367`)
 - Plain `@<query>` (no slash) fuzzy matches by basename only, so `@plan` no longer surfaces every file whose ancestor directories contain `plan` (ports pi-mono `968430f6`)
+- Changed slash-command autocomplete list rendering to combine command hint and description in a single displayed suggestion text
+- Changed render scheduling to throttle `requestRender` calls to roughly 60fps by batching updates
+- Changed terminal input handling to process complete cell-size responses without buffering partial input
+- Changed `KeyId` to accept super-modifier combinations and improve typed key-id validation
 
 ### Fixed
 
@@ -171,20 +215,11 @@
 - Allowed `SlashCommand.getArgumentCompletions` to return asynchronous results by accepting Promise-based completions
 - Added `argumentHint` support to slash command definitions and displayed it in command suggestion descriptions
 - Added support for xterm `modifyOtherKeys` printable key sequences by decoding `CSI 27;mod;key~` into text input
-
-### Changed
-
-- Changed slash-command autocomplete list rendering to combine command hint and description in a single displayed suggestion text
-- Changed render scheduling to throttle `requestRender` calls to roughly 60fps by batching updates
-- Changed terminal input handling to process complete cell-size responses without buffering partial input
-- Changed `KeyId` to accept super-modifier combinations and improve typed key-id validation
-
-### Fixed
-
 - Normalized line output during rendering to correct Thai/Lao AM glyph composition for displayed text
 - Fixed duplicated Kitty key input emissions by dropping the matching unmodified follow-up sequence after a Kitty CSI-u printable-key event
 
 ## [14.9.5] - 2026-05-12
+
 ### Fixed
 
 - Fixed rapidly blinking cursor artifact during task execution by consolidating cursor control sequences into the synchronized output buffer ([#992](https://github.com/can1357/oh-my-pi/issues/992))
@@ -238,6 +273,7 @@
 - Autocomplete fuzzy discovery now accepts optional SearchDb instance for faster searches
 
 ## [13.16.0] - 2026-03-27
+
 ### Changed
 
 - Updated tab replacement in editor text sanitization to respect configured tab width setting
@@ -253,6 +289,7 @@
 - Fixed editor consuming user-rebound copy keys, preventing custom keybindings from working in the editor
 
 ## [13.14.1] - 2026-03-21
+
 ### Added
 
 - Added Ctrl+_ as an additional default shortcut for undo
@@ -273,17 +310,20 @@
 - Fixed paste marker expansion to handle special regex replacement tokens ($1, $2, $&, $$, $`, $') literally in pasted content
 
 ## [13.11.0] - 2026-03-12
+
 ### Fixed
 
 - Fixed OSC 11 background color detection to correctly handle partial escape sequences that arrive mid-buffer, preventing user input from being swallowed
 - Fixed race condition where overlapping OSC 11 queries would be incorrectly cancelled by DA1 sentinels from previous queries
 
 ## [13.7.5] - 2026-03-04
+
 ### Changed
 
 - Extracted word navigation logic into reusable `moveWordLeft` and `moveWordRight` utility functions for consistent cursor movement across components
 
 ## [13.6.2] - 2026-03-03
+
 ### Fixed
 
 - Fixed cursor positioning when content shrinks to empty without clearOnShrink enabled
@@ -293,6 +333,7 @@
 ### Fixed
 
 - Fixed viewport repaint scrollback accounting during resize oscillation to avoid double-scrolling on height shrink and added exact-row scrollback assertions in overlay regression coverage ([#228](https://github.com/can1357/oh-my-pi/issues/228), [#234](https://github.com/can1357/oh-my-pi/issues/234))
+
 ## [13.5.3] - 2026-03-01
 
 ### Fixed
@@ -302,6 +343,7 @@
 - Fixed cursor positioning instability when appending content under external cursor relocation by using absolute screen addressing instead of relative cursor movement
 
 ## [13.5.2] - 2026-03-01
+
 ### Breaking Changes
 
 - Removed `getMermaidImage` callback from MarkdownTheme; replaced with `getMermaidAscii` that accepts ASCII string instead of image data
@@ -312,6 +354,7 @@
 - Mermaid diagrams now render as ASCII text instead of terminal graphics protocol images
 
 ## [13.5.1] - 2026-03-01
+
 ### Fixed
 
 - Fixed viewport shift handling to prevent stale content when mixed updates remap screen rows
@@ -339,6 +382,7 @@
 
 - Fixed stale/duplicated terminal cursor dedup state by synchronizing `#lastCursorSequence` in all render write paths (hard reset, viewport repaint, deleted-lines clear path, append fast path, and differential path).
 - Fixed scroll overshoot on `stop()` when content fills the viewport by clamping target row movement to valid screen rows.
+
 ## [13.4.0] - 2026-03-01
 
 ### Added
@@ -360,6 +404,7 @@
 - Restored terminal image protocol override and fallback detection for image rendering, including `PI_FORCE_IMAGE_PROTOCOL` support and Kitty fallback for screen/tmux/ghostty-style TERM environments.
 
 ## [13.3.8] - 2026-02-28
+
 ### Breaking Changes
 
 - Changed mermaid hash type from string to bigint in `getMermaidImage` callback and `extractMermaidBlocks` return type
@@ -381,6 +426,7 @@
 - Fixed stale viewport rows appearing when terminal height increases by triggering full re-render on height changes
 
 ## [12.18.0] - 2026-02-21
+
 ### Fixed
 
 - Fixed viewport synchronization issue by clearing scrollback when terminal state becomes desynced during full re-renders
@@ -409,18 +455,21 @@
 - Fixed incremental stale-row clearing to use erase-below semantics in synchronized output, reducing leftover-line artifacts after shrink operations.
 
 ## [12.9.0] - 2026-02-17
+
 ### Added
 
 - Exported `getTerminalId()` function to get a stable identifier for the current terminal, with support for TTY device paths and terminal multiplexers
 - Exported `getTtyPath()` function to resolve the TTY device path for stdin via POSIX `ttyname(3)`
 
 ## [12.5.0] - 2026-02-15
+
 ### Added
 
 - Added `cursorOverride` and `cursorOverrideWidth` properties to customize the end-of-text cursor glyph with ANSI-styled strings
 - Added `getUseTerminalCursor()` method to query the terminal cursor mode setting
 
 ## [11.10.0] - 2026-02-10
+
 ### Added
 
 - Added `hint` property to autocomplete items to display dim ghost text after cursor when item is selected
@@ -433,6 +482,7 @@
 - Updated editor to render inline hint text as dim ghost text after cursor when autocomplete suggestions are active or provider supplies hints
 
 ## [11.8.0] - 2026-02-10
+
 ### Added
 
 - Added Alt+Y keybinding to cycle through kill ring entries (yank-pop)
@@ -449,6 +499,7 @@
 - Changed undo coalescing in Input component to group consecutive word typing into single undo units
 
 ## [11.4.1] - 2026-02-06
+
 ### Fixed
 
 - Fixed terminal scrolling when displaying overlays after rendering large content, preventing hundreds of blank lines from being output
@@ -541,6 +592,7 @@
 - Fixed handling of private use Unicode codepoints (U+E000 to U+F8FF) in Kitty key decoding to prevent invalid character interpretation
 
 ## [9.7.0] - 2026-02-01
+
 ### Breaking Changes
 
 - Removed `Key` helper object from public API; use string literals like `"ctrl+c"` instead of `Key.ctrl("c")`
@@ -552,6 +604,7 @@
 - Simplified `isKeyRelease()` and `isKeyRepeat()` to use regex pattern matching instead of string inclusion checks
 
 ## [9.6.2] - 2026-02-01
+
 ### Changed
 
 - Renamed `EllipsisKind` enum to `Ellipsis` for clearer API naming
@@ -565,6 +618,7 @@
 - Removed `extractAnsiCode` function from public API
 
 ## [9.6.1] - 2026-02-01
+
 ### Changed
 
 - Improved performance of key ID parsing with optimized cache lookup strategy
@@ -575,12 +629,14 @@
 - Removed `visibleWidth` benchmark file in favor of Kitty sequence benchmarking
 
 ## [9.5.0] - 2026-02-01
+
 ### Changed
 
 - Improved fuzzy file search performance by using native implementation instead of spawning external process
 - Replaced external `fd` binary with native fuzzy path search for `@`-prefixed autocomplete
 
 ## [9.4.0] - 2026-01-31
+
 ### Added
 
 - Exported `padding` utility function for creating space-padded strings efficiently
@@ -592,59 +648,74 @@
 ## [9.2.2] - 2026-01-31
 
 ### Added
+
 - Added setAutocompleteMaxVisible() configuration (3-20 items)
 - Added image detection to terminal capabilities (containsImage method)
 - Added stdin monitoring to detect stalled input events and log warnings
 
 ### Changed
+
 - Improved blockquote rendering with text wrapping in Markdown component
 - Restructured terminal capabilities from interface-based to class-based model
 - Improved table column width calculation with word-aware wrapping
 - Refactored text utilities to use native WASM implementations for strings >256 chars with JS fast path
 
 ### Fixed
+
 - Simplified terminal write error handling to mark terminal as dead on any write failure
 - Fixed multi-line strings in renderOutputBlock causing width overflow
 - Fixed slash command autocomplete applying stale completion when typing quickly
 
 ### Removed
+
 - Removed TUI layout engine exports from public API (BoxNode, ColumnNode, LayoutNode, etc.)
 
 ## [8.12.7] - 2026-01-29
 
 ### Fixed
+
 - Fixed slash command autocomplete applying stale completion when typing quickly
 
 ## [8.4.1] - 2026-01-25
 
 ### Added
+
 - Added fuzzy match function for autocomplete suggestions
+
 ## [8.4.0] - 2026-01-25
 
 ### Changed
+
 - Added Ctrl+Backspace as a delete-word-backward keybinding and improved modified backspace matching
 
 ### Fixed
+
 - Terminal gracefully handles write failures by marking dead instead of exiting the process
 - Reserved cursor space for zero padding and corrected end-of-line cursor rendering to prevent wrap glitches
 - Corrected editor end-of-line cursor rendering assertion to use includes() instead of endsWith()
+
 ## [8.2.0] - 2026-01-24
 
 ### Added
+
 - Added mermaid diagram rendering engine (renderMermaidToPng) with mmdc CLI integration
 - Added terminal graphics encoding (iTerm2/Kitty) for mermaid diagrams with automatic width scaling
 - Added mermaid block extraction and deduplication utilities (extractMermaidBlocks)
 
 ### Changed
+
 - Updated TypeScript configuration for better publish-time configuration handling with tsconfig.publish.json
 - Migrated file system operations from synchronous to asynchronous APIs in autocomplete provider for non-blocking I/O
 - Migrated node module imports from named to namespace imports across all packages for consistency with project guidelines
 
 ### Fixed
+
 - Fixed crash when terminal becomes unavailable (EIO errors) by exiting gracefully instead of throwing
 - Fixed potential errors during emergency terminal restore when terminal is already dead
 - Fixed autocomplete race condition by tracking request ID to prevent stale suggestion results
+
 ## [6.8.3] - 2026-01-21
+
 ### Added
 
 - Added undo support in the editor via `Ctrl+-`
@@ -700,6 +771,7 @@
 - Fixed Alt+letter key combinations for better recognition
 
 ## [5.3.1] - 2026-01-15
+
 ### Fixed
 
 - Fixed rendering issues on Windows by preventing re-entrant renders
@@ -729,27 +801,32 @@
 ## [4.7.0] - 2026-01-12
 
 ### Fixed
+
 - Remove trailing space padding from Text, Markdown, and TruncatedText components when no background color is set (fixes copied text including unwanted whitespace)
 
 ## [4.6.0] - 2026-01-12
 
 ### Added
+
 - Add fuzzy matching module (`fuzzyMatch`, `fuzzyFilter`) for command autocomplete
 - Add `getExpandedText()` to editor for expanding paste markers
 - Add backslash+enter newline fallback for terminals without Kitty protocol
 
 ### Fixed
+
 - Remove Kitty protocol query timeout that caused shift+enter delays
 - Add bracketed paste check to prevent false key release/repeat detection
 - Rendering optimizations: only re-render changed lines
 - Refactor input component to use keybindings manager
 
 ## [4.4.4] - 2026-01-11
+
 ### Fixed
 
 - Fixed Ctrl+Enter sequences to insert new lines in the editor
 
 ## [4.2.1] - 2026-01-11
+
 ### Changed
 
 - Improved file autocomplete to show directory listing when typing `@` with no query, and fall back to prefix matching when fuzzy search returns no results
@@ -760,11 +837,13 @@
 - Fixed `fd` tool detection to automatically find `fd` or `fdfind` in PATH when not explicitly configured
 
 ## [4.1.0] - 2026-01-10
+
 ### Added
 
 - Added persistent prompt history storage support via `setHistoryStorage()` method, allowing history to be saved and restored across sessions
 
 ## [4.0.0] - 2026-01-10
+
 ### Added
 
 - `EditorComponent` interface for custom editor implementations
@@ -795,6 +874,7 @@
 - Fixed text wrapping allowing long whitespace tokens to exceed line width
 
 ## [3.20.0] - 2026-01-06
+
 ### Added
 
 - Added `isCapsLock` helper function for detecting Caps Lock key press via Kitty protocol
@@ -826,6 +906,7 @@
 - Added support for custom spinner frames in the Loader component
 
 ## [3.9.1337] - 2026-01-04
+
 ### Added
 
 - Added `setTopBorder()` method to Editor component for displaying custom status content in the top border
@@ -838,6 +919,7 @@
 - Changed cursor style from block to thin blinking bar (▏) at end of line
 
 ## [1.500.0] - 2026-01-03
+
 ### Added
 
 - Added `getText()` method to Text component for retrieving current text content
@@ -902,4 +984,4 @@ Initial release under @oh-my-pi scope. See previous releases at [badlogic/pi-mon
 
 ### Fixed
 
-- **Readline-style Ctrl+W**: Now skips trailing whitespace before deleting the preceding word, matching standard readline behavior. ([#306](https://github.com/badlogic/pi-mono/pull/306) by [@kim0](https://github.com/kim0))
+- **Readline-style Ctrl+W**: Now skips trailing whitespace before deleting the preceding word, matching standard readline behavior. ([#306](https://github.com/badlogic/pi-mono/pull/306) by [@kim0](https://github.com/kim0))

package/README.md

@@ -513,7 +513,7 @@ The TUI uses three rendering strategies:
 2. **Width Changed or Change Above Viewport**: Clear screen and full re-render
 3. **Normal Update**: Move cursor to first changed line, clear to end, render changed lines
 
-All updates are wrapped in **synchronized output** (`\x1b[?2026h` ... `\x1b[?2026l`) for atomic, flicker-free rendering.
+All updates are wrapped in **synchronized output** (`\x1b[?2026h` ... `\x1b[?2026l`) for atomic, flicker-free rendering unless `PI_NO_SYNC_OUTPUT=1` is set. The opt-out removes only the DEC 2026 wrapper; paint writes still guard terminal autowrap to avoid pending-wrap cursor artifacts.
 
 ## Terminal Interface
 

package/dist/types/terminal-capabilities.d.ts

@@ -16,7 +16,8 @@ export declare class TerminalInfo {
     readonly trueColor: boolean;
     readonly hyperlinks: boolean;
     readonly notifyProtocol: NotifyProtocol;
-    constructor(id: TerminalId, imageProtocol: ImageProtocol | null, trueColor: boolean, hyperlinks: boolean, notifyProtocol?: NotifyProtocol);
+    readonly eagerEraseScrollbackRisk: boolean;
+    constructor(id: TerminalId, imageProtocol: ImageProtocol | null, trueColor: boolean, hyperlinks: boolean, notifyProtocol?: NotifyProtocol, eagerEraseScrollbackRisk?: boolean);
     isImageLine(line: string): boolean;
     formatNotification(message: string): string;
     sendNotification(message: string): void;
@@ -28,6 +29,29 @@ export declare function isNotificationSuppressed(): boolean;
  * Windows Terminal introduced SIXEL support in preview 1.22.
  */
 export declare function isWindowsTerminalPreviewSixelSupported(env?: NodeJS.ProcessEnv, platform?: NodeJS.Platform): boolean;
+/**
+ * Whether eager live-frame native scrollback rebuilds are unsafe when the
+ * terminal viewport position is unobservable.
+ *
+ * A TUI history rebuild emits xterm ED3 (`CSI 3 J`, erase saved lines). On the
+ * terminals below, ED3 can disturb a reader parked in native scrollback during
+ * streaming: kitty/ghostty/alacritty/VTE clamp the scroll offset back to the
+ * active tail when saved lines are erased. WezTerm, macOS Terminal.app, and
+ * iTerm2 expose scrollback-only clears via ED3/terminfo E3; that still
+ * invalidates a reader's scrollback position during live streaming.
+ *
+ * Windows Terminal erases its host scrollback on ED3 and repositions the
+ * viewport against the shortened buffer, so a scrolled-up reader is yanked.
+ * Native win32 is excluded here because the renderer guards it with dedicated
+ * platform checks (the viewport position is never observable on Windows — see
+ * `Terminal.isNativeViewportAtBottom`); a `WT_SESSION` sighting on any other
+ * platform means the outer host is Windows Terminal fronting a WSL distro (WT
+ * propagates the variable into the Linux environment), where the same ED3
+ * yank applies. See #1610.
+ *
+ * Pure helper for tests and `TERMINAL` trait construction. See #1682 and #1719.
+ */
+export declare function detectTerminalEagerEraseScrollbackRisk(env?: NodeJS.ProcessEnv, platform?: NodeJS.Platform): boolean;
 export declare const TERMINAL_ID: TerminalId;
 export declare const TERMINAL: TerminalInfo;
 /**

package/dist/types/terminal.d.ts

@@ -30,6 +30,32 @@ export interface Terminal {
     /**
      * Returns whether the native terminal viewport is at the scrollback tail when
      * the host exposes that state. `undefined` means the terminal cannot report it.
+     *
+     * `ProcessTerminal` deliberately does not implement this — no real terminal
+     * can answer it truthfully:
+     *
+     * - POSIX terminals expose no scrollback-position API at all.
+     * - Every modern Windows terminal host (Windows Terminal, VS Code, Tabby,
+     *   Hyper, Alacritty, WezTerm, JetBrains, …) fronts console apps through
+     *   ConPTY, where kernel32's `GetConsoleScreenBufferInfo` describes the
+     *   pseudo-console buffer. That buffer is pinned to the visible grid —
+     *   scrollback lives in the host UI, invisible to console APIs
+     *   (microsoft/terminal#10191) — so a probe reads "at bottom" no matter
+     *   where the user scrolled. Trusting it let streaming-time rebuilds emit
+     *   `\x1b[3J` and yank scrolled readers: #1635 (Windows Terminal), #1746
+     *   (Tabby and other ConPTY hosts). No env var distinguishes these hosts
+     *   (Tabby sets none), so trust cannot be conditional on the environment.
+     * - Legacy conhost (the only non-ConPTY host) keeps a real scrollback
+     *   buffer, but its window follows the output cursor: a probe comparing
+     *   `srWindow.Bottom` against `dwSize.Y - 1` reads "scrolled up" for a user
+     *   following live output until all ~9001 buffer rows fill, permanently
+     *   blocking checkpoint scrollback reconciliation.
+     *
+     * The renderer treats a missing implementation / `undefined` as "unknown":
+     * live mutations defer destructive rebuilds and reconcile native scrollback
+     * at explicit checkpoints (prompt submit), where the user's keystroke has
+     * already pinned the host viewport to the bottom. Only test terminals
+     * (xterm.js-backed) implement this with a real answer.
      */
     isNativeViewportAtBottom?(): boolean | undefined;
     /**
@@ -41,21 +67,6 @@ export interface Terminal {
     /** The last detected terminal appearance, or undefined if not yet known. */
     get appearance(): TerminalAppearance | undefined;
 }
-/**
- * Whether the native console viewport-position probe should be consulted.
- *
- * Returns `true` only on native Windows that is *not* fronted by Windows
- * Terminal. The kernel32 `GetConsoleScreenBufferInfo` API answers about the
- * ConPTY pseudo-console — which is always pinned to its tail — and not about
- * the user-visible scrollback in modern hosts. Treat any such host as
- * unreportable so the renderer falls back to the deferred-rebuild path.
- *
- * Pure helper for unit testing; the runtime call site reads `$env` /
- * `process.platform`. See #1635.
- */
-export declare function shouldTrustNativeViewportProbe(env?: {
-    WT_SESSION?: string | undefined;
-}, platform?: NodeJS.Platform): boolean;
 /**
  * Real terminal using process.stdin/stdout
  */
@@ -65,20 +76,6 @@ export declare class ProcessTerminal implements Terminal {
     get appearance(): TerminalAppearance | undefined;
     onAppearanceChange(callback: (appearance: TerminalAppearance) => void): void;
     start(onInput: (data: string) => void, onResize: () => void): void;
-    /**
-     * Returns true when Windows' active console viewport is at the scrollback tail.
-     * POSIX terminals do not expose native scrollback position through a standard API.
-     *
-     * On native Windows running under Windows Terminal (the default modern
-     * host), the `kernel32` probe answers about the ConPTY pseudo-console — not
-     * the user-visible WT viewport — so it would always read "at bottom" while
-     * the user is scrolled up. Return `undefined` there so the renderer falls
-     * back to the POSIX-style deferred-rebuild path: streaming mutations stay
-     * non-destructive (no `\x1b[3J`), and the rebuild fires at the next prompt
-     * checkpoint via {@link TUI.refreshNativeScrollbackIfDirty} where the user
-     * is already pinned to the bottom by the editor keystroke. See #1635.
-     */
-    isNativeViewportAtBottom(): boolean | undefined;
     drainInput(maxMs?: number, idleMs?: number): Promise<void>;
     stop(): void;
     write(data: string): void;

package/dist/types/tui.d.ts

@@ -171,9 +171,20 @@ export declare class TUI extends Container {
      * non-destructive repaint. This trades the anti-yank guarantee for a clean,
      * duplicate-free history and is meant for windows where output above the fold
      * is actively re-rendering — e.g. a tool whose result is still streaming and
-     * re-laying-out rows that have already scrolled into history. A snap to the tail
-     * is acceptable there. A terminal that can report a *known*-scrolled viewport
-     * (Windows) still defers; only the unknown case is forced to rebuild.
+     * re-laying-out rows that have already scrolled into history. A terminal that
+     * reports a *known*-scrolled viewport still defers, as does native Windows
+     * (the viewport is never observable there and ConPTY hosts erase host
+     * scrollback on ED3 — #1635/#1746); only the unknown POSIX case is forced to
+     * rebuild. POSIX hosts known to disturb scrolled readers on xterm ED3
+     * (`CSI 3 J`, erase saved lines) also defer the eager opt-in; checkpoint and
+     * direct user-input rebuilds are unaffected.
+     *
+     * Disabling does not take effect until the next frame has been classified:
+     * the event batch that ends a foreground stream both removes its UI rows
+     * (loader/status teardown — a shrink) and clears this flag before the
+     * throttled render timer fires. If the flag dropped immediately, that
+     * teardown frame would hit the ED3-risk idle deferral and freeze on screen
+     * (stale spinner) until the next keystroke.
      */
     setEagerNativeScrollbackRebuild(enabled: boolean): void;
     setFocus(component: Component | null): void;

package/package.json

@@ -1,7 +1,7 @@
 {
 	"type": "module",
 	"name": "@oh-my-pi/pi-tui",
-	"version": "15.7.6",
+	"version": "15.8.2",
 	"description": "Terminal User Interface library with differential rendering for efficient text-based applications",
 	"homepage": "https://omp.sh",
 	"author": "Can Boluk",
@@ -37,8 +37,8 @@
 		"fmt": "biome format --write ."
 	},
 	"dependencies": {
-		"@oh-my-pi/pi-natives": "15.7.6",
-		"@oh-my-pi/pi-utils": "15.7.6",
+		"@oh-my-pi/pi-natives": "15.8.2",
+		"@oh-my-pi/pi-utils": "15.8.2",
 		"lru-cache": "11.5.1",
 		"marked": "^18.0.4"
 	},

package/src/components/markdown.ts

@@ -146,22 +146,24 @@ const DEFAULT_COLOR_SWATCH_GLYPH = "■";
 // entities like ☃ and paths like foo#fff) and not trailed by more hex
 // (so over-long runs never produce a misleading swatch). Length/letter rules
 // are enforced in classifyHexColor since the alternation can't express "exactly
-// 3, 4, 6, or 8".
+// 3, 6, or 8".
 const HEX_COLOR_REGEX = /(?<![\w#&])#([0-9a-fA-F]{3,8})(?![0-9a-fA-F])/g;
 const HEX_COLOR_EXACT_REGEX = /^#([0-9a-fA-F]{3,8})$/;
 
 /**
  * Decide whether a run of hex digits denotes a renderable CSS color.
  *
- * Only the canonical CSS lengths (#RGB, #RGBA, #RRGGBB, #RRGGBBAA) qualify. In
- * `strict` mode (bare prose) a 3/4-digit run must contain a hex letter, so the
+ * Only the canonical CSS lengths (#RGB, #RRGGBB, #RRGGBBAA) qualify. The 4-digit
+ * #RGBA form is deliberately excluded: it collides with hashline `#TAG` snapshot
+ * tags (4 hex digits, e.g. #6C5E), which would otherwise sprout spurious swatches.
+ * In `strict` mode (bare prose) a 3-digit run must contain a hex letter, so the
  * far more common short issue/PR references (#123, #1011) don't sprout swatches.
  * Codespans opt out of strictness — the backticks already signal "this is a color".
  */
 function classifyHexColor(hex: string, strict: boolean): boolean {
 	const n = hex.length;
-	if (n !== 3 && n !== 4 && n !== 6 && n !== 8) return false;
-	if (strict && n <= 4 && !/[a-fA-F]/.test(hex)) return false;
+	if (n !== 3 && n !== 6 && n !== 8) return false;
+	if (strict && n === 3 && !/[a-fA-F]/.test(hex)) return false;
 	return true;
 }