@vincemakes/kiso-code 0.15.5 → 0.15.6

package/dist/byte-trace.d.ts

@@ -0,0 +1,46 @@
+/**
+ * REL-0152-D12 — the byte trace: what kiso actually sent, and when.
+ *
+ * Three defects in this round are only decidable from the byte stream:
+ *
+ *   - REL-0152-D1, the stray `[` and `]` at the row edges. `[` is the
+ *     CSI introducer and `]` the OSC introducer, so a lost ESC prints
+ *     exactly those two characters and nothing else — but kiso emits no
+ *     OSC at all, and every CSI it writes carries more than its
+ *     introducer. Either the bytes leaving kiso already contain those
+ *     characters (ours) or they do not (the terminal's parser). Nobody
+ *     can tell from a screenshot, and three rounds have now tried.
+ *   - REL-0152-D7, content that appears late or not at all. The frame
+ *     that should have carried it either went out or did not.
+ *   - the paste latency. The editor is measured at 146KB in 6ms, so if
+ *     a paste still feels slow the time is being spent before kiso sees
+ *     the bytes — which the arrival timestamps show directly.
+ *
+ * Set KISO_TRACE_BYTES to a path and every byte in BOTH directions is
+ * recorded with a millisecond stamp, then the file answers the question
+ * instead of another round of inference.
+ *
+ *   KISO_TRACE_BYTES=/tmp/kiso-bytes.jsonl kiso chat
+ *
+ * One JSON object per line: {ms, dir, n, b} — the stamp relative to the
+ * trace's start, "out" or "in", the byte count, and the bytes as base64
+ * so no escape, control character or partial UTF-8 sequence is altered
+ * on the way to disk. Nothing is interpreted here; interpretation is
+ * what the trace exists to make possible.
+ *
+ * OFF unless the variable is set: zero cost, and it never turns itself
+ * on. What it records is the terminal traffic of one session — screen
+ * output and keystrokes — so it is a diagnostic a person switches on
+ * deliberately, for one run, when something is wrong.
+ */
+/**
+ * Arm the trace if KISO_TRACE_BYTES names a file. Call once, before the
+ * dock is entered, so the first frame is in the record too.
+ *
+ * stdout is wrapped rather than tapped because there is no other way to
+ * see every write: the compositor, the CLI's own logging and node's
+ * error paths all reach the terminal through it. stdin is TAPPED — an
+ * extra "data" listener, which every listener receives — so the editor's
+ * own reading is untouched and the trace cannot swallow a keystroke.
+ */
+export declare function armByteTrace(): void;

package/dist/byte-trace.js

@@ -0,0 +1,103 @@
+/**
+ * REL-0152-D12 — the byte trace: what kiso actually sent, and when.
+ *
+ * Three defects in this round are only decidable from the byte stream:
+ *
+ *   - REL-0152-D1, the stray `[` and `]` at the row edges. `[` is the
+ *     CSI introducer and `]` the OSC introducer, so a lost ESC prints
+ *     exactly those two characters and nothing else — but kiso emits no
+ *     OSC at all, and every CSI it writes carries more than its
+ *     introducer. Either the bytes leaving kiso already contain those
+ *     characters (ours) or they do not (the terminal's parser). Nobody
+ *     can tell from a screenshot, and three rounds have now tried.
+ *   - REL-0152-D7, content that appears late or not at all. The frame
+ *     that should have carried it either went out or did not.
+ *   - the paste latency. The editor is measured at 146KB in 6ms, so if
+ *     a paste still feels slow the time is being spent before kiso sees
+ *     the bytes — which the arrival timestamps show directly.
+ *
+ * Set KISO_TRACE_BYTES to a path and every byte in BOTH directions is
+ * recorded with a millisecond stamp, then the file answers the question
+ * instead of another round of inference.
+ *
+ *   KISO_TRACE_BYTES=/tmp/kiso-bytes.jsonl kiso chat
+ *
+ * One JSON object per line: {ms, dir, n, b} — the stamp relative to the
+ * trace's start, "out" or "in", the byte count, and the bytes as base64
+ * so no escape, control character or partial UTF-8 sequence is altered
+ * on the way to disk. Nothing is interpreted here; interpretation is
+ * what the trace exists to make possible.
+ *
+ * OFF unless the variable is set: zero cost, and it never turns itself
+ * on. What it records is the terminal traffic of one session — screen
+ * output and keystrokes — so it is a diagnostic a person switches on
+ * deliberately, for one run, when something is wrong.
+ */
+import { appendFileSync, writeFileSync } from "node:fs";
+let path = null;
+let start = 0;
+function line(dir, data) {
+    if (path === null)
+        return;
+    const buf = typeof data === "string" ? Buffer.from(data, "utf8") : Buffer.from(data);
+    try {
+        appendFileSync(path, `${JSON.stringify({ ms: Date.now() - start, dir, n: buf.length, b: buf.toString("base64") })}\n`);
+    }
+    catch {
+        // a trace that fails must never take the session with it
+        path = null;
+    }
+}
+/**
+ * Arm the trace if KISO_TRACE_BYTES names a file. Call once, before the
+ * dock is entered, so the first frame is in the record too.
+ *
+ * stdout is wrapped rather than tapped because there is no other way to
+ * see every write: the compositor, the CLI's own logging and node's
+ * error paths all reach the terminal through it. stdin is TAPPED — an
+ * extra "data" listener, which every listener receives — so the editor's
+ * own reading is untouched and the trace cannot swallow a keystroke.
+ */
+export function armByteTrace() {
+    const target = process.env.KISO_TRACE_BYTES;
+    if (target === undefined || target === "")
+        return;
+    path = target;
+    start = Date.now();
+    try {
+        writeFileSync(path, "");
+    }
+    catch {
+        path = null;
+        return;
+    }
+    const write = process.stdout.write.bind(process.stdout);
+    process.stdout.write = ((chunk, ...rest) => {
+        line("out", chunk);
+        return write(chunk, ...rest);
+    });
+    process.stdin.on("data", (chunk) => line("in", chunk));
+    // The environment goes in the record FIRST, because kiso emits
+    // DIFFERENT frame bytes per terminal — DEC 2026 synchronized output
+    // where it is supported, a cursor-hide degrade on Apple Terminal —
+    // so a capture that does not say which terminal made it cannot be
+    // compared against anything. Same for the size and the locale: a row
+    // is built to a width, and the ambiguous-width characters kiso uses
+    // in its own chrome (· … —) are one cell or two depending on how the
+    // terminal was told to treat them.
+    const env = {
+        TERM_PROGRAM: process.env.TERM_PROGRAM ?? null,
+        TERM_PROGRAM_VERSION: process.env.TERM_PROGRAM_VERSION ?? null,
+        TERM: process.env.TERM ?? null,
+        LANG: process.env.LANG ?? null,
+        LC_CTYPE: process.env.LC_CTYPE ?? null,
+        columns: process.stdout.columns ?? null,
+        rows: process.stdout.rows ?? null,
+    };
+    try {
+        appendFileSync(path, `${JSON.stringify({ ms: 0, dir: "env", n: 0, b: "", env })}\n`);
+    }
+    catch {
+        path = null;
+    }
+}

