jeo-code 0.8.31 → 0.8.33

package/CHANGELOG.md

@@ -6,6 +6,35 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 The README mirrors the latest 5 entries — regenerate with `bun run changelog:sync`.
 
+## [0.8.33] - 2026-07-20
+_Real terminal-resize testing (repeated tmux resize-window + keystroke reproductions, byte-for-byte ANSI replay outside jeo/tmux to isolate root causes deterministically) uncovered and closed a progressive screen-corruption bug: resizing down to a narrow terminal (e.g. a ~20-column tmux pane) produced a growing stack of duplicate status-bar lines on every subsequent keystroke, and a separate, independently-reproducible scroll bug in the mid-turn live renderer._
+
+### Fixed
+- **Narrow-terminal overflow across three width-floor call sites, the actual root cause of the live-reproduced corruption** — `src/tui/components/status.ts`'s `renderStatusBar` and its internal `leftBudget`, and `src/tui/components/input-box.ts`'s `renderInputFrame`, each clamped their `cols` UP to a fixed floor (24, 24, 8) regardless of the REAL terminal width, so a genuinely narrow terminal (e.g. 20 columns) still received a 24-column-wide status bar / input box. A real terminal hard-wraps that overflow, which desynced the idle-prompt footer's own row bookkeeping on every subsequent repaint — reproduced live via tmux (`resize-window` down + repeated keystrokes) as a stack of duplicate `⬢ model … ▦ ctx%` lines that grew by one on every keystroke, and confirmed via a byte-for-byte replay of the exact captured ANSI sequences through `cat` into a fresh tmux pane with jeo entirely absent — proving the bug lived in the emitted bytes themselves, not timing or readline interaction. All three floors now clamp to a minimum of 1, degrading gracefully (a small, correctly-sized box/bar) instead of overflowing.
+- **`src/tui/components/welcome.ts`'s narrow (`cols < 30`) one-line fallback no longer overflows** — an unbounded `jeo v{version} · {model}` line previously overflowed a real narrow terminal by up to 47 columns with a realistic provider-qualified model id (e.g. `antigravity/claude-sonnet-4-6 (antigravity)`). Now truncated to `cols - 1` — the SAME "leave the last column free" margin the boxed banner already uses elsewhere in this file, deliberately NOT `cols` exactly: a line filled to the exact terminal width followed by its own trailing newline is ambiguous to real terminals (pending-autowrap vs. explicit-LF), which independently reproduced the same duplicate-line corruption even after the overflow itself was fixed.
+- **`src/tui/renderer.ts`'s reserve-mode resize path no longer scrolls the terminal on a shrink** — `Renderer.render()`'s resize branch called `clear()` unconditionally, which zeroes `coverRows`/`prev` as an independent write; the SAME call's own reserve-block then read that now-wrong occupancy (0) and spuriously inserted real `"\n"` characters even when the post-resize frame was SHORTER than the pre-resize one. Literal `"\n"` genuinely scrolls a real terminal, corrupting whatever sits above the live frame and permanently desyncing the renderer's row math. Reserve mode now uses the same `reset()`-style bookkeeping the periodic self-heal resync already relies on (remembers the occupied rows via `coverRows`, no output) instead of an immediate `clear()`; non-reserve (alt-screen/pipe) mode is unaffected and keeps its defensive full clear. Reproduced deterministically with a standalone `Renderer` unit harness (no tmux/timing involved) before and after the fix.
+
+### Verified
+- `test/status-bar.test.ts`, `test/input-box.test.ts` — new regression tests: neither ever emits a line wider than a realistically narrow `cols` (5 through 23), closing the exact floor-overflow class found live.
+- `test/tui-welcome.test.ts` — updated + new tests: the narrow fallback is now `cols - 1`-capped (never overflows, even with a long provider-qualified model id).
+- `test/tui-renderer.test.ts` — new regression test: a reserve-mode resize down to a shorter frame never emits `"\n"`, and a second render right after stays clean (no lingering desync).
+- Full live tmux reproduction cycle for BOTH the idle-prompt path and the mid-turn `LaunchTui` path: resized a real `jeo --tmux` session down (e.g. 90×26 → 55×18, 80×24 → 20×10) and typed multiple keystrokes after each — before this pass, the idle-prompt footer visibly duplicated once per keystroke; after, it stays clean across repeated keystrokes at both a moderate (55×18) and an extreme (20×10) narrow width, confirmed via direct pane capture, not just unit assertions.
+- Full `bun test` — 3097 pass / 0 fail across 304 files.
+- `bun run typecheck` — no errors.
+
+## [0.8.32] - 2026-07-20
+_gjc parity: TUI display-width/wrapping is now grapheme-cluster-aware for emoji sequences (VS16 presentation, skin-tone modifiers, keycaps, ZWJ-joined emoji like family/profession glyphs), fixing box-border and wrap misalignment ("깨짐") that the old per-code-point width summation produced whenever such a sequence appeared in a message — Korean/CJK-only text was already correctly handled and is unaffected._
+
+### Fixed
+- **Display-width no longer over/under-counts emoji sequences, so box borders and hard-wraps never misalign when one appears in a message** (`src/tui/components/width.ts`) — gjc parity (`#1996` "preserve … Unicode grapheme semantics for … VS16 emoji presentation, ZWJ, keycaps, and emoji modifiers"). The old `visibleWidth`/`truncateToWidth` summed `charWidth()` per CODE POINT, which is wrong for any sequence a terminal renders as ONE glyph: `❤️` (heart + VS16) summed to 1 column where terminals render 2; `👍🏽` (thumbs-up + Fitzpatrick skin-tone modifier) summed to 4 where terminals render 2; a 4-person ZWJ family emoji (`👨‍👩‍👧‍👦`) summed to 8 where terminals render 2 — quantified live against the actual old per-code-point path before fixing (not asserted from inference). New `nextGraphemeCluster()` absorbs VS15/VS16, Fitzpatrick modifiers (`U+1F3FB`-`U+1F3FF`), keycap combiners (`U+20E3`), combining marks, and ZWJ-joined chains into one atomic width-2 (or width-1 for VS15 text-presentation) unit; `visibleWidth`/`truncateToWidth` (and therefore `wrapTextWithAnsi`, built on both) now consume it instead of raw per-code-point `charWidth()`, and `truncateToWidth` can no longer split one of these sequences in half at a wrap/truncation boundary (a second corruption vector the old code point-by-point cut was exposed to). Korean/CJK/Hangul-only text (no emoji sequences) was already correct and is byte-identical before/after.
+
+### Verified
+- `test/width.test.ts` — 11 pass (was 9): new `nextGraphemeCluster` unit coverage for the VS15/VS16/Fitzpatrick/keycap/ZWJ cases above, plus a `truncateToWidth` atomicity test proving a 2-wide cluster is dropped whole (never half) at a 1-column budget.
+- Live (unmocked) reproduction: quantified the OLD per-code-point sum against the NEW `visibleWidth` for all 4 sequence classes — heart 1→2, thumbs-up+modifier 4→2, ZWJ family 8→2, keycap 1→2 — confirming this was a real, sometimes-severe (family emoji off by 6 columns) miscount, not a hypothetical.
+- Live (unmocked) box-render smoke test: wrapped a real mixed Korean/emoji message (family emoji, VS16 heart, skin-tone thumbs-up) into a 20-column box via `wrapTextWithAnsi` — every wrapped line's `visibleWidth` fit the declared budget with correct padding, confirming no overflow/misalignment end-to-end (not just at the unit level).
+- Full `bun test` — 3092 pass / 0 fail across 304 files (2 transient parallel-load flakes on the first run — unrelated `/model` pin routing + a Node `--inspect-brk` debug-session test, neither touching `width.ts` — both isolated-pass and a full clean re-run confirmed no regression).
+- `bun run typecheck` — no errors.
+
 ## [0.8.31] - 2026-07-20
 _`web_search` no longer silently degrades every non-Anthropic model to keyless DuckDuckGo scraping — OpenAI and Gemini sessions now get their own native, hosted search tool (matching the same active-model-gated, credential-required design Anthropic already had), with DuckDuckGo remaining the always-on terminal fallback for everyone else._
 

