zames_pro 2.67.2 → 2.67.4

package/CHANGELOG.md

@@ -7,6 +7,27 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.67.4] - 2026-10-08
+
+### Fixed
+
+- **readme:** `npm run build:readme` generated a `README.ru.md` again even
+  though it is no longer published (removed from `files[]` in 2.67.1) and a
+  test asserted it must not exist — so a local build wrote an untracked file
+  and could trip the drift test. The generator now writes ONLY `README.md`.
+
+## [2.67.3] - 2026-10-08
+
+### Fixed
+
+- **input:** a terminal resize no longer clears the whole viewport. The
+  2.67.2 fix removed the duplicate footer by clearing the screen (`ESC[2J`),
+  but that pushed the history above into the scrollback and left a blank gap
+  between the input line and the text the operator was reading. The block is
+  now erased with a RELATIVE move (the cursor row within the block), which
+  lands on the block top row after a reflow and clears ONLY our own rows —
+  the history above stays visible and in place.
+
 ## [2.67.2] - 2026-10-08
 
 ### Fixed

package/dist/input.js

@@ -681,25 +681,25 @@ export class LineEditor {
     }
     _writeBlock() {
         const cols = process.stdout.columns || 80;
-        // After a resize the relative erase is unreliable (the terminal
-        // re-flowed everything and the cursor row changed). Re-DRAW the block
-        // from a known position instead: clear the visible viewport, go HOME,
-        // fill it with blank lines, then draw at the bottom. ESC[2J clears the
-        // SCREEN, not the scrollback, so the history above is preserved.
+        // After a resize the terminal re-flowed the lines above the block, so
+        // the block's ABSOLUTE row changed. But the cursor is still on the input
+        // line and `_eraseBlock` moves up by the cursor row WITHIN the block — a
+        // RELATIVE move that still lands on the block top row, whatever the
+        // reflow did. So we clear ONLY our own block (status + input) and leave
+        // the history above it visible and in place. We deliberately do NOT clear
+        // the whole viewport (ESC[2J): that pushed the history into the scrollback
+        // and left a blank gap between the footer and the text the operator was
+        // reading (they had to scroll up to see their own chat). `_blockRows` is
+        // kept so the shrink-padding (`_padShrink`) can still push a shorter block
+        // back down to the bottom.
         if (this._resizeRepin) {
             this._resizeRepin = false;
             this._eraseBlock();
             this._lastStatusBlock = '';
+            // Forget the old block height: after a reflow the shrink-padding must
+            // not add scroll (it would push the freshly drawn block up and open a
+            // gap above the footer). The normal path records the new height.
             this._blockRows = 0;
-            // Clear the VISIBLE viewport before re-pinning. After a resize the
-            // terminal re-flowed the lines above the block, and padding to the
-            // bottom scrolls the OLD copy of the block back into view — without the
-            // clear the old status/input stays on screen as a DUPLICATE of the
-            // freshly drawn one (the artifact seen on resize). The scrollback buffer
-            // is untouched: ESC[2J clears the screen, NOT the scrollback, so the
-            // history printed above is still reachable by scrolling up.
-            process.stdout.write(ESC + '[2J' + ESC + '[H');
-            this._padToBottom();
         }
         // Status line above the input: the spinner/answer text on the left and the
         // token context right-aligned on the SAME row (10k · 12%). The context is

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zames_pro",
-  "version": "2.67.2",
+  "version": "2.67.4",
   "description": "Terminal coding agent that drives chat.deepseek.com through Playwright — no API key required. Reads and edits files, runs commands, commits to git, like Claude Code / Codex CLI.",
   "type": "module",
   "bin": {

package/scripts/build-readme.mts

@@ -1,22 +1,21 @@
-// Assemble README.md and README.ru.md from two language sources.
+// Assemble README.md from the two language sources.
 //
 // Why: npm renders exactly ONE readme per package (README.md in the root) and
-// has no language tabs, so a separate README.ru.md is invisible on the npm
-// page. But npm renders the readme with GitHub Flavored Markdown (via
-// GitHub's API), so a <details> block DOES work there -- and on GitHub too.
-// We therefore keep the English text on top and fold the other language into
-// a collapsible block at the bottom. README.ru.md is generated too so the
-// GitHub switcher can point at it directly, but it is NOT published to npm
-// (see "files" in package.json):
-// it would just duplicate the folded block.
+// has no language tabs. npm renders the readme with GitHub Flavored Markdown
+// (via GitHub's API), so a <details> block DOES work there -- and on GitHub
+// too. We keep the English text on top and fold the Russian translation into
+// a collapsible block at the bottom. The language switcher is an in-page
+// `#readme-ru` anchor, so one README.md serves both languages -- there is
+// no separate README.ru.md anymore (it was invisible on npm and just
+// duplicated the folded block).
 //
 // The two sources (docs/readme.en.md, docs/readme.ru.md) are the single point
 // of edit for each language; this script wires the switcher and the collapsible
-// cross-language block so neither README has to be maintained by hand. The
-// generated files are committed; test/readme-built.test.ts re-runs buildReadmes()
-// and fails if they drift from the sources.
+// cross-language block so neither language has to be maintained by hand. The
+// generated file is committed; test/readme-built.test.ts re-runs buildReadmes()
+// and fails if it drifts from the sources.
 //
-// Usage:  npm run build:readme
+// Usage:  npom run build:readme
 
 import fs from 'node:fs'
 import path from 'node:path'
@@ -70,19 +69,14 @@ function details(summary: string, body: string): string {
   ].join(NL)
 }
 
-// Returns the two generated readmes WITHOUT touching the disk, so a test can
-// compare them against the committed files. Both files carry the SAME content
-// (English on top, Russian folded): README.md is what npm publishes, and
-// README.ru.md exists only so the GitHub language switcher has a target. The
-// switcher is an IN-PAGE `#readme-ru` anchor, so it works from either file
-// without fetching the other one.
-export function buildReadmes(rootDir: string): {
-  readmeEn: string
-  readmeRu: string
-} {
+// Returns the generated README.md WITHOUT touching the disk, so a test can
+// compare it against the committed file. Only README.md is generated: the
+// Russian translation lives inside it as a <details> block, and the switcher
+// is an in-page `#readme-ru` anchor.
+export function buildReadmes(rootDir: string): { readmeEn: string } {
   const en = readSource(rootDir, 'readme.en.md')
   const ru = readSource(rootDir, 'readme.ru.md')
-  const doc = [
+  const readmeEn = [
     en.head,
     '',
     EN_SWITCH,
@@ -93,7 +87,7 @@ export function buildReadmes(rootDir: string): {
     details('🇷🇺 Читать по-русски (Russian)', ru.body),
     '',
   ].join(NL)
-  return { readmeEn: doc, readmeRu: doc }
+  return { readmeEn }
 }
 
 // Run only when invoked directly (not when imported by a test).
@@ -101,8 +95,7 @@ const invoked =
   process.argv[1] &&
   path.resolve(process.argv[1]) === fileURLToPath(import.meta.url)
 if (invoked) {
-  const { readmeEn, readmeRu } = buildReadmes(root)
+  const { readmeEn } = buildReadmes(root)
   fs.writeFileSync(path.join(root, 'README.md'), readmeEn)
-  fs.writeFileSync(path.join(root, 'README.ru.md'), readmeRu)
-  console.log('build-readme: wrote README.md and README.ru.md')
+  console.log('build-readme: wrote README.md')
 }