@modelstatus/cli 0.1.55 → 0.1.56

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@modelstatus/cli",
-  "version": "0.1.55",
+  "version": "0.1.56",
   "description": "Track which AI models you use, where, and never get surprised by a retirement. Free offline model-health for any repo (mm status), browser sign-in for cloud inventory + alerts.",
   "keywords": [
     "llm",

package/src/tui/app.js

@@ -88,22 +88,19 @@ function useTermDims() {
   const [dims, setDims] = React.useState({ cols: (stdout && stdout.columns) || 80, rows: (stdout && stdout.rows) || 24 });
   React.useEffect(() => {
     if (!stdout) return undefined;
-    // Functional update that returns the SAME object when nothing changed, so a
-    // re-measure that finds identical dims doesn't trigger a needless re-render.
+    // Re-measure ONLY on a genuine resize event — NEVER poll with timers.
+    // ROOT CAUSE of the Warp clip: process.stdout.rows changes a beat AFTER the
+    // alt-screen transition settles, and a re-render with those changed dims
+    // SCROLLS the window's top (the header) off-screen in Warp. The dims read at
+    // mount render correctly; a "more accurate" later value is actually worse. So
+    // we keep the mount-time dims and only react to real resizes (functional
+    // update returns the SAME object when nothing changed → no needless render).
     const on = () => setDims((prev) => {
       const cols = stdout.columns || 80, rows = stdout.rows || 24;
       return prev.cols === cols && prev.rows === rows ? prev : { cols, rows };
     });
     stdout.on("resize", on);
-    // Re-measure a few beats after mount. When the TUI REMOUNTS right after the
-    // game leaves the alternate screen, some terminals (notably Warp's block
-    // model) re-flow the viewport a moment LATER and report stdout.{columns,rows}
-    // stale at mount-time — so the first frame is too SHORT and Ink falls back to
-    // cursor-up diffing, which drifts/scrolls the window off the top (and Ctrl-L
-    // can't fix it because it redraws at the same wrong height). These one-shot
-    // re-reads pick up the settled size and snap the window back to full screen.
-    const timers = [60, 250, 600, 1200].map((ms) => setTimeout(on, ms));
-    return () => { stdout.off("resize", on); timers.forEach(clearTimeout); };
+    return () => { stdout.off("resize", on); };
   }, [stdout]);
   const fw = Number(process.env.MM_TUI_WIDTH);
   const fh = Number(process.env.MM_TUI_HEIGHT);

package/src/tui/game/launch.js

@@ -83,13 +83,13 @@ export async function playGameInTui({ dir, width, height, initialView = "scan",
     // remounted tree fills the whole terminal from the top (same as Ctrl-L).
     // RECYCLE Warp's alt screen (leave + re-enter) to force it back into clean
     // full-screen mode — Warp drops that presentation during the game round-trip
-    // and its block header otherwise bleeds over the top rows. Then PAUSE before
-    // remounting: Warp reports its stable full-screen height a beat AFTER the
-    // ?1049h transition, so rendering immediately measures a transient (too-tall)
-    // size and clips a few rows off the top. The settle lets the height stabilize
-    // first; useTermDims also re-measures post-mount as a backstop.
+    // and its block header otherwise bleeds over the top rows. Then remount RIGHT
+    // AWAY (just a tick to flush the write): this reads the dims at mount the same
+    // way a FRESH launch does — those render perfectly. Do NOT wait for Warp to
+    // "settle" its reported height; the settled value is the one that clips (see
+    // useTermDims — we no longer poll for it).
     try { process.stdout.write("\x1b[?1049l\x1b[?1049h\x1b[2J\x1b[H"); } catch { /* ignore */ }
-    await new Promise((r) => setTimeout(r, 200));
+    await new Promise((r) => setImmediate(r));
     appController.remount({ initialView, fresh: false });
   } catch (e) {
     if (onError) onError(e); else throw e;