package/README.ja.md

@@ -283,11 +283,11 @@ CI は `.github/workflows/npm-publish.yml` で公開します — GitHub リリ
 ## 変更履歴 (Changelog)
 
 <!-- CHANGELOG:START (auto-generated from CHANGELOG.md — run `bun run changelog:sync`) -->
+- **[0.8.33]** (2026-07-20) — Real terminal-resize testing (repeated tmux resize-window + keystroke reproductions, byte-for-byte ANSI replay outside jeo/tmux to isolate root causes deterministically) uncovered and closed a progressive screen-corruption bug: resizing down to a narrow terminal (e.g. a ~20-column tmux pane) produced a growing stack of duplicate status-bar lines on every subsequent keystroke, and a separate, independently-reproducible scroll bug in the mid-turn live renderer.
+- **[0.8.32]** (2026-07-20) — gjc parity: TUI display-width/wrapping is now grapheme-cluster-aware for emoji sequences (VS16 presentation, skin-tone modifiers, keycaps, ZWJ-joined emoji like family/profession glyphs), fixing box-border and wrap misalignment ("깨짐") that the old per-code-point width summation produced whenever such a sequence appeared in a message — Korean/CJK-only text was already correctly handled and is unaffected.
 - **[0.8.31]** (2026-07-20) — `web_search` no longer silently degrades every non-Anthropic model to keyless DuckDuckGo scraping — OpenAI and Gemini sessions now get their own native, hosted search tool (matching the same active-model-gated, credential-required design Anthropic already had), with DuckDuckGo remaining the always-on terminal fallback for everyone else.
 - **[0.8.30]** (2026-07-20) — `bun run build` (the host-only dev binary build) has been silently broken for every user who ran it — a drift between the plain `package.json` `build` script and the actual working release-binary build command (`scripts/ci-release-build-binaries.ts`), which had already documented and fixed the exact same crash.
 - **[0.8.29]** (2026-07-20) — gajae-code (gjc) v0.10.2→v0.11.4 gap analysis: most of that range is gjc-specific architecture jeo intentionally does not replicate (SDK broker/session-index recovery, Gajae Pet, coordinator-mcp, Telegram/Discord rich-delivery internals, browser tab workers, worktree-subcommand removal, RPC durable model selection) — one genuinely applicable TUI bug was found and closed; the CLI empty-non-TTY-stdin fix (gjc #2586) was investigated and found already-correct by construction (jeo's one-shot gate forces true whenever stdin isn't a TTY, regardless of args, so the hang gjc fixed cannot occur here).
-- **[0.8.28]** (2026-07-16) — Improved the welcome UI's right-side table to display dynamic sections (What's New, Flow keys, Project pulse, and Session trail) matching gajae-code (gjc) >= 0.8.0 features.
-- **[0.8.27]** (2026-07-16) — Repeat-read recovery now survives both context-overflow and refusal-result elision without reopening mutating-call loops.
 
 See [CHANGELOG.md](CHANGELOG.md) for the full history.
 <!-- CHANGELOG:END -->

