@vincemakes/kiso-tui-cells 0.32.0 → 0.32.2

package/dist/render.d.ts

@@ -176,6 +176,21 @@ export declare function foldThinking(block: string): string;
  *  the line the pipe has always written, which is what keeps the two
  *  renderings one shape rather than two. */
 export declare function foldThinkingRow(block: string, room: number): string;
+/**
+ * DC-60 (0.32.2) — the words of a turn, whatever shape its content took.
+ *
+ * A turn that carries an image is an ARRAY of blocks (text, image, text…)
+ * in the durable log. Its echo — the user chip while the session runs, the
+ * transcript's replay, the session listing — must say the words and mark
+ * the image, and it must say them from ONE definition: the live echo used
+ * to pass a string through and an array became an empty chip, while the
+ * transcript path projected the array on its own. The image mark is
+ * "(image)"; the bytes are never shown.
+ */
+export declare function echoText(content: string | readonly {
+    readonly type?: string;
+    readonly text?: string;
+}[]): string;
 /** v2b — the [result] echo truncates at 160 chars + a /last hint. */
 export declare function foldResult(content: string): string;
 /**
@@ -194,6 +209,22 @@ export declare function renderToolSummary(name: string, input: Record<string, un
  *  the summary detail uses, WITHOUT the counts (the header names what
  *  was expanded, not its size). */
 export declare function toolTarget(name: string, input: Record<string, unknown>): string;
