…ion from #3860

PR #3860 upgraded ink 6.2.3 → 7.0.2 with the claim of "no business code
changes." In production this turns out to break the TUI:

- After `/clear`, the next user message and AI response do not render
  to the static history area — only the dynamic spinner/input area is
  visible (#3860 + chore/upgrade-ink-7 branch reproduce this).
- After Ctrl+O (TOGGLE_COMPACT_MODE), the screen is cleared and stays
  blank.
- Any `refreshStatic()` call path (auth refresh, model change, render-
  mode switch, /clear, Ctrl+O) puts the UI into the same "muted" state.

Root cause is an ink 7 regression: when `<Static>` is remounted by
changing its `key` prop, the new instance's items are never written to
stdout. A 30-line minimal repro (pure ink + Static + key++) confirms
this independently of qwen-code.

Closest upstream issue: vadimdemedes/ink#773
(useLayoutEffect-driven child stripping in <Static>). PR #905
("Fix dangling staticNode reference") merged into ink 7 fixed the
unmount-OOM path but not this remount path. No upstream issue yet
matches the "remount loses content" case — we should file one and
ship a re-upgrade once it is resolved.

Scope of this revert (intentional partial revert of #3860):

- ink ^7.0.2 → ^6.2.3 (cli + root hoist)
- react / react-dom 19.2.4 pin → ^19.1.0 (cli direct, root overrides
  removed)
- wrap-ansi ^10.0.0 → 9.0.2 (cli direct, root override restored)
- react-devtools-core kept at ^6.1.5 (still ink-6 compatible — ink
  6.8.0's peerOptional requires >=6.1.2; downgrading to 4.x would
  re-introduce a conflict)
- @vitest/eslint-plugin pin "1.3.4" → "^1.3.4"
- "@types/node" override removed (was only needed for ink 7's Node 22
  type drift)

What this revert keeps:

- Node engines >=22 across root / cli / core / sdk / web-templates and
  the matching Dockerfile / .nvmrc / CI matrix work. PR #1876 followed
  up by adding Node 24 support to the matrix, and rolling those back
  would conflict with that work. The visible bug is the ink runtime
  regression, not the engine bump.
- doctorChecks.ts MIN_NODE_MAJOR = 22 (matches engines).
- The test gating that #3860 added for ink-7 input throttle (AuthDialog
  / AskUserQuestionDialog / InputPrompt). With ink 6 these tests would
  pass un-gated, but leaving the gate in place is harmless and a
  follow-up can un-gate them. Keeping this revert minimal.

Verification (local, ink 6.8.0 single instance):

- npm ls ink → single ink@6.8.0
- npm ls react → single react@19.2.4 (kept by vscode-ide-companion
  workspace pin; ink 6 is fine on 19.2)
- npm run typecheck --workspace=packages/cli → clean
- AppContainer.test.tsx 61/61 pass
- MainContent.test.tsx 6/6 pass
- clearCommand.test.ts 13/13 pass

Re-upgrade path: once ink ships a fix for the Static-remount
regression, redo this upgrade behind the feat/virtual-viewport-on-ink7
branch where the `<Static>` + clearTerminal combo is replaced by an
overflowY=hidden self-managed viewport.

Generated with AI

Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>

…n from #3860 (#4083)

* revert(deps): downgrade ink 7.0.2 → 6.x to fix Static-remount regression from #3860

PR #3860 upgraded ink 6.2.3 → 7.0.2 with the claim of "no business code
changes." In production this turns out to break the TUI:

- After `/clear`, the next user message and AI response do not render
  to the static history area — only the dynamic spinner/input area is
  visible (#3860 + chore/upgrade-ink-7 branch reproduce this).
- After Ctrl+O (TOGGLE_COMPACT_MODE), the screen is cleared and stays
  blank.
- Any `refreshStatic()` call path (auth refresh, model change, render-
  mode switch, /clear, Ctrl+O) puts the UI into the same "muted" state.

Root cause is an ink 7 regression: when `<Static>` is remounted by
changing its `key` prop, the new instance's items are never written to
stdout. A 30-line minimal repro (pure ink + Static + key++) confirms
this independently of qwen-code.

Closest upstream issue: vadimdemedes/ink#773
(useLayoutEffect-driven child stripping in <Static>). PR #905
("Fix dangling staticNode reference") merged into ink 7 fixed the
unmount-OOM path but not this remount path. No upstream issue yet
matches the "remount loses content" case — we should file one and
ship a re-upgrade once it is resolved.

Scope of this revert (intentional partial revert of #3860):

- ink ^7.0.2 → ^6.2.3 (cli + root hoist)
- react / react-dom 19.2.4 pin → ^19.1.0 (cli direct, root overrides
  removed)
- wrap-ansi ^10.0.0 → 9.0.2 (cli direct, root override restored)
- react-devtools-core kept at ^6.1.5 (still ink-6 compatible — ink
  6.8.0's peerOptional requires >=6.1.2; downgrading to 4.x would
  re-introduce a conflict)
- @vitest/eslint-plugin pin "1.3.4" → "^1.3.4"
- "@types/node" override removed (was only needed for ink 7's Node 22
  type drift)

What this revert keeps:

- Node engines >=22 across root / cli / core / sdk / web-templates and
  the matching Dockerfile / .nvmrc / CI matrix work. PR #1876 followed
  up by adding Node 24 support to the matrix, and rolling those back
  would conflict with that work. The visible bug is the ink runtime
  regression, not the engine bump.
- doctorChecks.ts MIN_NODE_MAJOR = 22 (matches engines).
- The test gating that #3860 added for ink-7 input throttle (AuthDialog
  / AskUserQuestionDialog / InputPrompt). With ink 6 these tests would
  pass un-gated, but leaving the gate in place is harmless and a
  follow-up can un-gate them. Keeping this revert minimal.

Verification (local, ink 6.8.0 single instance):

- npm ls ink → single ink@6.8.0
- npm ls react → single react@19.2.4 (kept by vscode-ide-companion
  workspace pin; ink 6 is fine on 19.2)
- npm run typecheck --workspace=packages/cli → clean
- AppContainer.test.tsx 61/61 pass
- MainContent.test.tsx 6/6 pass
- clearCommand.test.ts 13/13 pass

Re-upgrade path: once ink ships a fix for the Static-remount
regression, redo this upgrade behind the feat/virtual-viewport-on-ink7
branch where the `<Static>` + clearTerminal combo is replaced by an
overflowY=hidden self-managed viewport.

Generated with AI

Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>

* ci(fix): keep wrap-ansi 10 + skip 1 ink-7-specific TableRenderer test

The initial revert downgraded wrap-ansi to 9.0.2 (the pre-PR-#3860
state). After rebasing onto current main, PR #4050 (preserve table
ANSI color across wrapped lines) brought in a new test
("does not preserve foreground after an explicit foreground reset")
whose wrap point depends on ink 7's <Text> wrapping behavior.

Two-part fix:

1. Restore wrap-ansi to 10 (cli direct dep). The wrap-ansi version is
   independent of the ink regression we're reverting — wrap-ansi 10
   has no peer-dep tie to ink 7 — and #4050's TableRenderer code on
   main already assumes wrap-ansi 10. Keeping the wrap-ansi bump
   removes the root override for wrap-ansi (was forcing all transitives
   to 9.0.2) so cli's TableRenderer gets the wrap-ansi 10 it expects,
   while ink 6's transitive wrap-ansi naturally resolves to 9 (its own
   declared range) — no conflict.

