howtofixcli 0.7.8 → 0.7.9

package/dist/tool-render.js

@@ -1,769 +0,0 @@
-import { homedir } from "node:os";
-import { isAbsolute, relative, resolve, sep } from "node:path";
-import { formatElapsed } from "./workflow-progress.js";
-/**
- * Tool call/result rendering, in the shape Claude Code uses:
- *
- *   ⏺ Read(src/ui.ts)
- *     ⎿  120 lines
- *   ⏺ Edit(src/ui.ts)
- *     ⎿  +12 / -3
- *   ⏺ Bash(git status)
- *     ⎿  exit 0
- *
- * Everything here is pure text, so it can be exercised without a session, a
- * model, or a terminal. `ui.ts` feeds it the SDK's tool events; `feed.ts` colours
- * and indents the result.
- */
-/**
- * Marks a tool invocation. `●` (U+25CF) is deliberate: unlike `⏺` (U+23FA) it
- * carries neither the Unicode Emoji property nor a coverage gap — all 12
- * monospace fonts shipped on this box have it, while `⏺` is present in only one.
- */
-export const TOOL_MARKER = "●";
-/**
- * Marks the result belonging to the invocation above it. `└` (U+2514) rather
- * than Claude Code's `⎿` (U+23BF): the box-drawing elbow is present in DejaVu,
- * Liberation and FreeMono, whereas `⎿` is missing from every monospace font
- * here except FreeMono and renders as tofu almost everywhere.
- */
-export const RESULT_MARKER = "└";
-/**
- * Marks the collapsed body of a result. `⋯` (U+22EF) rather than an ellipsis
- * character alone: the row reads as "there is more here, press ctrl+e", and the
- * midline dots sit inside the same monospace cell width as the other markers.
- */
-export const EXPAND_MARKER = "⋯";
-/**
- * Braille spinner frames. Braille is outside the Unicode Emoji set, and this is
- * the same frame set the `ora` package made ubiquitous, so any font that shows
- * a CLI spinner at all has these.
- */
-export const SPINNER_FRAMES = ["⠋", "⠙", "⠹", "⠸", "⠼", "⠴", "⠦", "⠧", "⠇", "⠏"];
-/** The current spinner frame, derived from the clock so callers keep no state. */
-export function spinnerFrame(intervalMs = 90) {
-    const index = Math.floor(Date.now() / intervalMs) % SPINNER_FRAMES.length;
-    return SPINNER_FRAMES[index] ?? SPINNER_FRAMES[0];
-}
-/**
- * Marks a call that built something, as opposed to one that read something.
- *
- * A chat turn and a build are not the same event, and until they were marked
- * apart a session read as an undifferentiated wall of `● Mcp__robloxstudio__…`
- * lines: the mesh that took a minute to generate looked exactly like the sixth
- * `get_project_structure` of the same minute. Someone scrolling back to find
- * "the boat I made" had nothing to scroll to.
- *
- * `▲` (U+25B2) rather than a colour, first: colour is what a terminal strips —
- * through `NO_COLOR`, a pipe, or a log file — and the distinction has to survive
- * that.
- *
- * And then rather than the obvious `▸` (U+25B8) or `◫` (U+25EB), which is the
- * part measured rather than guessed: of the three monospace families installed
- * here, both of those are present in only two, so on Liberation Mono and FreeMono
- * they render as tofu — the same coverage gap the `⏺` note above exists to avoid.
- * `▲` is present in all three, carries no Emoji property, and keeps the same
- * single cell width as `●`.
- */
-export const BUILD_MARKER = "▲";
-/**
- * Marks a build that did not finish. `!` rather than a glyph: a failure is the
- * one line someone reads carefully, and an ASCII character cannot be missing
- * from a font.
- */
-export const BUILD_FAILED_MARKER = "!";
-/**
- * Marks a build that produced something a person can look at.
- *
- * `○` (U+25CB) for the same reason as the marker above — it is in all three
- * families on this box, where the picture-like `◫` is in two. Kept apart from
- * `BUILD_MARKER` because it says something different: not "this wrote to the
- * place" but "there is a picture of what it wrote", which is the line worth
- * stopping on when scrolling back.
- */
-export const BUILD_IMAGE_MARKER = "○";
-/**
- * Tools whose completion produced or changed something, rather than reading it.
- *
- * The list is explicit rather than a pattern, for the reason the record's own
- * list is: a rule based on the name would catch whatever the next server calls
- * its read tool, and `get_project_structure` runs on nearly every turn. A build
- * marker on those would be noise, and noise on the lines that matter is worse
- * than no marker at all.
- */
-const BUILDING_TOOLS = [
-    // The bridge's own writes.
-    "create_object",
-    "set_properties",
-    "delete_object",
-    "clone_instance",
-    "reparent_instance",
-    "set_script_source",
-    "edit_script_lines",
-    "insert_script_lines",
-    "execute_luau",
-    // Studio's generators, reached as `mcp__roblox-studio__<name>`.
-    "generate_mesh",
-    "generate_material",
-    "generate_procedural_model",
-];
-/**
- * The bare tool name, with any `mcp__<server>__` prefix removed.
- *
- * The CLI sees both sources prefixed, so a marker that only worked for one of
- * them would mark half the builds.
- */
-export function bareToolName(toolName) {
-    return toolName.includes("__") ? toolName.slice(toolName.lastIndexOf("__") + 2) : toolName;
-}
-/** Whether this call built something, as opposed to reading it. */
-export function isBuildTool(toolName) {
-    return BUILDING_TOOLS.includes(bareToolName(toolName));
-}
-/**
- * The marker a finished call gets.
- *
- * An ordinary call keeps `●`, so a build stands out by being different rather
- * than by everything else being marked. A failed build is marked apart from a
- * failed read: the first says the place may have been left half-changed, which
- * is the one failure worth going back to look at.
- */
-export function resultMarker(toolName, isError) {
-    if (!isBuildTool(toolName))
-        return TOOL_MARKER;
-    return isError ? BUILD_FAILED_MARKER : BUILD_MARKER;
-}
-/**
- * The shortest path that still identifies the file.
- *
- * A model passes an absolute path as readily as a relative one - measured, not
- * assumed: asked to read `src/theme.ts` by absolute path, it did - and printing
- * `/Users/…/HowToFix-CLI/src/theme.ts` spends 40 characters of the line saying
- * what `src/theme.ts` says in 12. Claude Code's `getDisplayPath` applies the
- * same three rules, in the same order:
- *
- *   1. relative to the working directory, when that does not escape it
- *   2. `~`-relative for a path under home
- *   3. absolute, when neither applies
- *
- * This is a DISPLAY transform only. The tool receives the path the model sent;
- * nothing here rewrites an argument.
- */
-export function displayPath(filePath, cwd = process.cwd()) {
-    if (!filePath)
-        return filePath;
-    if (!isAbsolute(filePath))
-        return filePath;
-    // Normalise first. Both problems with the earlier versions came from a path
-    // that still held a `..` when it was measured: `relative()` then produced a
-    // `..`-prefixed string that lost to the absolute form, and the `~` branch
-    // produced `~/…/HowToFix-CLI/../elsewhere/x.ts`, which is longer than what it
-    // replaced. Resolving once makes both checks answer about the real location.
-    const resolved = resolve(filePath);
-    const rel = relative(cwd, resolved);
-    // The working directory itself has no relative form - `relative` returns `""`
-    // - and falling through to the home rule printed `~/Kuliah/iseng/HowToFix-CLI`
-    // for a path whose whole identity is "here". `.` is what it is.
-    if (rel === "")
-        return ".";
-    // Rule 1: inside the working directory. `..` only appears when it is not.
-    if (rel && !rel.startsWith(`..${sep}`) && rel !== "..")
-        return rel;
-    // Rule 2: under home. Checked after the working directory, so a repository in
-    // home shows `src/theme.ts` rather than `~/Kuliah/iseng/HowToFix-CLI/src/…`.
-    const home = homedir();
-    if (home && (resolved === home || resolved.startsWith(home + sep))) {
-        return `~${resolved.slice(home.length)}`;
-    }
-    return resolved;
-}
-/** Collapse whitespace and clip to a budget, for one-line summaries. */
-export function clip(text, max) {
-    const one = text.replace(/\s+/g, " ").trim();
-    return one.length > max ? `${one.slice(0, Math.max(1, max - 1))}…` : one;
-}
-function field(args, key) {
-    if (args && typeof args === "object") {
-        const value = args[key];
-        if (typeof value === "string" && value.length > 0)
-            return value;
-        if (typeof value === "number")
-            return String(value);
-    }
-    return undefined;
-}
-function argsSummary(args, max = 160) {
-    if (!args || typeof args !== "object")
-        return "";
-    try {
-        const text = JSON.stringify(args);
-        return text && text !== "{}" ? clip(text, max) : "";
-    }
-    catch {
-        return "";
-    }
-}
-/**
- * The text between `⏺ Name(` and `)`. Kept separate from the formatting so the
- * target can be reused (for example by a future expanded view).
- */
-export function toolTarget(toolName, args) {
-    switch (toolName) {
-        case "read": {
-            const path = displayPath(field(args, "path") ?? "");
-            const range = [field(args, "offset"), field(args, "limit")].filter(Boolean);
-            return range.length > 0 ? `${path} ${range.length === 1 ? `offset=${range[0]}` : `offset=${range[0]}, limit=${range[1]}`}` : path;
-        }
-        case "edit":
-        case "write":
-            return displayPath(field(args, "path") ?? "");
-        case "bash":
-        case "powershell": {
-            const command = field(args, "command") ?? "";
-            // A background command is the one thing about it a reader has to know: the
-            // call returns immediately and the work keeps going.
-            const background = args?.run_in_background === true;
-            return background ? `${command}  [background]` : command;
-        }
-        case "bash_output": {
-            const id = field(args, "task_id");
-            const filter = field(args, "filter");
-            if (!id)
-                return "all tasks";
-            return filter ? `${id} filter=${filter}` : id;
-        }
-        case "kill_shell":
-            return field(args, "task_id") ?? "";
-        case "compress": {
-            // `content` is an array of ranges; the topic alone does not say how much
-            // is being collapsed, and the range count is the useful second fact.
-            const topic = field(args, "topic") ?? "";
-            const ranges = Array.isArray(args.content) ? args.content.length : 0;
-            return ranges > 1 ? `${topic} (${ranges} ranges)` : topic;
-        }
-        case "grep": {
-            const pattern = field(args, "pattern") ?? "";
-            const where = field(args, "path");
-            return where ? `${pattern} in ${displayPath(where)}` : pattern;
-        }
-        case "find":
-        case "glob": {
-            const pattern = field(args, "pattern") ?? field(args, "glob") ?? "";
-            const where = field(args, "path");
-            return where ? `${pattern} in ${displayPath(where)}` : pattern;
-        }
-        case "ls":
-            // `ls` renders a path like the others; it was the one left absolute, so
-            // the tool that lists a directory printed the longest form of its name.
-            return displayPath(field(args, "path") ?? ".");
-        case "task":
-            return field(args, "agent") ?? "task";
-        case "ask":
-            return field(args, "question") ?? "";
-        case "web_search":
-            return field(args, "query") ?? "";
-        case "web_fetch":
-            return field(args, "url") ?? "";
-        case "lsp": {
-            const action = field(args, "action") ?? "lsp";
-            const file = field(args, "file") ?? "";
-            const line = field(args, "line");
-            return line ? `${action} ${file}:${line}` : `${action} ${file}`;
-        }
-        case "quality":
-            return field(args, "path") ?? "changed files";
-        case "think":
-            return "private";
-        case "todo": {
-            const op = field(args, "op") ?? "view";
-            const task = field(args, "task");
-            const items = args?.items;
-            if (op === "init" && Array.isArray(items))
-                return `init ${items.length} task${items.length === 1 ? "" : "s"}`;
-            return task ? `${op} ${task}` : op;
-        }
-        case "context": {
-            const op = field(args, "op") ?? "list";
-            const key = field(args, "key");
-            return key ? `${op} ${key}` : op;
-        }
-        case "workflow": {
-            const path = field(args, "path");
-            if (path)
-                return path;
-            const code = field(args, "code") ?? "";
-            // Show the script's own name when it declares one; it is the useful handle.
-            const name = /export\s+const\s+meta\s*=\s*\{[\s\S]*?name\s*:\s*["'`]([^"'`]+)/.exec(code)?.[1];
-            if (name)
-                return name;
-            const first = code.trim().split("\n")[0] ?? "";
-            return first.length > 40 ? `${first.slice(0, 40)}…` : first;
-        }
-        default:
-            return argsSummary(args);
-    }
-}
-/** `⏺ Read(src/ui.ts)` — the invocation line. */
-export function formatToolCall(toolName, args, max = 100) {
-    // An MCP name arrives as `mcp__roblox-studio__generate_mesh`, and title-casing
-    // that produced `Mcp__roblox-studio__generate_mesh` — the server's name twice,
-    // in the one line meant to be scanned. The bare name is what the person
-    // recognises, and it is also what decides whether this is a build.
-    const bare = bareToolName(toolName);
-    const isMcp = bare !== toolName;
-    const label = isMcp
-        ? bare
-        : bare.charAt(0).toUpperCase() + bare.slice(1);
-    const marker = isBuildTool(toolName) ? BUILD_MARKER : TOOL_MARKER;
-    const target = clip(toolTarget(bare, args), max);
-    return target ? `${marker} ${label}(${target})` : `${marker} ${label}`;
-}
-/**
- * Counts `+`/`-` lines in a unified diff, skipping the `+++`/`---` file headers.
- *
- * It must be a unified diff: a caller that passes `+12 -3` (a stat, not a diff)
- * gets zero from both counters, because no line starts with a single marker.
- * That is not a bug in the counter but it is a silent wrong answer, and it cost
- * a debugging round when a fixture used the wrong shape.
- */
-export function diffStat(diff) {
-    let additions = 0;
-    let removals = 0;
-    for (const line of diff.split("\n")) {
-        if (line.startsWith("+") && !line.startsWith("+++"))
-            additions += 1;
-        else if (line.startsWith("-") && !line.startsWith("---"))
-            removals += 1;
-    }
-    return { additions, removals };
-}
-function resultText(result) {
-    const content = result?.content;
-    if (typeof content === "string")
-        return content;
-    if (!Array.isArray(content))
-        return "";
-    return content.map((part) => (part && typeof part === "object" && part.type === "text" ? String(part.text ?? "") : "")).join("");
-}
-/**
- * The `details` bag of a tool result, or an empty object.
- *
- * Exported because the workbench needs the same shape to build a live panel from
- * a partial result, and two readings of the same field would drift.
- */
-export function detailsOf(result) {
-    const details = result?.details;
-    return details && typeof details === "object" ? details : {};
-}
-/**
- * `structuredContent` is where the SDK puts machine-readable tool output. For
- * bash that is `{ output, truncated, exit_code, wall_time_seconds }` — `details`
- * is undefined for shell tools, so this is the only reliable exit code.
- */
-function structuredOf(result) {
-    const structured = result?.structuredContent;
-    return structured && typeof structured === "object" ? structured : {};
-}
-function exitCodeOf(structured) {
-    const code = structured.exit_code;
-    return typeof code === "number" && Number.isFinite(code) ? code : undefined;
-}
-/**
- * What a build produced, as one line, or nothing when the result does not say.
- *
- * Both real shapes are read because both are real: the bridge answers with an
- * object, and Studio answers with content blocks whose text is JSON. Reading
- * only the top level would leave every generator result blank — the half where
- * the line matters most, since a generated mesh is the slow thing worth seeing
- * the outcome of.
- *
- * Nothing is invented. An absent count stays absent, because `0 instances` and
- * "nobody counted" are different facts and only one of them is a problem. A
- * result that says nothing recognisable returns nothing, and the caller falls
- * back to the ordinary summary rather than to a guess.
- */
-function buildSummary(result) {
-    const candidates = [];
-    if (result && typeof result === "object") {
-        candidates.push(result);
-        const content = result.content;
-        if (Array.isArray(content)) {
-            for (const part of content) {
-                const text = part?.text;
-                if (typeof text !== "string")
-                    continue;
-                try {
-                    const parsed = JSON.parse(text);
-                    if (parsed && typeof parsed === "object")
-                        candidates.push(parsed);
-                }
-                catch {
-                    // A plain sentence from Studio carries no counts. The call still
-                    // happened; it just has nothing to add here.
-                }
-            }
-        }
-    }
-    const parts = [];
-    for (const candidate of candidates) {
-        const instances = ["instances", "instanceCount", "count", "parts", "partsCreated"]
-            .map((key) => candidate[key])
-            .find((value) => typeof value === "number" && Number.isFinite(value));
-        // "1 instances" reads as machine output, and this line is shown to a person.
-        if (typeof instances === "number") {
-            parts.push(`${instances} instance${instances === 1 ? "" : "s"}`);
-        }
-        const files = firstStringList(candidate, ["files", "written", "paths"]);
-        if (files)
-            parts.push(files.join(", "));
-        const images = firstStringList(candidate, ["images", "renders", "screenshots"]);
-        // The marker says a picture exists; the name says which. Both, because a
-        // marker with no name leaves nothing to open. The word "renders" is spelled
-        // out beside it so the glyph is never the only thing carrying the meaning.
-        if (images)
-            parts.push(`renders ${BUILD_IMAGE_MARKER} ${images.join(", ")}`);
-        const findings = firstStringList(candidate, ["findings", "warnings", "errors"]);
-        // The count only, here: the feed is a summary line, and the findings
-        // themselves are long enough to bury it. They are what a check reports in
-        // full elsewhere; this line's job is to say there is something to look at.
-        if (findings)
-            parts.push(`${findings.length} finding${findings.length === 1 ? "" : "s"}`);
-        if (parts.length > 0)
-            break;
-    }
-    return parts.length > 0 ? parts.join(" · ") : undefined;
-}
-function firstStringList(record, keys) {
-    for (const key of keys) {
-        const value = record[key];
-        if (!Array.isArray(value))
-            continue;
-        const strings = value.filter((entry) => typeof entry === "string" && entry !== "");
-        if (strings.length > 0)
-            return strings;
-    }
-    return undefined;
-}
-function firstLine(text) {
-    return (text
-        .trim()
-        .split("\n")
-        .find((line) => line.trim()) ?? "");
-}
-/** ` (N lines)` for a shell call, preferring the structured output over the text. */
-function shellOutputLines(structured, text) {
-    const output = typeof structured.output === "string" ? structured.output : text.replace(/\n*Command exited with code \d+\s*$/, "");
-    const lines = lineCount(output);
-    return lines > 0 ? ` (${lines} line${lines === 1 ? "" : "s"})` : "";
-}
-/**
- * `1 line` / `2 lines`.
- *
- * Every count label in this file needs it, and the one that was written inline
- * (`write`) was the one that got it wrong. Claude Code reaches the same
- * conclusion from the other direction: its collapse summary carries the
- * singular/plural branch six times, once per category.
- */
-function plural(count, one, many) {
-    return count === 1 ? one : many;
-}
-function lineCount(text) {
-    const trimmed = text.trim();
-    return trimmed ? trimmed.split("\n").length : 0;
-}
-/**
- * The summary after `⎿`. This is the line that makes a tool call readable at a
- * glance: line counts for reads, a diff stat for edits, an exit code for shell.
- */
-/** Token counts are read at a glance, so thousands collapse to one decimal. */
-function formatTokens(count) {
-    return count < 1000 ? `${count} tokens` : `${(count / 1000).toFixed(1)}k tokens`;
-}
-export function formatToolResult(toolName, result, isError) {
-    const text = resultText(result);
-    const details = detailsOf(result);
-    const structured = structuredOf(result);
-    // A failed call reports its own reason, which beats any generic summary. The
-    // SDK wraps a nonzero exit as "<output>\n\n\nCommand exited with code N"; the
-    // code itself is more useful as a summary, so prefer it when present.
-    if (isError) {
-        const code = exitCodeOf(structured);
-        if (code !== undefined && (toolName === "bash" || toolName === "powershell"))
-            return `exit ${code}`;
-        const first = text
-            .trim()
-            .split("\n")
-            .find((line) => line.trim());
-        return clip(first ?? "failed", 120);
-    }
-    // A build reports what it produced, before any generic handling. "Done" on a
-    // mesh that produced eight instances says nothing a person can use, and the
-    // whole reason a build is marked apart is so the line can be read for what it
-    // made.
-    if (isBuildTool(toolName)) {
-        const summary = buildSummary(result);
-        if (summary)
-            return summary;
-        // A result with no counts still said something happened to something. The
-        // tool's own name is the honest summary — `set_properties` on a part is what
-        // occurred — where a generic "done" would spend the line saying nothing.
-        const bare = bareToolName(toolName);
-        if (bare === "execute_luau")
-            return "ran";
-        return clip(bare.replace(/_/g, " "), 120);
-    }
-    switch (toolName) {
-        case "task": {
-            // The first line of the result is the child's own summary
-            // (`## scout#id done (17 tool uses · 56.6k · 1m 34.3s)`), so the feed shows
-            // that rather than the whole report: what the child produced belongs to the
-            // model, and the reader needs the shape of the work. Several children come
-            // back as one summary per line.
-            const heads = text
-                .split("\n")
-                .filter((line) => line.startsWith("## "))
-                .map((line) => line.replace(/^##\s*/, "").trim());
-            if (heads.length === 0) {
-                const first = text
-                    .trim()
-                    .split("\n")
-                    .find((line) => line.trim());
-                return clip(first ?? "done", 120);
-            }
-            return heads.map((head) => clip(head, 120)).join("\n");
-        }
-        case "read": {
-            const truncation = details.truncation;
-            // The truncation notice is appended to the content, so it must not count
-            // towards the line total.
-            const lines = lineCount(text.replace(/\n*\[[^\]]*\]\s*$/, ""));
-            const base = lines === 0 ? "empty" : `${lines} line${lines === 1 ? "" : "s"}`;
-            return truncation?.truncated ? `${base} (truncated from ${truncation.totalLines ?? "?"})` : base;
-        }
-        case "compress": {
-            // The number the user otherwise has to type /dcp status to see. Without
-            // it a compression is invisible: it changes what the provider is sent and
-            // nothing on screen, so there is no way to tell it helped.
-            const blockIds = Array.isArray(details.blockIds) ? details.blockIds : [];
-            const replaced = typeof details.compressedTokens === "number" ? details.compressedTokens : 0;
-            const summaryTokens = typeof details.summaryTokens === "number" ? details.summaryTokens : 0;
-            const label = blockIds.length === 1 ? `b${String(blockIds[0])}` : `${blockIds.length} blocks`;
-            if (replaced === 0)
-                return label;
-            // A summary can be LARGER than what it replaced - a model that copies the
-            // file contents into it does exactly that. Clamping at zero printed
-            // "0 tokens saved" for a compression that added 161 tokens, which reads as
-            // a no-op rather than as the regression it is. The sign is the whole
-            // message here.
-            const delta = replaced - summaryTokens;
-            if (delta < 0)
-                return `${label} · ${formatTokens(-delta)} LARGER than the range`;
-            return `${label} · ${formatTokens(delta)} saved`;
-        }
-        case "edit": {
-            const diff = typeof details.diff === "string" ? details.diff : "";
-            if (!diff)
-                return "applied";
-            const { additions, removals } = diffStat(diff);
-            return `+${additions} / -${removals}`;
-        }
-        case "write": {
-            const lines = lineCount(text);
-            if (lines === 0)
-                return "written";
-            // `written (1 lines)` was the only label in this file that did not agree
-            // with its own count. `read`, `grep` and `web_search` all handle the
-            // singular; this one did not, because the plural was written inline here
-            // rather than through the helper below.
-            return `written (${lines} ${plural(lines, "line", "lines")})`;
-        }
-        case "bash":
-        case "powershell": {
-            // Ground truth (dist/core/tools/bash.js): `details` is always undefined and
-            // the exit code lives in `structuredContent.exit_code`. The earlier version
-            // of this formatter matched /exit code:/ against the content, which never
-            // matches the SDK's "Command exited with code N" wording, so every shell
-            // call summarised as a bare "done".
-            const code = exitCodeOf(structured);
-            if (code === undefined)
-                return text.trim() ? clip(firstLine(text), 120) : "done";
-            const suffix = shellOutputLines(structured, text);
-            return code === 0 ? `exit 0${suffix}` : `exit ${code}`;
-        }
-        case "grep": {
-            const lines = lineCount(text);
-            return lines === 0 ? "no matches" : `${lines} match${lines === 1 ? "" : "es"}`;
-        }
-        case "web_search": {
-            const count = typeof details.count === "number" ? details.count : lineCount(text);
-            return count === 0 ? "no results" : `${count} result${count === 1 ? "" : "s"}`;
-        }
-        case "web_fetch": {
-            const chars = typeof details.chars === "number" ? details.chars : text.length;
-            return `${chars} chars`;
-        }
-        case "lsp": {
-            const count = typeof details.count === "number" ? details.count : undefined;
-            if (typeof details.error === "string")
-                return clip(details.error, 120);
-            return count === undefined ? clip(firstLine(text), 120) : `${count} location${count === 1 ? "" : "s"}`;
-        }
-        case "quality": {
-            if (typeof details.error === "string")
-                return clip(details.error, 120);
-            if (details.off === true)
-                return "off";
-            const files = typeof details.files === "number" ? details.files : 0;
-            const functions = typeof details.functions === "number" ? details.functions : 0;
-            const findings = typeof details.findings === "number" ? details.findings : 0;
-            const score = typeof details.score === "number" ? ` · ${Math.round(details.score)}` : "";
-            if (files === 0)
-                return "no files";
-            return `${files} file${files === 1 ? "" : "s"} · ${functions} fn · ${findings} finding${findings === 1 ? "" : "s"}${score}`;
-        }
-        case "todo": {
-            const todos = (details.todos ?? []);
-            if (!Array.isArray(todos) || todos.length === 0)
-                return "list cleared";
-            const done = todos.filter((item) => item.status === "completed").length;
-            const open = todos.filter((item) => item.status === "pending" || item.status === "in_progress").length;
-            return `${done}/${todos.length} done, ${open} open`;
-        }
-        case "context": {
-            const notes = details.notes;
-            const count = notes ? Object.keys(notes).length : 0;
-            return count === 0 ? "no notes" : `${count} note${count === 1 ? "" : "s"} held`;
-        }
-        case "workflow": {
-            const agents = typeof details.agents === "number" ? details.agents : 0;
-            const tokens = typeof details.outputTokens === "number" ? details.outputTokens : 0;
-            const failed = Array.isArray(details.steps) ? details.steps.filter((step) => step.status === "failed").length : 0;
-            if (typeof details.error === "string")
-                return `failed after ${agents} agent(s)`;
-            const elapsed = typeof details.startedAt === "number" && typeof details.endedAt === "number" ? `, ${formatElapsed(details.endedAt - details.startedAt)}` : "";
-            return `${agents} agent(s), ${tokens} tokens${elapsed}${failed > 0 ? `, ${failed} failed` : ""}`;
-        }
-        case "bash_output": {
-            // The first line the tool writes is the task and its state; the rest is the
-            // task's own output, which the summary should not repeat.
-            const head = text.trim().split("\n")[0] ?? "";
-            const state = /running/.test(head) ? "running" : /finished/.test(head) ? "finished" : "task";
-            const body = text
-                .trim()
-                .split("\n")
-                .slice(2)
-                .filter((line) => line.trim()).length;
-            return body === 0 ? state : `${state} · ${body} line${body === 1 ? "" : "s"}`;
-        }
-        case "kill_shell": {
-            const first = text.trim().split("\n")[0] ?? "";
-            return first.startsWith("Stopped") ? "stopped" : clip(first, 120);
-        }
-        default: {
-            const first = text
-                .trim()
-                .split("\n")
-                .find((line) => line.trim());
-            return first ? clip(first, 120) : "done";
-        }
-    }
-}
-/**
- * Body lines under a result. Deliberately narrow: the summary line already
- * carries the gist, so only a diff (edits) or a few output lines (shell) are
- * worth repeating. Everything else stays collapsed until there is an expand
- * toggle.
- */
-export function toolResultDetail(toolName, result) {
-    const details = detailsOf(result);
-    if (toolName === "edit" && typeof details.diff === "string") {
-        return details.diff
-            .split("\n")
-            .filter((line) => line.length > 0)
-            .slice(0, 12);
-    }
-    if (toolName === "bash" || toolName === "powershell") {
-        // A background start has no command output yet; its content is the task
-        // header, which the summary already carries.
-        const body0 = resultText(result);
-        if (body0.startsWith("Started bash_"))
-            return [];
-        // The exit code is already the summary; show the command's own output. The
-        // SDK appends "Command exited with code N" to the content on failure, which
-        // would only repeat the summary line.
-        const structured = structuredOf(result);
-        const body = typeof structured.output === "string" ? structured.output : resultText(result).replace(/\n*Command exited with code \d+\s*$/, "");
-        const lines = body
-            .trimEnd()
-            .split("\n")
-            .filter((line) => line.trim());
-        return lines.slice(-4);
-    }
-    if (toolName === "bash_output") {
-        // The task's own output is the point, so show its last lines.
-        const lines = resultText(result)
-            .split("\n")
-            .slice(2)
-            .filter((line) => line.trim());
-        return lines.slice(-6);
-    }
-    if (toolName === "todo") {
-        // The list is the point of the tool, so show it rather than only counting.
-        const todos = (details.todos ?? []);
-        const mark = { pending: "[ ]", in_progress: "[>]", completed: "[x]", dropped: "[-]" };
-        return todos.slice(0, 6).map((item) => `${mark[item.status ?? "pending"] ?? "[ ]"} ${item.content ?? ""}`);
-    }
-    if (toolName === "task") {
-        // The summary carries each child's header, so the detail is the report under
-        // it — the child's own words, which is what the parent reads next and what a
-        // reader wants when they open a call. The header is dropped rather than
-        // repeated, so the two lines do not say the same thing twice.
-        return resultText(result)
-            .split("\n")
-            .filter((line) => line.trim() && !line.startsWith("## "))
-            .slice(0, 6);
-    }
-    if (toolName === "workflow") {
-        // A workflow is only legible if you can see the agents it ran and where each
-        // one failed, so the steps are the detail rather than a count.
-        const steps = (details.steps ?? []);
-        const lines = steps.map((step) => {
-            const glyph = step.status === "running" ? "▸" : step.status === "failed" ? "×" : "✓";
-            const where = step.phase ? `${step.phase} · ` : "";
-            return `${glyph} ${where}${step.label ?? "agent"}`;
-        });
-        return lines.slice(-6);
-    }
-    return [];
-}
-/**
- * The whole output of a tool call, for the expand toggle.
- *
- * `toolResultDetail` is deliberately narrow — the summary line already carries
- * the gist, and the workbench is a transcript, not a log viewer. That is the
- * right default and the wrong *only* option: when a call needs to be read in
- * full (a diff that did not apply, the tail of a failing suite, the file a
- * `read` actually returned), the user wants the whole thing without leaving the
- * screen or asking the agent to repeat it.
- *
- * Capped so a stray `cat` of a huge file cannot wedge the render: the cap is
- * large enough to read a normal result and small enough that one keypress
- * cannot paint a megabyte.
- */
-export const EXPANDED_LINE_CAP = 400;
-export function toolResultFull(toolName, result) {
-    const details = detailsOf(result);
-    if (toolName === "edit" && typeof details.diff === "string") {
-        return details.diff
-            .split("\n")
-            .filter((line) => line.length > 0)
-            .slice(0, EXPANDED_LINE_CAP);
-    }
-    const structured = structuredOf(result);
-    const body = typeof structured.output === "string" ? structured.output : resultText(result).replace(/\n*Command exited with code \d+\s*$/, "");
-    const lines = body.trimEnd().split("\n");
-    const kept = lines.slice(0, EXPANDED_LINE_CAP);
-    if (lines.length > EXPANDED_LINE_CAP)
-        kept.push(`… ${lines.length - EXPANDED_LINE_CAP} more line(s)`);
-    return kept;
-}