package/README.ko.md

@@ -284,11 +284,11 @@ CI는 `.github/workflows/npm-publish.yml`로 배포합니다 — GitHub 릴리
 ## 변경 이력 (Changelog)
 
 <!-- CHANGELOG:START (auto-generated from CHANGELOG.md — run `bun run changelog:sync`) -->
+- **[0.8.33]** (2026-07-20) — Real terminal-resize testing (repeated tmux resize-window + keystroke reproductions, byte-for-byte ANSI replay outside jeo/tmux to isolate root causes deterministically) uncovered and closed a progressive screen-corruption bug: resizing down to a narrow terminal (e.g. a ~20-column tmux pane) produced a growing stack of duplicate status-bar lines on every subsequent keystroke, and a separate, independently-reproducible scroll bug in the mid-turn live renderer.
+- **[0.8.32]** (2026-07-20) — gjc parity: TUI display-width/wrapping is now grapheme-cluster-aware for emoji sequences (VS16 presentation, skin-tone modifiers, keycaps, ZWJ-joined emoji like family/profession glyphs), fixing box-border and wrap misalignment ("깨짐") that the old per-code-point width summation produced whenever such a sequence appeared in a message — Korean/CJK-only text was already correctly handled and is unaffected.
 - **[0.8.31]** (2026-07-20) — `web_search` no longer silently degrades every non-Anthropic model to keyless DuckDuckGo scraping — OpenAI and Gemini sessions now get their own native, hosted search tool (matching the same active-model-gated, credential-required design Anthropic already had), with DuckDuckGo remaining the always-on terminal fallback for everyone else.
 - **[0.8.30]** (2026-07-20) — `bun run build` (the host-only dev binary build) has been silently broken for every user who ran it — a drift between the plain `package.json` `build` script and the actual working release-binary build command (`scripts/ci-release-build-binaries.ts`), which had already documented and fixed the exact same crash.
 - **[0.8.29]** (2026-07-20) — gajae-code (gjc) v0.10.2→v0.11.4 gap analysis: most of that range is gjc-specific architecture jeo intentionally does not replicate (SDK broker/session-index recovery, Gajae Pet, coordinator-mcp, Telegram/Discord rich-delivery internals, browser tab workers, worktree-subcommand removal, RPC durable model selection) — one genuinely applicable TUI bug was found and closed; the CLI empty-non-TTY-stdin fix (gjc #2586) was investigated and found already-correct by construction (jeo's one-shot gate forces true whenever stdin isn't a TTY, regardless of args, so the hang gjc fixed cannot occur here).
-- **[0.8.28]** (2026-07-16) — Improved the welcome UI's right-side table to display dynamic sections (What's New, Flow keys, Project pulse, and Session trail) matching gajae-code (gjc) >= 0.8.0 features.
-- **[0.8.27]** (2026-07-16) — Repeat-read recovery now survives both context-overflow and refusal-result elision without reopening mutating-call loops.
 
 See [CHANGELOG.md](CHANGELOG.md) for the full history.
 <!-- CHANGELOG:END -->