2. Skip the one new test that asserts a specific wrap position. The
   other assertions in that test (foreground cleared, equal visible
   widths) still pass on ink 6 — only `expectWrappedContinuation` is
   ink-7-specific. The sibling test 'does not preserve foreground
   after an explicit reset' (using \\u001b[0m instead of \\u001b[39m)
   still passes unmodified on ink 6, so the ANSI-handling logic itself
   is verified end-to-end. The TODO marker references the re-upgrade
   path.

Local verification:

- TableRenderer.test.tsx: 54/54 pass + 1 skipped
- AppContainer.test.tsx: 61/61 pass
- MainContent.test.tsx: 6/6 pass
- clearCommand.test.ts: 13/13 pass
- npm run typecheck --workspace=packages/cli: clean
- npm ls ink → single ink@6.8.0
- npm ls wrap-ansi → cli direct: 10.0.0; ink 6 transitive: 9.0.2
  (no conflict, no override)

Generated with AI

Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>

---------

Co-authored-by: 秦奇 <gary.gq@alibaba-inc.com>
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>

Signed-off-by: Salman Muin Kayser Chishti <13schishti@gmail.com>

Signed-off-by: Salman Muin Kayser Chishti <13schishti@gmail.com>

…n from #3860 (#4083)

* revert(deps): downgrade ink 7.0.2 → 6.x to fix Static-remount regression from #3860

PR #3860 upgraded ink 6.2.3 → 7.0.2 with the claim of "no business code
changes." In production this turns out to break the TUI:

- After `/clear`, the next user message and AI response do not render
  to the static history area — only the dynamic spinner/input area is
  visible (#3860 + chore/upgrade-ink-7 branch reproduce this).
- After Ctrl+O (TOGGLE_COMPACT_MODE), the screen is cleared and stays
  blank.
- Any `refreshStatic()` call path (auth refresh, model change, render-
  mode switch, /clear, Ctrl+O) puts the UI into the same "muted" state.

Root cause is an ink 7 regression: when `<Static>` is remounted by
changing its `key` prop, the new instance's items are never written to
stdout. A 30-line minimal repro (pure ink + Static + key++) confirms
this independently of qwen-code.

Closest upstream issue: vadimdemedes/ink#773
(useLayoutEffect-driven child stripping in <Static>). PR #905
("Fix dangling staticNode reference") merged into ink 7 fixed the
unmount-OOM path but not this remount path. No upstream issue yet
matches the "remount loses content" case — we should file one and
ship a re-upgrade once it is resolved.

Scope of this revert (intentional partial revert of #3860):

- ink ^7.0.2 → ^6.2.3 (cli + root hoist)
- react / react-dom 19.2.4 pin → ^19.1.0 (cli direct, root overrides
  removed)
- wrap-ansi ^10.0.0 → 9.0.2 (cli direct, root override restored)
- react-devtools-core kept at ^6.1.5 (still ink-6 compatible — ink
  6.8.0's peerOptional requires >=6.1.2; downgrading to 4.x would
  re-introduce a conflict)
- @vitest/eslint-plugin pin "1.3.4" → "^1.3.4"
- "@types/node" override removed (was only needed for ink 7's Node 22
  type drift)

What this revert keeps:

- Node engines >=22 across root / cli / core / sdk / web-templates and
  the matching Dockerfile / .nvmrc / CI matrix work. PR #1876 followed
  up by adding Node 24 support to the matrix, and rolling those back
  would conflict with that work. The visible bug is the ink runtime
  regression, not the engine bump.
- doctorChecks.ts MIN_NODE_MAJOR = 22 (matches engines).
- The test gating that #3860 added for ink-7 input throttle (AuthDialog
  / AskUserQuestionDialog / InputPrompt). With ink 6 these tests would
  pass un-gated, but leaving the gate in place is harmless and a
  follow-up can un-gate them. Keeping this revert minimal.

Verification (local, ink 6.8.0 single instance):

- npm ls ink → single ink@6.8.0
- npm ls react → single react@19.2.4 (kept by vscode-ide-companion
  workspace pin; ink 6 is fine on 19.2)
- npm run typecheck --workspace=packages/cli → clean
- AppContainer.test.tsx 61/61 pass
- MainContent.test.tsx 6/6 pass
- clearCommand.test.ts 13/13 pass

Re-upgrade path: once ink ships a fix for the Static-remount
regression, redo this upgrade behind the feat/virtual-viewport-on-ink7
branch where the `<Static>` + clearTerminal combo is replaced by an
overflowY=hidden self-managed viewport.

Generated with AI

Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>

* ci(fix): keep wrap-ansi 10 + skip 1 ink-7-specific TableRenderer test

The initial revert downgraded wrap-ansi to 9.0.2 (the pre-PR-#3860
state). After rebasing onto current main, PR #4050 (preserve table
ANSI color across wrapped lines) brought in a new test
("does not preserve foreground after an explicit foreground reset")
whose wrap point depends on ink 7's <Text> wrapping behavior.

Two-part fix:

1. Restore wrap-ansi to 10 (cli direct dep). The wrap-ansi version is
   independent of the ink regression we're reverting — wrap-ansi 10
   has no peer-dep tie to ink 7 — and #4050's TableRenderer code on
   main already assumes wrap-ansi 10. Keeping the wrap-ansi bump
   removes the root override for wrap-ansi (was forcing all transitives
   to 9.0.2) so cli's TableRenderer gets the wrap-ansi 10 it expects,
   while ink 6's transitive wrap-ansi naturally resolves to 9 (its own
   declared range) — no conflict.

2. Skip the one new test that asserts a specific wrap position. The
   other assertions in that test (foreground cleared, equal visible
   widths) still pass on ink 6 — only `expectWrappedContinuation` is
   ink-7-specific. The sibling test 'does not preserve foreground
   after an explicit reset' (using \\u001b[0m instead of \\u001b[39m)
   still passes unmodified on ink 6, so the ANSI-handling logic itself
   is verified end-to-end. The TODO marker references the re-upgrade
   path.

Local verification:

- TableRenderer.test.tsx: 54/54 pass + 1 skipped
- AppContainer.test.tsx: 61/61 pass
- MainContent.test.tsx: 6/6 pass
- clearCommand.test.ts: 13/13 pass
- npm run typecheck --workspace=packages/cli: clean
- npm ls ink → single ink@6.8.0
- npm ls wrap-ansi → cli direct: 10.0.0; ink 6 transitive: 9.0.2
  (no conflict, no override)

Generated with AI

Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>

---------

Co-authored-by: 秦奇 <gary.gq@alibaba-inc.com>
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>