acuvo-code 0.5.1 → 0.5.2

package/ENTERPRISE.md

@@ -189,7 +189,7 @@ are the numbers to quote. Counting is the first thing a reviewer does.
 
 ⚠️ **This said "18 shipped files", then "41", then "90", then "101", then "108", and every
 one went stale in turn.** The package ships **120 files — 118 in `lib/`, 2 in
-`bin/` — about 78245 lines**, with **237 test files** beside them (counted 2026-08-22).
+`bin/` — about 78328 lines**, with **237 test files** beside them (counted 2026-08-22).
 
 ⭐ **AND THE 108 WENT STALE IN THE MOST INSTRUCTIVE WAY POSSIBLE: THREE OF THE FILES IT
 MISSED WERE REACHABLE FROM NOTHING.** `wiring-reach.test.mjs` was naming
@@ -203,7 +203,7 @@ exactly the kind of number this section warns about.
 allowlist also carries **`test/`, `ENTERPRISE.md` and `ROADMAP.md`**, and the published
 tarball is **265 files, 5.1 MB unpacked — 182 of them tests against 98 of `lib/`.** That is
 deliberate, not drift (commit `ed08f2710`, *"ship the tests, and add CI that would have
-caught the false green"*): a document that invites you to audit 76736 lines and then ships
+caught the false green"*): a document that invites you to audit 78328 lines and then ships
 you the source without the tests is asking to be taken on trust, which is the one thing this
 file refuses to ask for. ⭐ **Run them yourself: `npm test` inside the installed package.**
 The stale sentence is the more interesting failure — it under-claimed, so nobody would ever
@@ -892,8 +892,8 @@ For completeness, the properties none of them offers:
   (`lib/media.mjs`), and generates imagery with no configuration and no account
   (`lib/imagegen.mjs`) — critiqued before it is accepted, and reported as unreviewed when
   no critic is available.
-- ⭐ **Zero dependencies.** The entire auditable surface is 116 files and 76736 lines,
-  and there is no `node_modules` behind it. (Counted 2026-08-20 from
+- ⭐ **Zero dependencies.** The entire auditable surface is 120 files and 78328 lines,
+  and there is no `node_modules` behind it. (Counted 2026-08-22 from
   `lib/*.mjs` + `bin/*.mjs`; `test/docs-truth.test.mjs` fails the build if this number
   drifts, which is why it went 18 → 41 → 46 → 52 → 53 → 57 → 60 → 61 → 62 → 65 → 66 → 69 → 70 → 71 → 72 → 73 → 80 → 84 → 90 → 100 → 101 → 102 → 103 → 107 → 108 → 111 as modules landed (111 = the three that were WRITTEN and imported by nothing — `python.mjs`, `cache-floor.mjs`, `plan-coherence.mjs`; 108 = `warm-provider.mjs`, which keeps a session on the upstream that holds its prompt cache; 107 = `login.mjs`, the command that stores an Acuvo credential — until it existed, `writeAccount` was called by nothing and every user fell through to BYOK). ⚠️ Two of those three landed on this count while remaining UNREACHABLE, which is the sharpest illustration this document has that a file count is a claim about bytes, never about capability. ⭐ A
   count that fails the build is the only kind that stays true — this one has now caught its own

package/lib/chat.mjs

@@ -353,7 +353,14 @@ export async function runChat({
    * quits) has to arrive here too, or the escape hatch is a single-use one.
    */
   if (rl) rl.on('SIGINT', () => { onInterrupt(); });
-  if (banner) output.write(`${banner}\n`);
+  /**
+   * ⚠️⚠️ THE BANNER IS DEFERRED UNTIL AFTER THE PIN, AND THE ORDER IS NOT
+   * COSMETIC. `pinRegion` CLEARS the screen so the transcript starts at the top
+   * of a clean one — printed before that, the banner is erased by the very
+   * thing meant to sit beneath it, which is exactly what a screenshot showed:
+   * a banner cut in half with the conversation crammed at the bottom.
+   */
+  const writeBanner = () => { if (banner) output.write(`${banner}\n`); };
   // ⚠️ `/help` IS ADVERTISED IN THE ONE LINE EVERY SESSION PRINTS. A command
   // surface nobody is told about is the same defect item 14 closed for `--help`:
   // the feature worked and nothing a stranger would read mentioned it.
@@ -398,6 +405,13 @@ export async function runChat({
     process.once('SIGTERM', releasePin);
   }
 
+  /**
+   * ⭐ NOW the banner, at the top of a screen the pin has just cleared, with the
+   * conversation free to grow downward beneath it — which is the direction every
+   * scrollback in existence runs.
+   */
+  writeBanner();
+
   try {
     for (;;) {
       /**

package/lib/input-box.mjs

@@ -96,16 +96,30 @@ export function renderBox({ value = '', cursor = 0, columns = 80, prompt = '›
   const shown = value.slice(start, start + room);
 
   const body = `${prompt}${shown}`;
-  const pad = ' '.repeat(Math.max(0, inner - visibleWidth(body)));
+  const pad = ' '.repeat(Math.max(0, width - visibleWidth(body)));
 
+  /**
+   * ── ⚠️⚠️ A RULE AND A PROMPT — NOT A BOX. THE SCREENSHOT SETTLED IT ─────────
+   *
+   * I built a four-sided box because Roman said "copy Claude's box exactly", and
+   * a screenshot of the real thing shows there IS no box: a horizontal rule
+   * across the full width, then `❯ ` beneath it. The submitted line gets a
+   * subtle highlight bar rather than a border.
+   *
+   * ⭐ AND THE RULE IS WHY IT LOOKS SETTLED RATHER THAN DRAWN. Two borders and
+   * two side walls make the input an object floating in the terminal; one rule
+   * makes it the bottom of the page. Roman: *"ours is organised weirdly."*
+   *
+   * ⚠️ Two rows, not three — so the reserved region shrinks with it and the
+   * transcript gets a row back.
+   */
   return {
     lines: [
-      `╭${'─'.repeat(width - 2)}╮`,
-      `│${body}${pad}│`,
-      `╰${'─'.repeat(width - 2)}╯`,
+      '─'.repeat(width),
+      `${body}${pad}`,
     ],
-    // 1-based: the │, then the prompt, then however far into the shown text.
-    cursorColumn: 1 + 1 + promptWidth + (cursor - start),
+    // 1-based, and there is no left border to skip any more.
+    cursorColumn: 1 + promptWidth + (cursor - start),
   };
 }
 
@@ -274,10 +288,17 @@ export function paint(output, state, { first = false, atRow = 0 } = {}) {
    * viewport when the box is at the bottom of the screen, and every subsequent
    * `up` is then off by a row for the rest of the session.
    */
-  const home = first ? '' : `\r${CSI}1A`;
+  /**
+   * ⚠️ THE ROW MATH FOLLOWS THE ROW COUNT, and it changed when the box became a
+   * rule. With TWO rows the cursor already ends on the prompt line after the
+   * write, so there is no reposition to make — the old `ESC[1A` was correct for
+   * three rows and would now land on the RULE, one row too high, which is the
+   * same off-by-one that walked the box up the screen before.
+   */
+  const home = first ? '' : `\r${CSI}${lines.length - 1}A`;
   output.write(
     `${CSI}?25l${home}${CSI}0J${lines.join('\n')}` +
-    `${CSI}1A\r${CSI}${cursorColumn}G${CSI}?25h`,
+    `\r${CSI}${cursorColumn}G${CSI}?25h`,
   );
 }
 
@@ -409,7 +430,7 @@ export function readBoxedLine({ input, output, history = [], onInterrupt = null,
  * ⚠️ AND IT IS OPT-IN. A reserved region is a claim on somebody's whole screen;
  * off a TTY, in CI, under a pipe or with ACUVO_NO_PIN=1 it is never set.
  */
-export function pinRegion(output, { rows = 3, env = process.env } = {}) {
+export function pinRegion(output, { rows = 2, env = process.env } = {}) {
   const height = output?.rows ?? process.stdout?.rows ?? 0;
   const enabled = Boolean(output?.isTTY)
     && height > rows + 4
@@ -422,12 +443,21 @@ export function pinRegion(output, { rows = 3, env = process.env } = {}) {
   let released = false;
 
   /**
-   * ⚠️ THE CURSOR IS PARKED INSIDE THE SCROLL REGION BEFORE ANYTHING PRINTS.
-   * Setting a region moves the cursor to home (1,1) on most terminals, so
-   * without this the next line of output lands at the TOP of the screen and the
-   * transcript reads backwards.
+   * ── ⚠️⚠️ CLEAR, THEN START AT THE TOP. MY FIRST VERSION STARTED AT THE BOTTOM ─
+   *
+   * Roman, from a screenshot: the banner was cut in half with a huge empty gap
+   * beneath it and the conversation crammed at the bottom of the screen.
+   *
+   * The cause: this parked the cursor at the BOTTOM of the region, so the first
+   * line printed on the last usable row and everything after it scrolled. A
+   * terminal fills downward — the transcript has to START at the top and grow
+   * toward the input, which is what every scrollback in existence does.
+   *
+   * ⚠️ AND THE SCREEN IS CLEARED FIRST. Whatever the shell left behind would
+   * otherwise sit inside our region and scroll along with the session, so the
+   * banner would never be at the top of anything.
    */
-  output.write(`${CSI}1;${bottom}r${CSI}${bottom};1H`);
+  output.write(`${CSI}2J${CSI}1;${bottom}r${CSI}1;1H`);
 
   const release = () => {
     if (released) return;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "acuvo-code",
-  "version": "0.5.1",
+  "version": "0.5.2",
   "description": "Acuvo Code — the terminal client for the Acuvo capability registry. Zero dependencies, by design.",
   "type": "module",
   "bin": {