package/dist/index.js

@@ -42,6 +42,7 @@ import { autoCompactFromEnv, chat, contextWindowTokens, estimateCtxRatio } from
 import { loadProjectConfig, loadUserConfig, mergeConfigs, resolveAutoCompact, resolveContextWindow, resolveModel } from "./config.js";
 import { resume } from "./resume.js";
 import { resumeTail } from "./resume-tail.js";
+import { armByteTrace } from "./byte-trace.js";
 import { collectSessionCards, projectSessionCard } from "./session-cards.js";
 // The moved exports stay reachable from this entry — the test imports
 // (project-trust, coding-agent) never change (B4: zero assertion changes).
@@ -630,6 +631,9 @@ async function main() {
     // swallows it — the standard "the stream may die under me" idiom.
     process.stdout.on("error", () => { });
     process.stderr.on("error", () => { });
+    // REL-0152-D12: armed only by KISO_TRACE_BYTES, and armed HERE so the
+    // banner and the first frame are in the record. Off by default.
+    armByteTrace();
     // Modes: --mode <name> wins over KISO_MODE — both applied before the
     // first makeAgent (the tier extensions read `current` live). The flag
     // is stripped from the positional args, so it works in any position.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vincemakes/kiso-code",
-	"version": "0.15.5",
+	"version": "0.15.6",
 	"description": "kiso CLI \u2014 the durable coding agent that survives kill -9: kiso chat / kiso resume / kiso sessions.",
 	"type": "module",
 	"license": "MIT",
@@ -18,19 +18,19 @@
 		"test": "vitest run"
 	},
 	"dependencies": {
-		"@vincemakes/kiso-ask-ext": "0.15.5",
-		"@vincemakes/kiso-core": "0.15.5",
-		"@vincemakes/kiso-evals": "0.15.5",
-		"@vincemakes/kiso-mcp-ext": "0.15.5",
-		"@vincemakes/kiso-provider-anthropic": "0.15.5",
-		"@vincemakes/kiso-provider-openai": "0.15.5",
-		"@vincemakes/kiso-runtime": "0.15.5",
-		"@vincemakes/kiso-skills-ext": "0.15.5",
-		"@vincemakes/kiso-subagent-ext": "0.15.5",
-		"@vincemakes/kiso-task-ext": "0.15.5",
-		"@vincemakes/kiso-tools-node": "0.15.5",
-		"@vincemakes/kiso-tui": "0.15.5",
-		"@vincemakes/kiso-tui-cells": "0.15.5"
+		"@vincemakes/kiso-ask-ext": "0.15.6",
+		"@vincemakes/kiso-core": "0.15.6",
+		"@vincemakes/kiso-evals": "0.15.6",
+		"@vincemakes/kiso-mcp-ext": "0.15.6",
+		"@vincemakes/kiso-provider-anthropic": "0.15.6",
+		"@vincemakes/kiso-provider-openai": "0.15.6",
+		"@vincemakes/kiso-runtime": "0.15.6",
+		"@vincemakes/kiso-skills-ext": "0.15.6",
+		"@vincemakes/kiso-subagent-ext": "0.15.6",
+		"@vincemakes/kiso-task-ext": "0.15.6",
+		"@vincemakes/kiso-tools-node": "0.15.6",
+		"@vincemakes/kiso-tui": "0.15.6",
+		"@vincemakes/kiso-tui-cells": "0.15.6"
 	},
 	"devDependencies": {
 		"@types/node": "^26.1.2",