@modelstatus/cli 0.1.56 → 0.1.58

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@modelstatus/cli",
-  "version": "0.1.56",
+  "version": "0.1.58",
   "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

@@ -44,13 +44,14 @@ const CHROME_ROWS = 10;
 // the frame, NEGATIVE grows it past the reported height.
 //  - 1 everywhere: a full-height ink frame write+newlines its bottom line and
 //    scrolls the buffer up 1/render; the 1-row reserve keeps the last line blank.
-//  - -7 in Warp: empirically (the user dialing it live in their Warp), the frame
-//    must be GROWN ~7 rows past stdout.rows or the top clips — Warp's block model
-//    reports/handles the alt-screen height such that a flush-height frame rides too
-//    high. So in Warp we render TALLER, which pushes the window down into view.
-//    Gated on Warp (a negative reserve elsewhere would over-grow + clip the top of
-//    a normal full-screen terminal).
-const WARP_RESERVE = -7;
+//  - -3 in Warp: Warp under-reports the alt-screen height — its TRUE full-screen
+//    viewport is stdout.rows + 3, so the frame must be exactly that tall to fill it
+//    without clipping. DERIVED from two clean (no-poll) data points in the user's
+//    Warp: reserve -7 clipped 4 rows off the top, -11 clipped 8 (clip = -reserve-3),
+//    so clip hits 0 at reserve = -3. A taller frame (more negative) OVER-grows and
+//    scrolls the top — incl. the tab-strip nav — off the alt screen (unrecoverable;
+//    no scrollback). Gated on Warp (this offset is Warp-specific).
+const WARP_RESERVE = -3;
 
 /** True when running under Warp (TERM_PROGRAM=WarpTerminal, or any WARP_* env, or
  * TERM_PROGRAM merely containing "warp" — broad so detection doesn't silently