acuvo-code 0.6.0 → 0.6.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 78328 lines**, with **237 test files** beside them (counted 2026-08-22).
+`bin/` — about 78511 lines**, with **238 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 78328 lines and then ships
+caught the false green"*): a document that invites you to audit 78511 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,7 +892,7 @@ 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 120 files and 78328 lines,
+- ⭐ **Zero dependencies.** The entire auditable surface is 120 files and 78511 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

package/lib/input-box.mjs

@@ -528,7 +528,26 @@ export function pinRegion(output, { rows = 2, env = process.env } = {}) {
    * screen. Both are needed and the order matters: erase the history, erase the
    * screen, then home.
    */
-  output.write(`${CSI}3J${CSI}2J${CSI}1;${bottom}r${CSI}1;1H`);
+  /**
+   * ── ⚠️⚠️ 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.
+   *
+   * ⭐ HOME FIRST puts the viewport at the top of the buffer BEFORE anything is
+   * erased, so there is nowhere stale for it to stay.
+   *
+   * ⚠️ 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.
+   */
+  output.write(`${CSI}H${CSI}2J${CSI}3J${CSI}1;${bottom}r${CSI}1;1H`);
 
   const release = () => {
     if (released) return;