acuvo-code 0.6.7 → 0.6.8

package/lib/input-box.mjs

@@ -516,7 +516,7 @@ export function pinRegion(output, { rows = 2, env = process.env } = {}) {
    */
   const enabled = Boolean(output?.isTTY)
     && height > rows + 4
-    && String(env.ACUVO_PIN ?? '') === '1'
+    && String(env.ACUVO_NO_PIN ?? '') !== '1'
     && String(env.CI ?? '').toLowerCase() !== 'true';
 
   if (!enabled) return { enabled: false, release() {}, rows: 0, bottom: 0 };
@@ -525,66 +525,56 @@ export function pinRegion(output, { rows = 2, env = process.env } = {}) {
   let released = false;
 
   /**
-   * ── ⚠️⚠️ CLEAR, THEN START AT THE TOP. MY FIRST VERSION STARTED AT THE BOTTOM ─
+   * ── ⭐⭐⭐ RESERVE THE ROWS. DO NOT CLEAR THE SCREEN. ────────────────────────
    *
-   * 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 CLEAR WAS THE ENTIRE BUG, THROUGH FOUR ATTEMPTS. Every previous
+   * version began `ESC[H ESC[2J ESC[3J` — home, erase screen, erase scrollback.
+   * That is what `clear` emits, and it is completely wrong here for two reasons
+   * that took far too long to separate:
    *
-   * 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.
+   *   1. It runs AFTER the banner has been printed, so it erases the thing the
+   *      user just saw. Roman: "I see the green logo and text for a fraction of
+   *      a second then I just see the prompt box, nothing else."
+   *   2. `3J` deletes the SCROLLBACK — the user's shell history, and then their
+   *      own session. "Can't scroll up or it's just not there." A CLI has no
+   *      business destroying the buffer it was launched into.
    *
-   * ⚠️ 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.
-   */
-  /**
-   * ⚠️⚠️ `3J` BEFORE `2J`, AND WITHOUT IT THE PROMPT IS OFF-SCREEN. Roman:
-   * *"when you type acuvo you have to scroll down to see the prompt area."*
-   *
-   * `ESC[2J` clears the visible screen but PUSHES what was there into
-   * SCROLLBACK — so VS Code (and most terminals) leave the viewport parked up
-   * in the history, showing the old shell output with our banner and prompt
-   * below the fold. The user has to scroll to find the thing they just started.
-   *
-   * `ESC[3J` deletes the scrollback itself, so there is nothing above to be
-   * parked in and the viewport has nowhere to sit but the top of a clean
-   * screen. Both are needed and the order matters: erase the history, erase the
-   * screen, then home.
-   */
-  /**
-   * ── ⚠️⚠️ THE CANONICAL CLEAR, IN THE CANONICAL ORDER — TWICE WRONG BEFORE ──
-   *
-   * Roman, twice: *"you have to scroll down to see the prompt area."*
-   *
-   * What `clear` itself emits is `ESC[H ESC[2J ESC[3J` — HOME FIRST, then erase
-   * the screen, then erase the scrollback. I had `3J 2J` with the home last, and
-   * the order is not cosmetic: erasing scrollback while the cursor is still
-   * parked in it leaves the viewport anchored to a region that no longer exists,
-   * so the terminal keeps showing the old shell output and our banner and prompt
-   * sit below the fold.
+   * ⭐ AND THE REFERENCE NEVER DID THIS. Claude Code does not clear your screen
+   * when it starts; your prompt, your previous commands and your scrollback are
+   * all still there afterwards. I imported a clear because I was thinking of a
+   * full-screen TUI, and then spent four builds fixing the ORDER of an operation
+   * that should not have existed.
    *
-   * ⭐ HOME FIRST puts the viewport at the top of the buffer BEFORE anything is
-   * erased, so there is nowhere stale for it to stay.
+   * ⚠️ THE ROOM IS MADE BY SCROLLING, NOT BY ERASING. Printing `rows` newlines
+   * pushes existing content up exactly as any command would, leaving the cursor
+   * on the last line with `rows` blank lines below the content. Stepping back up
+   * to `bottom` and declaring the region there reserves those lines for the
+   * input — and everything above is untouched, still scrollable, still theirs.
    *
-   * ⚠️ AND THE SCROLL REGION IS SET LAST. Setting a region while the cursor is
-   * outside it is undefined across terminals — some clamp, some ignore it. Clear
-   * completely, then declare the region, then place the cursor inside it.
+   * ⚠️ THE CURSOR IS PLACED LAST, AND THAT IS NOT COSMETIC: DECSTBM homes the
+   * cursor to (1,1) as a side effect. Without the final move, the first line of
+   * output would land at the TOP of the screen and overwrite the banner — which
+   * is a quieter version of the same defect this rewrite removes.
    */
-  output.write(`${CSI}H${CSI}2J${CSI}3J${CSI}1;${bottom}r${CSI}1;1H`);
+  const makeRoom = '\n'.repeat(rows);
+  output.write(`${makeRoom}${CSI}${rows}A${CSI}1;${bottom}r${CSI}${bottom};1H`);
 
   const release = () => {
     if (released) return;
     released = true;
     /**
-     * ⚠️ `ESC[r` WITH NO ARGUMENTS RESETS TO THE FULL SCREEN. Then the cursor is
-     * moved below the reserved rows so the shell prompt does not land on top of
-     * our box — an exit that leaves the terminal technically correct and
-     * visually broken is still a bad exit.
+     * ⚠️ `ESC[r` WITH NO ARGUMENTS RESETS TO THE FULL SCREEN. Then the cursor
+     * moves below the reserved rows so the shell prompt does not land on top of
+     * our input — an exit that is technically correct and visually broken is
+     * still a bad exit.
+     *
+     * ⭐ AND NOTHING IS ERASED ON THE WAY OUT EITHER. The session the user just
+     * had stays on screen and in scrollback, which is the whole point of not
+     * having taken over their terminal in the first place.
      */
     try {
-      output.write(`${CSI}r${CSI}${height};1H\n`);
+      output.write(`${CSI}r${CSI}${height};1H
+`);
     } catch { /* the stream may already be gone on a hard exit */ }
   };
 

package/package.json

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