@aragon-agent/cli 0.6.42 → 0.6.44

package/dist/ui/scrollback/budget.js

@@ -12,15 +12,20 @@
  * and every row it did not ask for became `gap` - blank rows ABOVE the content, which
  * is what the user reported as "the app starts halfway down the screen" and as "a big
  * blank between the result and the running card". The band now takes the whole pool
- * (`fill`), so the region is `[header][band][composer][status]` top to bottom and
+ * (`fill`), so the region is `[band][composer][identity][status]` top to bottom and
  * `gap` cannot exist: `resolveCanvasLayout` is given `frameRows === capacity` and
  * derives `gap = 0` (see the spec's §5.5 proof, which is why the writer needs no
  * change at all).
  *
  * The composer, popup and status rows come from the SAME `buildFrameBudget` the
  * full-screen layout uses, so the two modes cannot disagree about how tall the
- * editor is. What differs is the top: the header is a real slot here (D3), and the
- * row it occupies is spent from the region, not from the printed transcript.
+ * editor is. What differs is the top: the identity row is a real slot here (D3), and
+ * the row it occupies is spent from the region, not from the printed transcript.
+ * THE COUNT IS ALL THIS MODULE OWNS, NOT THE POSITION: since
+ * `tui-header-leaks-into-scrollback` the identity row is drawn between the composer and
+ * the status group (`ScrollbackShell.tsx`), because region row 0 is necessarily the
+ * successor of the newest printed row and chrome there lands inside the conversation.
+ * Moving it changed no number below: it is still 1 row, still taken out of `remaining`.
  *
  * THIS IS THE ONLY CALL SITE OF `buildLiveBand` (I-8). `remaining` is computed here
  * once and handed to the band; an `App` that computed its own copy would make
@@ -56,9 +61,11 @@ export function buildScrollbackBudget(input) {
     }
     // D1 · H = C. `frameRows` is `rows - 1` by construction (`layout/budget.ts`), so the
     // region ends exactly on the row above the writer's parked cursor.
+    // The identity row is drawn at the BOTTOM now; it is still one row and still deducted
+    // here, which is why `liveRows`, `bandRows` and `previewRows` did not move with it.
     const headerRows = 1;
     const liveRows = Math.max(1, base.frameRows);
-    // The whole pool: everything between the header and the status line. Two independent
+    // The whole pool: everything above the composer slot. Two independent
     // derivations put its floor at 1, so `max(0, ...)` is defensive only:
     //  1. `composerSlotRows = 2 + clampDraftRows(rows, draftRows)` and
     //     `draftMaxRows(rows) = max(1, min(6, floor(rows / 4)))`, so on the narrowest

package/dist/ui/scrollback/tail-anchor.d.ts

@@ -7,7 +7,9 @@
  * `justifyContent="flex-end"` therefore pushed those four rows against the composer and
  * left every unused row ABOVE the conversation - the "the first reply starts at the
  * bottom of the screen" report. The answer is conditional anchoring: top while the
- * content fits, so the conversation is written downwards from under the header.
+ * content fits, so the conversation is written downwards from the region's top row
+ * (`tui-header-leaks-into-scrollback` took the identity row off that row and put it
+ * below the composer, so the first line of the band is now the first line of the screen).
  *
  * WHY THE FALLBACK IS `bottom` AND NOT THE OTHER WAY ROUND. `flex-start` inside an
  * `overflow="hidden"` box clips the NEWEST rows (Ink's clip rectangle is the box's
@@ -26,7 +28,8 @@
  * parameters and a unit test can drive it with any table it likes.
  */
 import type { Entry } from '../../agent/reducer.js';
-/** `top` = content grows down from the header; `bottom` = newest row hugs the composer. */
+/** `top` = content grows down from the region's top row; `bottom` = newest row hugs the
+ *  composer. */
 export type TailAnchor = 'top' | 'bottom';
 /**
  * Which alignment the live tail should use for the entries it is about to render.

package/dist/ui/scrollback/tail-anchor.js

@@ -7,7 +7,9 @@
  * `justifyContent="flex-end"` therefore pushed those four rows against the composer and
  * left every unused row ABOVE the conversation - the "the first reply starts at the
  * bottom of the screen" report. The answer is conditional anchoring: top while the
- * content fits, so the conversation is written downwards from under the header.
+ * content fits, so the conversation is written downwards from the region's top row
+ * (`tui-header-leaks-into-scrollback` took the identity row off that row and put it
+ * below the composer, so the first line of the band is now the first line of the screen).
  *
  * WHY THE FALLBACK IS `bottom` AND NOT THE OTHER WAY ROUND. `flex-start` inside an
  * `overflow="hidden"` box clips the NEWEST rows (Ink's clip rectangle is the box's

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aragon-agent/cli",
-  "version": "0.6.42",
+  "version": "0.6.44",
   "description": "AragonAgent CLI — a Claude-Code / Codex-style interactive terminal UI (TUI) on top of the @aragon-agent/core engine. Installable and runnable via npm / npx.",
   "license": "MIT",
   "author": "AragonAgent contributors",
@@ -56,7 +56,7 @@
     "prepublishOnly": "npm run build"
   },
   "dependencies": {
-    "@aragon-agent/core": "^0.2.54",
+    "@aragon-agent/core": "^0.2.56",
     "chalk": "^5.6.2",
     "cli-highlight": "^2.0.0",
     "commander": "^12.1.0",