+/**
+ * HF-1 (0.32.1) — a head row is ONE row, whatever the model wrote.
+ *
+ * The owner's 0.32.0 dogfood: the model issued a heredoc shell command
+ * (`python3 - <<'EOF' …`), the running card's head carried its newlines
+ * into the compositor, invariant ①b threw in the field and the process
+ * died. `escapeTerminal` keeps `\n` on purpose (text blocks need it); a
+ * HEAD ROW does not — it is one physical row by construction. So every
+ * builder that puts a tool's target on a row projects the breaks to a
+ * visible mark first: a line break becomes `⏎` (CRLF is one), a tab
+ * becomes one cell of space (its width is a property of the column, and
+ * a cut row has no column to give it). The full command is still on the
+ * approval panel and in the durable log; the row says what ran, in one
+ * row.
+ */
+export declare function oneRow(text: string): string;
 /** k-units for the status line: 12345 → 12.3k, 800 → 800, null → ?. */
 export declare function kUnit(value: number | null): string;
 /**

package/dist/render.js

@@ -142,6 +142,26 @@ export function foldThinkingRow(block, room) {
         : trimmed.slice(0, 100);
     return `${p.dim}…${head}${suffix}${p.reset}`;
 }
+/**
+ * DC-60 (0.32.2) — the words of a turn, whatever shape its content took.
+ *
+ * A turn that carries an image is an ARRAY of blocks (text, image, text…)
+ * in the durable log. Its echo — the user chip while the session runs, the
+ * transcript's replay, the session listing — must say the words and mark
+ * the image, and it must say them from ONE definition: the live echo used
+ * to pass a string through and an array became an empty chip, while the
+ * transcript path projected the array on its own. The image mark is
+ * "(image)"; the bytes are never shown.
+ */
+export function echoText(content) {
+    if (typeof content === "string")
+        return content;
+    return content
+        .map((b) => (b.type === "text" ? (b.text ?? "") : "(image)"))
+        .join(" ")
+        .replace(/ +/g, " ")
+        .trim();
+}
 /** v2b — the [result] echo truncates at 160 chars + a /last hint. */
 export function foldResult(content) {
     const flat = content.replaceAll("\n", " ");
@@ -167,7 +187,7 @@ export function renderToolSummary(name, input, result, reason = null) {
     }
     const mark = result.isError ? `${p.red}✗${p.reset}` : `${p.bold}✓${p.reset}`;
     const shortName = name.replace("_file", "");
-    const detail = toolSummaryDetail(name, input, result);
+    const detail = oneRow(toolSummaryDetail(name, input, result)); // HF-1: one row, whatever the command
     return `${mark} ${escapeTerminal(`${shortName} ${detail}`)}`;
 }
 function toolSummaryDetail(name, input, result) {
@@ -213,6 +233,27 @@ function toolSummaryDetail(name, input, result) {
  *  the summary detail uses, WITHOUT the counts (the header names what
  *  was expanded, not its size). */
 export function toolTarget(name, input) {
+    return oneRow(toolTargetRaw(name, input));
+}
+/**
+ * HF-1 (0.32.1) — a head row is ONE row, whatever the model wrote.
+ *
+ * The owner's 0.32.0 dogfood: the model issued a heredoc shell command
+ * (`python3 - <<'EOF' …`), the running card's head carried its newlines
+ * into the compositor, invariant ①b threw in the field and the process
+ * died. `escapeTerminal` keeps `\n` on purpose (text blocks need it); a
+ * HEAD ROW does not — it is one physical row by construction. So every
+ * builder that puts a tool's target on a row projects the breaks to a
+ * visible mark first: a line break becomes `⏎` (CRLF is one), a tab
+ * becomes one cell of space (its width is a property of the column, and
+ * a cut row has no column to give it). The full command is still on the
+ * approval panel and in the durable log; the row says what ran, in one
+ * row.
+ */
+export function oneRow(text) {
+    return text.replace(/\r\n|\n|\r/g, "\u23ce").replace(/\t/g, " ");
+}
+function toolTargetRaw(name, input) {
     switch (name) {
         case "read_file":
         case "write_file":

package/dist/strings.js

@@ -205,6 +205,12 @@ export const KEY_BINDINGS = [
     { keys: "alt+⌫ / alt+d", what: "delete word (ctrl+w too)" },
     { keys: "ctrl+x", what: "copy the last answer" },
     { keys: "ctrl+z / ctrl+y", what: "undo / redo" },
+    // REL-0152-D15/D16 — the image paste. It is on the sheet because a
+    // terminal's own Cmd+V only ever pastes TEXT: a human with an image on
+    // the clipboard has no way to discover this key by trying the obvious
+    // one, which is exactly the case the sheet exists for. It pairs with
+    // the undo row above and keeps the table's count even.
+    { keys: "ctrl+v", what: "attach a clipboard image" },
 ];
 /**
  * TUI2-R2pre ④ — THE display-verb table (the integrator's ruling).
@@ -294,7 +300,10 @@ const SHEET_GRID = [
     // exactly as its comment predicted it would.
     [10, 11],
     [12, 13],
-    [14],
+    // ctrl+v joins the undo row's neighbour: the count is even again, so
+    // the last row pairs instead of standing alone. The warning three
+    // comments up applies unchanged — this grid does not update itself.
+    [14, 15],
 ];
 const SHEET_STOPS = [
     [16, 43],
@@ -310,10 +319,11 @@ const SHEET_STOPS = [
     // The stop is 39 here because `alt+⌫ / alt+d delete word (ctrl+w too)`
     // is the widest first cell on the sheet — a narrower stop packs the
     // two cells together with a single space and the column disappears.
-    // The last row has ONE binding, so it pads nothing (an empty stop
-    // list, not a stop of 36, which would leave trailing blanks).
+    // The last row PAIRS now that ctrl+v joined (it had one binding and an
+    // empty stop list); it takes a stop like its neighbours so the second
+    // column lines up rather than following a single space.
+    [39],
     [39],
-    [],
 ];
 /**
  * TUI2-R1 (D) — the sheet, one screen, static.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vincemakes/kiso-tui-cells",
-	"version": "0.32.0",
+	"version": "0.32.2",
 	"description": "kiso tui-cells — the components cell renderer (components, diff, width, the render slice). Zero runtime dependencies: input is data, output is bytes.",
 	"type": "module",
 	"license": "MIT",