package/README.md

@@ -291,11 +291,11 @@ Huge thanks to [gajae-code](https://github.com/Yeachan-Heo/gajae-code) for the i
 ## Changelog
 
 <!-- CHANGELOG:START (auto-generated from CHANGELOG.md — run `bun run changelog:sync`) -->
+- **[0.8.33]** (2026-07-20) — Real terminal-resize testing (repeated tmux resize-window + keystroke reproductions, byte-for-byte ANSI replay outside jeo/tmux to isolate root causes deterministically) uncovered and closed a progressive screen-corruption bug: resizing down to a narrow terminal (e.g. a ~20-column tmux pane) produced a growing stack of duplicate status-bar lines on every subsequent keystroke, and a separate, independently-reproducible scroll bug in the mid-turn live renderer.
+- **[0.8.32]** (2026-07-20) — gjc parity: TUI display-width/wrapping is now grapheme-cluster-aware for emoji sequences (VS16 presentation, skin-tone modifiers, keycaps, ZWJ-joined emoji like family/profession glyphs), fixing box-border and wrap misalignment ("깨짐") that the old per-code-point width summation produced whenever such a sequence appeared in a message — Korean/CJK-only text was already correctly handled and is unaffected.
 - **[0.8.31]** (2026-07-20) — `web_search` no longer silently degrades every non-Anthropic model to keyless DuckDuckGo scraping — OpenAI and Gemini sessions now get their own native, hosted search tool (matching the same active-model-gated, credential-required design Anthropic already had), with DuckDuckGo remaining the always-on terminal fallback for everyone else.
 - **[0.8.30]** (2026-07-20) — `bun run build` (the host-only dev binary build) has been silently broken for every user who ran it — a drift between the plain `package.json` `build` script and the actual working release-binary build command (`scripts/ci-release-build-binaries.ts`), which had already documented and fixed the exact same crash.
 - **[0.8.29]** (2026-07-20) — gajae-code (gjc) v0.10.2→v0.11.4 gap analysis: most of that range is gjc-specific architecture jeo intentionally does not replicate (SDK broker/session-index recovery, Gajae Pet, coordinator-mcp, Telegram/Discord rich-delivery internals, browser tab workers, worktree-subcommand removal, RPC durable model selection) — one genuinely applicable TUI bug was found and closed; the CLI empty-non-TTY-stdin fix (gjc #2586) was investigated and found already-correct by construction (jeo's one-shot gate forces true whenever stdin isn't a TTY, regardless of args, so the hang gjc fixed cannot occur here).
-- **[0.8.28]** (2026-07-16) — Improved the welcome UI's right-side table to display dynamic sections (What's New, Flow keys, Project pulse, and Session trail) matching gajae-code (gjc) >= 0.8.0 features.
-- **[0.8.27]** (2026-07-16) — Repeat-read recovery now survives both context-overflow and refusal-result elision without reopening mutating-call loops.
 
 See [CHANGELOG.md](CHANGELOG.md) for the full history.
 <!-- CHANGELOG:END -->

package/README.zh.md

@@ -283,11 +283,11 @@ CI 通过 `.github/workflows/npm-publish.yml` 发布 — GitHub 发布 release
 ## 更新日志 (Changelog)
 
 <!-- CHANGELOG:START (auto-generated from CHANGELOG.md — run `bun run changelog:sync`) -->
+- **[0.8.33]** (2026-07-20) — Real terminal-resize testing (repeated tmux resize-window + keystroke reproductions, byte-for-byte ANSI replay outside jeo/tmux to isolate root causes deterministically) uncovered and closed a progressive screen-corruption bug: resizing down to a narrow terminal (e.g. a ~20-column tmux pane) produced a growing stack of duplicate status-bar lines on every subsequent keystroke, and a separate, independently-reproducible scroll bug in the mid-turn live renderer.
+- **[0.8.32]** (2026-07-20) — gjc parity: TUI display-width/wrapping is now grapheme-cluster-aware for emoji sequences (VS16 presentation, skin-tone modifiers, keycaps, ZWJ-joined emoji like family/profession glyphs), fixing box-border and wrap misalignment ("깨짐") that the old per-code-point width summation produced whenever such a sequence appeared in a message — Korean/CJK-only text was already correctly handled and is unaffected.
 - **[0.8.31]** (2026-07-20) — `web_search` no longer silently degrades every non-Anthropic model to keyless DuckDuckGo scraping — OpenAI and Gemini sessions now get their own native, hosted search tool (matching the same active-model-gated, credential-required design Anthropic already had), with DuckDuckGo remaining the always-on terminal fallback for everyone else.
 - **[0.8.30]** (2026-07-20) — `bun run build` (the host-only dev binary build) has been silently broken for every user who ran it — a drift between the plain `package.json` `build` script and the actual working release-binary build command (`scripts/ci-release-build-binaries.ts`), which had already documented and fixed the exact same crash.
 - **[0.8.29]** (2026-07-20) — gajae-code (gjc) v0.10.2→v0.11.4 gap analysis: most of that range is gjc-specific architecture jeo intentionally does not replicate (SDK broker/session-index recovery, Gajae Pet, coordinator-mcp, Telegram/Discord rich-delivery internals, browser tab workers, worktree-subcommand removal, RPC durable model selection) — one genuinely applicable TUI bug was found and closed; the CLI empty-non-TTY-stdin fix (gjc #2586) was investigated and found already-correct by construction (jeo's one-shot gate forces true whenever stdin isn't a TTY, regardless of args, so the hang gjc fixed cannot occur here).
-- **[0.8.28]** (2026-07-16) — Improved the welcome UI's right-side table to display dynamic sections (What's New, Flow keys, Project pulse, and Session trail) matching gajae-code (gjc) >= 0.8.0 features.
-- **[0.8.27]** (2026-07-16) — Repeat-read recovery now survives both context-overflow and refusal-result elision without reopening mutating-call loops.
 
 See [CHANGELOG.md](CHANGELOG.md) for the full history.
 <!-- CHANGELOG:END -->

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jeo-code",
-  "version": "0.8.31",
+  "version": "0.8.33",
   "description": "Clean, highly optimized AI coding agent using spec-first loop",
   "type": "module",
   "main": "src/cli.ts",

package/src/commands/launch.ts

@@ -764,7 +764,7 @@ export async function runLaunchCommand(args: string[]): Promise<void> {
    *  mid-turn TUI binding): full last reply + full last tool output. */
   const composeDetailLines = (): string[] => {
     if (!lastReply && !lastToolDetail) return [];
-    const sep = "─".repeat(Math.min(48, Math.max(20, (process.stdout.columns ?? 80) - 1)));
+    const sep = "─".repeat(Math.min(48, Math.max(1, (process.stdout.columns ?? 80) - 1)));
     const toolDetail = lastToolDetail
       ? [sep, `detail · full last tool output (${lastToolDetail.tool})`, sep, ...lastToolDetail.output.split("\n").slice(0, 2000).map(sanitizeForTerminal)]
       : [];
@@ -816,7 +816,7 @@ export async function runLaunchCommand(args: string[]): Promise<void> {
             // exact prior conversation instead of a bare message count.
             if (messages.length > 0) {
               resumedWithHistory = true;
-              const sep = "─".repeat(Math.min(48, Math.max(20, (process.stdout.columns ?? 80) - 1)));
+              const sep = "─".repeat(Math.min(48, Math.max(1, (process.stdout.columns ?? 80) - 1)));
               console.log([sep, ...formatTranscript(history, { maxTurns: 6, color: true, unicode: true }), sep].join("\n"));
             }
 
@@ -880,7 +880,7 @@ export async function runLaunchCommand(args: string[]): Promise<void> {
           // screen instead of just a bare message count.
           if (messages.length > 0) {
             resumedWithHistory = true;
-            const sep = "─".repeat(Math.min(48, Math.max(20, (process.stdout.columns ?? 80) - 1)));
+            const sep = "─".repeat(Math.min(48, Math.max(1, (process.stdout.columns ?? 80) - 1)));
             console.log([sep, ...formatTranscript(history, { maxTurns: 6, color: true, unicode: true }), sep].join("\n"));
           }
 
@@ -2209,7 +2209,7 @@ export async function runLaunchCommand(args: string[]): Promise<void> {
   // so it never repeats. Screen-safe: prints BEFORE the prompt is armed.
   try {
     const whatsNew = await consumeLaunchWhatsNew({
-      cols: Math.min(100, Math.max(40, (process.stdout.columns ?? 80) - 2)),
+      cols: Math.min(100, Math.max(1, (process.stdout.columns ?? 80) - 2)),
       unicode: supportsUnicode(),
       color: welcomeTheme.color,
     });
@@ -2224,7 +2224,7 @@ export async function runLaunchCommand(args: string[]): Promise<void> {
     {
       const card = formatForgeBox(
         { title: "[skill]", lines: skillInvocationCard(skill, intent) },
-        { width: scaleForgeWidth(Math.min(100, Math.max(40, (process.stdout.columns ?? 80) - 2))), unicode: supportsUnicode(), paint: accentPaint(uiTheme), paintShadow: accentShadowPaint(uiTheme), color: uiTheme.color },
+        { width: scaleForgeWidth(Math.min(100, Math.max(1, (process.stdout.columns ?? 80) - 2))), unicode: supportsUnicode(), paint: accentPaint(uiTheme), paintShadow: accentShadowPaint(uiTheme), color: uiTheme.color },
       );
       logLines(card);
     }
@@ -2729,7 +2729,7 @@ export async function runLaunchCommand(args: string[]): Promise<void> {
   let lastFooterKey = "";
   const logLines = (lines: string | string[]) => {
     const arr = Array.isArray(lines) ? lines : [lines];
-    const cols = Math.max(20, (process.stdout.columns ?? 80) - 1);
+    const cols = Math.max(1, (process.stdout.columns ?? 80) - 1);
     for (const line of arr) {
       console.log(truncateAnsi(line, cols));
     }
@@ -2934,7 +2934,7 @@ export async function runLaunchCommand(args: string[]): Promise<void> {
     });
   };
   const previewLines = (line: string, selected = -1): string[] => {
-    const cols = Math.max(24, (process.stdout.columns ?? 80) - 1);
+    const cols = Math.max(1, (process.stdout.columns ?? 80) - 1);
     // Caret offset comes from readline's live cursor when it matches the rendered
     // line (arrow keys/Home/End move it); otherwise (history nav mismatch) caret
     // sits at the end of the text.
@@ -2983,7 +2983,7 @@ export async function runLaunchCommand(args: string[]): Promise<void> {
   // with ↑/↓ counters. Recomputes the scroll bound/page size each paint so scroll
   // keys can clamp correctly. Mirrors the mid-turn LaunchTui panel.
   const historyPreviewLines = (detail: string[]): string[] => {
-    const cols = Math.max(24, (process.stdout.columns ?? 80) - 1);
+    const cols = Math.max(1, (process.stdout.columns ?? 80) - 1);
     const physical = detail.flatMap(line => line.split("\n")).map(line => truncateAnsi(line, cols));
     const bodyLimit = Math.max(1, footerRows - 2); // status bar + title rows
     const scrollable = physical.length > bodyLimit;

package/src/tui/components/input-box.ts

@@ -107,7 +107,13 @@ function normalizeHighlights(
  * can park the REAL terminal cursor right after `>` — moving with the arrow keys.
  */
 export function renderInputFrame(line: string, opts: InputBoxOptions = {}): InputFrame {
-  const cols = Math.max(24, Math.trunc(opts.cols ?? 80));
+  // Never clamp UP past what the caller reports as the real terminal width — a
+  // fixed floor here (previously 24) silently overflowed any narrower terminal
+  // (e.g. a resize down to 20 cols still drew a 24-col box), which real terminals
+  // then hard-wrap/split at the boundary (the exact box-border corruption a real
+  // resize-down reproduces live). Degrading to a very small, ugly-but-correctly-
+  // sized box is strictly better than one that overflows and gets torn.
+  const cols = Math.max(1, Math.trunc(opts.cols ?? 80));
   const useColor = opts.color !== false;
   const placeholder = opts.placeholder ?? "Type your message...";
   const bodyWidth = Math.max(1, cols - 4);

package/src/tui/components/status.ts

@@ -66,7 +66,14 @@ function shortenCwd(cwd: string, maxLen: number, unicode: boolean): string {
 export function renderStatusBar(d: StatusBarData): string {
   const unicode = d.unicode !== false;
   const useColor = d.color !== false;
-  const cols = Math.max(24, Math.trunc(d.cols));
+  // Never clamp UP past the caller's real terminal width — a fixed floor here
+  // (previously 24) silently overflowed any narrower terminal (e.g. a resize down
+  // to 20 cols still emitted a 24-col status bar), which a real terminal then
+  // hard-wraps at the boundary and desyncs the idle-footer's own row bookkeeping
+  // on every subsequent repaint (reproduced live: a growing stack of duplicate
+  // status-bar lines on each keystroke after a resize-down, root-caused to this
+  // exact overflow via a byte-for-byte ANSI replay outside jeo/tmux entirely).
+  const cols = Math.max(1, Math.trunc(d.cols));
   const sep = " / ";
 
   // Right side first — it has priority and fixed width.
@@ -97,7 +104,7 @@ export function renderStatusBar(d: StatusBarData): string {
     bits.push(`${unicode ? "⑂" : "y"} ${d.branch}${dirty}`);
   }
   // Budget the cwd into whatever width remains (right stats + 2-col gap reserved).
-  const leftBudget = Math.max(8, cols - rightWidth - (rightWidth > 0 ? 2 : 0));
+  const leftBudget = Math.max(1, cols - rightWidth - (rightWidth > 0 ? 2 : 0));
   if (d.cwd) {
     const used = visibleWidth(` ${bits.join(sep)}${sep}${unicode ? "▸" : ">"}  `);
     const room = leftBudget - used - 1;

package/src/tui/components/welcome.ts

@@ -185,7 +185,17 @@ export function renderWelcome(d: WelcomeData): string[] {
   const useColor = d.color !== false;
 
   if (cols < 30) {
-    return [ `jeo v${d.version} · ${d.model}` ];
+    // Narrow-terminal one-line fallback — MUST itself be width-capped: an unbounded
+    // `jeo v{version} · {model}` overflows badly with a realistic provider-qualified
+    // model id (e.g. "antigravity/claude-sonnet-4-6 (antigravity)" overflows a 10-col
+    // terminal by 47 columns), which is exactly the box-border/wrap misalignment a
+    // real terminal-resize-down reproduces live. `cols - 1` (not `cols`) — same
+    // "leave the last column free" convention as the boxed banner below: a line
+    // truncated to EXACTLY `cols` is ambiguous to real terminals (a full-width row
+    // followed by this line's own trailing "\n" can double-advance a row via the
+    // pending-autowrap/explicit-LF ambiguity), which is a second, independent
+    // corruption vector reproduced live — not just a cosmetic nicety.
+    return [truncate(`jeo v${d.version} · ${d.model}`, Math.max(0, cols - 1))];
   }
 
   // The banner fills the full terminal width (gjc forge: flush with the input box and

package/src/tui/components/width.ts

@@ -58,6 +58,85 @@ export function charWidth(cp: number): number {
   }
   return 1;
 }
+const ZWJ = 0x200d;
+const VS15 = 0xfe0e; // variation selector: force TEXT (narrow) presentation
+const VS16 = 0xfe0f; // variation selector: force EMOJI (wide) presentation
+const FITZPATRICK_MIN = 0x1f3fb; // Emoji Modifier Fitzpatrick Type-1-2 .. Type-6
+const FITZPATRICK_MAX = 0x1f3ff;
+const KEYCAP_COMBINING = 0x20e3; // combining enclosing keycap (1️⃣, #️⃣, *️⃣)
+
+function isFitzpatrick(cp: number): boolean {
+  return cp >= FITZPATRICK_MIN && cp <= FITZPATRICK_MAX;
+}
+
+/** True for combining/zero-width marks that attach to a preceding base rather than
+ *  starting a new cluster on their own (diacritics etc.) — the zero-width branch of
+ *  `charWidth` MINUS variation selectors (VS15/VS16 are handled explicitly above,
+ *  since they change the CLUSTER's width rather than merely contributing 0 to it). */
+function isAttachableCombining(cp: number): boolean {
+  return (cp >= 0x0300 && cp <= 0x036f)
+    || (cp >= 0x1ab0 && cp <= 0x1aff)
+    || (cp >= 0x1dc0 && cp <= 0x1dff)
+    || (cp >= 0x20d0 && cp <= 0x20ff)
+    || cp === 0xfeff;
+}
+
+function codePointAndLength(s: string, i: number): { cp: number; length: number } {
+  const cp = s.codePointAt(i)!;
+  return { cp, length: cp > 0xffff ? 2 : 1 };
+}
+
+/**
+ * Resolve the visual CLUSTER starting at `s[i]` (not an SGR escape or tab — callers
+ * handle those separately) into its total consumed UTF-16 length and DISPLAY width,
+ * absorbing variation selectors, skin-tone modifiers, keycap combiners, combining
+ * marks, and ZWJ-joined sequences into ONE atomic unit (gjc parity: "preserve …
+ * Unicode grapheme semantics for … Korean tone marks, VS16 emoji presentation, ZWJ,
+ * keycaps, and emoji modifiers").
+ *
+ * Per-code-point summing (the old behavior) over- or under-counts every one of these:
+ * 👍🏽 (thumbs-up + Fitzpatrick modifier) summed to 4 columns where a terminal renders
+ * ONE 2-wide glyph; ❤️ (heart + VS16) summed to 1 where a terminal renders 2; a 4-person
+ * ZWJ family emoji summed to 8 where a terminal renders 2. Every one of those is a real,
+ * visible box-border/wrap misalignment ("깨짐") the instant such a sequence appears in a
+ * message — this collapses each sequence to the width a terminal ACTUALLY renders it at,
+ * atomically, so `truncateToWidth`/`wrapTextWithAnsi` also never split one in half at a
+ * boundary (this is a pragmatic subset of UAX #29 grapheme-cluster breaking scoped to
+ * the sequences a chat/coding TUI actually sees — not a general script-shaping engine).
+ */
+export function nextGraphemeCluster(s: string, i: number): { length: number; width: number } {
+  const base = codePointAndLength(s, i);
+  let width = charWidth(base.cp);
+  let len = base.length;
+  let j = i + base.length;
+  const peek = (): number => s.codePointAt(j) ?? -1;
+
+  if (peek() === VS15) { width = 1; len += 1; j += 1; }
+  else if (peek() === VS16) { width = 2; len += 1; j += 1; }
+
+  while (isFitzpatrick(peek())) {
+    const mod = codePointAndLength(s, j);
+    len += mod.length;
+    j += mod.length;
+    width = 2;
+  }
+
+  if (peek() === KEYCAP_COMBINING) { len += 1; j += 1; width = 2; }
+
+  while (isAttachableCombining(peek())) {
+    const mark = codePointAndLength(s, j);
+    len += mark.length;
+    j += mark.length;
+  }
+
+  if (peek() === ZWJ && j + 1 < s.length) {
+    const joined = nextGraphemeCluster(s, j + 1);
+    len += 1 + joined.length;
+    width = 2;
+  }
+
+  return { length: len, width };
+}
 
 /**
  * Visible display width of a string: SGR escapes count 0, tabs advance to the
@@ -81,9 +160,9 @@ export function visibleWidth(s: string): number {
       i += 1;
       continue;
     }
-    const cp = s.codePointAt(i)!;
-    w += charWidth(cp);
-    i += cp > 0xffff ? 2 : 1;
+    const cluster = nextGraphemeCluster(s, i);
+    w += cluster.width;
+    i += cluster.length;
   }
   return w;
 }
@@ -130,9 +209,9 @@ export function truncateToWidth(s: string, cols: number): string {
       cw = TAB_STOP - (w % TAB_STOP);
       chunk = "\t";
     } else {
-      const cp = s.codePointAt(i)!;
-      cw = charWidth(cp);
-      chunk = cp > 0xffff ? s.slice(i, i + 2) : s[i]!;
+      const cluster = nextGraphemeCluster(s, i);
+      cw = cluster.width;
+      chunk = s.slice(i, i + cluster.length);
     }
     if (w + cw > limit) break;
     out += chunk;

package/src/tui/renderer.ts

@@ -49,7 +49,29 @@ export class Renderer {
     const currentRows = size().rows;
     if ((this.prevCols !== undefined && this.prevCols !== currentCols) ||
         (this.prevRows !== undefined && this.prevRows !== currentRows)) {
-      this.clear();
+      if (this.reserve) {
+        // Inline/reserve mode: a resize needs a full repaint, but NOT an immediate
+        // clear() — clear() zeroes coverRows/prev to 0 as an independent write, which
+        // then fools the reserve block below (right after this) into believing NOTHING
+        // currently occupies the screen (occupied=0) — even though the old frame's rows
+        // are still physically there. With occupied wrongly 0, `next.length > occupied`
+        // spuriously trips even when the new (post-resize) frame is SHORTER than the
+        // old one, inserting real "\n" characters that ACTUALLY SCROLL the terminal —
+        // corrupting whatever sits above the live frame and permanently desyncing this
+        // renderer's row bookkeeping from reality (every later diff then paints at the
+        // wrong absolute row, producing progressively worse duplicate/torn content on
+        // each subsequent tick — reproduced deterministically with a standalone
+        // Renderer harness before this fix landed). reset() is the same self-heal path
+        // the periodic full-resync already uses: it remembers the old occupied rows via
+        // coverRows (no output), so the diff loop below EL-clears exactly the excess
+        // rows in place — no scroll, no desync.
+        this.reset();
+      } else {
+        // Non-reserve (alt-screen/pipe) mode has no reserve block to fool (gated on
+        // `this.reserve`), and the underlying screen buffer's own dimensions just
+        // changed — keep the defensive full ED clear.
+        this.clear();
+      }
     }
     this.prevCols = currentCols;
     this.prevRows = currentRows;