@aragon-agent/cli 0.6.46 → 0.6.48

package/dist/prompts/limits.js

@@ -1,53 +0,0 @@
-/**
- * Structural bounds for the quick-prompt library (quick-prompt-library §5.1).
- *
- * ASCII ONLY - `src/prompts/**` is inside `glyphs.test.ts::inScope`.
- *
- * STRUCTURE, NOT POLICY (index.md:52-56). Nothing here is user-tunable: these are
- * what an entry, the library and the picker's query can physically carry. The
- * three keys a user may actually change (`prompts.enabled`, `insertMode`, `hint`)
- * live in `config/schema.ts`, are clamped there, and are persisted there. Mixing
- * the two is how a "temporary" ceiling becomes a setting nobody clamps.
- *
- * EVERY NUMBER IS A CODE-POINT COUNT, not a byte count and not a UTF-16 length.
- * Titles and bodies are typed in Chinese by the users this feature exists for, so
- * a byte-based ceiling would silently allow a third of the characters a
- * Latin-alphabet user gets. `[...text].length` is the measurement everywhere in
- * this tree.
- */
-export const PROMPT_LIMITS = {
-    /** Entries one library may hold. The 201st create is REFUSED, never truncated. */
-    maxPrompts: 200,
-    /** Title, without surrounding whitespace. */
-    titleMaxChars: 80,
-    /** Body. Large enough for a 40-line procedure, small enough to rewrite cheaply. */
-    contentMaxChars: 8000,
-    /** Optional one-line note under the title. */
-    descriptionMaxChars: 200,
-    /** Tags per entry. */
-    maxTags: 6,
-    /** Characters per tag. */
-    tagMaxChars: 24,
-    /** Body preview lines the list page's detail block may spend (read-only). */
-    detailPreviewLines: 3,
-    /** Rows the list page's detail block may occupy, preview lines included. */
-    detailMaxLines: 6,
-    /** Characters of a body shown on ONE preview line. */
-    previewLineChars: 72,
-};
-/**
- * The picker's own structural bounds.
- *
- * A SEPARATE OBJECT because the picker is a separate surface with a separate
- * budget: its rows carry an index and a title and nothing else, and its query is
- * a filter rather than content. Sharing one object would tie a future change to
- * the library's row height.
- */
-export const PROMPT_PICKER_LIMITS = {
-    /** Longest query the filter accepts; further typing is ignored. */
-    queryMaxChars: 64,
-    /** `1`-`9` pick directly, so nine. */
-    quickDigits: 9,
-    /** Rows the picker's detail block may occupy. */
-    detailMaxLines: 4,
-};

package/dist/prompts/search.d.ts

@@ -1,58 +0,0 @@
-/**
- * Filtering and view ordering for the picker (quick-prompt-library D-9 / D-10).
- *
- * ASCII ONLY - `src/prompts/**` is inside `glyphs.test.ts::inScope`.
- *
- * SUBSEQUENCE MATCHING, NOT SUBSTRING MATCHING. `clr` should find `clean code
- * review`, and Chinese titles make the same demand in a different shape: the
- * characters a user remembers are rarely contiguous. The query is matched
- * case-insensitively against the title, then the tags, then the description, and
- * the FIELD a match landed in is a stronger signal than how good the match was.
- *
- * NO CHARACTER HIGHLIGHTING (D-10). Colouring the matched characters would mean
- * splitting a row into styled runs, and every row in this package is one
- * `wrap="truncate"` `<Text>` precisely so its height is exactly one row. The
- * detail block answers "why did this match" instead.
- */
-import type { QuickPrompt, PromptSortView } from './types.js';
-/**
- * Greedy subsequence match; `null` when `query` is not a subsequence of `text`.
- *
- * The score is LOWER-is-better and is built from what a reader would actually
- * call a good match: how early the first hit is, how tightly the hits cluster,
- * and how many characters had to be skipped between them.
- */
-export declare function subsequenceScore(text: string, query: string): number | null;
-/**
- * Filter, but NEVER REORDER BEYOND WHAT THE QUERY EARNS.
- *
- * Ties keep the library's own order, because a filter that reshuffles entries with
- * equal scores makes the list move under the user's arrow keys while they type.
- * Favourites win ties, which is the only preference the picker states.
- */
-export declare function searchPrompts(prompts: readonly QuickPrompt[], query: string): {
-    prompt: QuickPrompt;
-    score: number;
-}[];
-/**
- * The three presentations (D-9).
- *
- * `manual` is the only persisted order; the other two are VANISHING views. The one
- * that rearranges is `favorite` - `recent` sorts by `lastUsedAt` only, so an entry
- * that has never been used keeps its place at the tail instead of jumping around
- * while the user watches.
- */
-export declare function viewOrder(prompts: readonly QuickPrompt[], view: PromptSortView): QuickPrompt[];
-/** The next view in the `Ctrl+S` cycle (manual -> recent -> favorite -> manual). */
-export declare function nextView(view: PromptSortView): PromptSortView;
-/**
- * Title order, for the `/prompts sort name` write.
- *
- * A TOTAL order (title, then id): a sort the user asked for has to be reproducible, and
- * two entries sharing a title would otherwise swap places between runs - a "sorted"
- * library that reorders itself on every read is worse than an unsorted one. Code-unit
- * comparison rather than `localeCompare`, because the file is written on one machine and
- * read on the next, and a locale-dependent order would silently rewrite the user's
- * sequence on a different machine for no reason they could see.
- */
-export declare function sortedPromptTitleOrder(prompts: readonly QuickPrompt[]): QuickPrompt[];

package/dist/prompts/search.js

@@ -1,146 +0,0 @@
-/**
- * Filtering and view ordering for the picker (quick-prompt-library D-9 / D-10).
- *
- * ASCII ONLY - `src/prompts/**` is inside `glyphs.test.ts::inScope`.
- *
- * SUBSEQUENCE MATCHING, NOT SUBSTRING MATCHING. `clr` should find `clean code
- * review`, and Chinese titles make the same demand in a different shape: the
- * characters a user remembers are rarely contiguous. The query is matched
- * case-insensitively against the title, then the tags, then the description, and
- * the FIELD a match landed in is a stronger signal than how good the match was.
- *
- * NO CHARACTER HIGHLIGHTING (D-10). Colouring the matched characters would mean
- * splitting a row into styled runs, and every row in this package is one
- * `wrap="truncate"` `<Text>` precisely so its height is exactly one row. The
- * detail block answers "why did this match" instead.
- */
-/** How much worse a match in tags, or in the description, is than in the title. */
-const TAG_PENALTY = 1_000;
-const DESCRIPTION_PENALTY = 2_000;
-/**
- * Greedy subsequence match; `null` when `query` is not a subsequence of `text`.
- *
- * The score is LOWER-is-better and is built from what a reader would actually
- * call a good match: how early the first hit is, how tightly the hits cluster,
- * and how many characters had to be skipped between them.
- */
-export function subsequenceScore(text, query) {
-    if (query.length === 0)
-        return 0;
-    const haystack = text.toLowerCase();
-    const needle = query.toLowerCase();
-    let at = 0;
-    let first = -1;
-    let last = -1;
-    let gaps = 0;
-    for (const char of needle) {
-        const hit = haystack.indexOf(char, at);
-        if (hit === -1)
-            return null;
-        if (first === -1)
-            first = hit;
-        else if (hit > last + 1)
-            gaps += hit - last - 1;
-        last = hit;
-        at = hit + 1;
-    }
-    const span = last - first + 1;
-    return first * 4 + gaps * 2 + (span - needle.length);
-}
-function fieldScore(prompt, query) {
-    const title = subsequenceScore(prompt.title, query);
-    if (title !== null)
-        return title;
-    let best = null;
-    for (const tag of prompt.tags ?? []) {
-        const score = subsequenceScore(tag, query);
-        if (score !== null && (best === null || score < best))
-            best = score;
-    }
-    if (best !== null)
-        return TAG_PENALTY + best;
-    const description = prompt.description;
-    if (description === undefined)
-        return null;
-    const score = subsequenceScore(description, query);
-    return score === null ? null : DESCRIPTION_PENALTY + score;
-}
-/**
- * Filter, but NEVER REORDER BEYOND WHAT THE QUERY EARNS.
- *
- * Ties keep the library's own order, because a filter that reshuffles entries with
- * equal scores makes the list move under the user's arrow keys while they type.
- * Favourites win ties, which is the only preference the picker states.
- */
-export function searchPrompts(prompts, query) {
-    const trimmed = query.trim();
-    if (trimmed.length === 0)
-        return prompts.map((prompt) => ({ prompt, score: 0 }));
-    const hits = [];
-    for (let at = 0; at < prompts.length; at += 1) {
-        const prompt = prompts[at];
-        const score = fieldScore(prompt, trimmed);
-        if (score !== null)
-            hits.push({ prompt, score, at });
-    }
-    hits.sort((a, b) => {
-        const favourite = (b.prompt.favorite === true ? 1 : 0) - (a.prompt.favorite === true ? 1 : 0);
-        if (favourite !== 0)
-            return favourite;
-        if (a.score !== b.score)
-            return a.score - b.score;
-        return a.at - b.at;
-    });
-    return hits.map(({ prompt, score }) => ({ prompt, score }));
-}
-/**
- * The three presentations (D-9).
- *
- * `manual` is the only persisted order; the other two are VANISHING views. The one
- * that rearranges is `favorite` - `recent` sorts by `lastUsedAt` only, so an entry
- * that has never been used keeps its place at the tail instead of jumping around
- * while the user watches.
- */
-export function viewOrder(prompts, view) {
-    if (view === 'manual')
-        return [...prompts];
-    const indexed = prompts.map((prompt, at) => ({ prompt, at }));
-    if (view === 'favorite') {
-        indexed.sort((a, b) => {
-            const favourite = (b.prompt.favorite === true ? 1 : 0) - (a.prompt.favorite === true ? 1 : 0);
-            return favourite !== 0 ? favourite : a.at - b.at;
-        });
-        return indexed.map(({ prompt }) => prompt);
-    }
-    indexed.sort((a, b) => {
-        const recent = (b.prompt.lastUsedAt ?? 0) - (a.prompt.lastUsedAt ?? 0);
-        return recent !== 0 ? recent : a.at - b.at;
-    });
-    return indexed.map(({ prompt }) => prompt);
-}
-/** The next view in the `Ctrl+S` cycle (manual -> recent -> favorite -> manual). */
-export function nextView(view) {
-    if (view === 'manual')
-        return 'recent';
-    if (view === 'recent')
-        return 'favorite';
-    return 'manual';
-}
-/**
- * Title order, for the `/prompts sort name` write.
- *
- * A TOTAL order (title, then id): a sort the user asked for has to be reproducible, and
- * two entries sharing a title would otherwise swap places between runs - a "sorted"
- * library that reorders itself on every read is worse than an unsorted one. Code-unit
- * comparison rather than `localeCompare`, because the file is written on one machine and
- * read on the next, and a locale-dependent order would silently rewrite the user's
- * sequence on a different machine for no reason they could see.
- */
-export function sortedPromptTitleOrder(prompts) {
-    const compare = (a, b) => {
-        if (a.title !== b.title)
-            return a.title < b.title ? -1 : 1;
-        return a.id < b.id ? -1 : a.id > b.id ? 1 : 0;
-    };
-    return [...prompts].sort(compare);
-}

package/dist/prompts/types.d.ts

@@ -1,204 +0,0 @@
-/**
- * The quick-prompt library's data model (quick-prompt-library §6.1).
- *
- * ASCII ONLY - `src/prompts/**` is inside `glyphs.test.ts::inScope`. Chinese copy
- * lives in `copy.ts` as `\uXXXX` escapes, never as literal text in this tree.
- *
- * THE DISK SHAPE IS THE ONLY TRUTH (D-3 / I-6). `App` holds a `PromptLibrary`
- * snapshot for rendering, every mutation goes through `store.ts`, and the store
- * hands the new snapshot back. No component computes an optimistic library of its
- * own, because "the UI says it was added and the disk disagrees" is a failure
- * mode with no error message.
- */
-/**
- * One entry.
- *
- * `useCount` / `createdAt` / `updatedAt` are ALWAYS present: a missing number
- * would make every consumer write `?? 0` and one of them would eventually forget.
- * `description` / `tags` / `favorite` / `lastUsedAt` are optional because "absent"
- * is their honest state.
- */
-export interface QuickPrompt {
-    /** `randomUUID()`. Never shown in full; the list uses an 8-character prefix. */
-    id: string;
-    /** 1..80 code points, trimmed, no control characters. Never empty (I-5). */
-    title: string;
-    /** 1..8000 code points. Original newlines preserved; `\r\n` normalised to `\n`. */
-    content: string;
-    /** 0..200 code points. */
-    description?: string;
-    /** 0..6 tags, each 0..24 code points. */
-    tags?: string[];
-    favorite?: boolean;
-    /** Monotonic per entry (I-4). */
-    useCount: number;
-    /** Epoch ms. */
-    createdAt: number;
-    updatedAt: number;
-    lastUsedAt?: number;
-}
-/**
- * The whole library.
- *
- * `prompts` IS the manual order (I-1): index 0 is what the list shows first and
- * what `Ctrl+Up/Down` rearranges. There is no `order` field, because a second
- * ordering authority is a second thing that can disagree with the first.
- */
-export interface PromptLibrary {
-    schema: 1;
-    prompts: QuickPrompt[];
-    /** Epoch ms of the last successful write; strictly increasing (I-3). */
-    updatedAt: number;
-}
-/**
- * The persistent re-orderings `/prompts sort <key>` can name (D-9).
- *
- * A WRITE key, not a view: `PromptSortView` is what the picker renders and never
- * persists, this is what the user may ask to have rewritten on disk. They overlap by two
- * words and are deliberately separate types, because "sort by recent" and "show me the
- * recent order for a moment" are different promises.
- */
-export type PromptSortKey = 'name' | 'recent' | 'favorite';
-/** The picker's three presentations. A VIEW: never persisted (D-9). */
-export type PromptSortView = 'manual' | 'recent' | 'favorite';
-/**
- * Why a write or a lookup failed. A stable code, never a sentence: the sentence
- * comes from `copy.ts`, so the same failure has one wording on every surface.
- */
-export type PromptWriteError = 'title_required' | 'content_required' | 'title_too_long' | 'content_too_long' | 'description_too_long' | 'tag_too_long' | 'too_many_tags' | 'too_many_prompts' | 'not_found' | 'ambiguous' | 'write_failed';
-/**
- * The result of one mutation.
- *
- * THE LIBRARY TRAVELS WITH THE FAILURE TOO, and that is deliberate: a
- * `write_failed` still applied in memory (D-4), so the caller has to be able to
- * render what the user just created rather than pretending nothing happened.
- */
-export type PromptMutationResult = {
-    ok: true;
-    library: PromptLibrary;
-    id?: string;
-} | {
-    ok: false;
-    code: PromptWriteError;
-    library: PromptLibrary;
-};
-/**
- * A one-shot hand-off into the manager overlay (D-21).
- *
- * `App` never edits the overlay's state directly; it hands over an intent, and the
- * overlay consumes it exactly once by nonce. That is what makes `/prompts edit 2`
- * land in the editor with a prefilled draft instead of on row 0 of the list.
- */
-export type PromptLibraryEntry = {
-    kind: 'list';
-    focusId?: string;
-} | {
-    kind: 'create';
-    seed?: {
-        title?: string;
-        content?: string;
-    };
-} | {
-    kind: 'edit';
-    id: string;
-} | {
-    kind: 'delete';
-    id: string;
-};
-/** `nonce` is monotonic; the same value is consumed at most once (I-8). */
-export interface PromptLibraryIntent {
-    nonce: number;
-    entry: PromptLibraryEntry;
-}
-/**
- * `<n|title>` resolved to an entry (D-22).
- *
- * `ambiguous` CARRIES ITS CANDIDATES. Titles may repeat (I-2), and a lookup that
- * failed without saying which entries matched would leave the user with nothing
- * to type next - which is exactly how `/prompts rm <title>` deletes the wrong
- * prompt, and there is no recycle bin (D-13).
- */
-export type PromptRefResolution = {
-    ok: true;
-    prompt: QuickPrompt;
-} | {
-    ok: false;
-    code: 'not_found';
-} | {
-    ok: false;
-    code: 'ambiguous';
-    candidates: QuickPrompt[];
-};
-/**
- * The editable form of one entry.
- *
- * `id: null` means "not saved yet". `tags` is the RAW field text: parsing it on
- * every keystroke would rewrite what the user is typing as they type it.
- */
-export interface PromptEditorDraft {
-    id: string | null;
-    title: string;
-    content: string;
-    description: string;
-    tags: string;
-    favorite: boolean;
-}
-/** The three things the manager overlay may ask the store to do (P2-1: idempotent). */
-export type PromptLibraryMutation = {
-    kind: 'create';
-    draft: PromptEditorDraft;
-} | {
-    kind: 'update';
-    id: string;
-    draft: PromptEditorDraft;
-} | {
-    kind: 'delete';
-    id: string;
-} | {
-    kind: 'move';
-    id: string;
-    delta: -1 | 1;
-} | {
-    kind: 'favorite';
-    id: string;
-    favorite: boolean;
-};
-/**
- * What a command (or the picker) may ask the host to do (§6.3 / P1-3).
- *
- * THREE METHODS, and each one is something the command layer genuinely cannot do
- * itself: open a surface, hand that surface a payload, or read the library through
- * the same resolver the user's typing is interpreted with. Everything else
- * (notifications, toasts, overlays in general) already exists on `CommandContext`
- * and is not repeated here.
- */
-export interface PromptCommandPort {
-    /** Open the picker (`overlay: 'prompt-pick'`). */
-    openPicker(): void;
-    /** Open the manager on a specific page, with an optional prefilled draft. */
-    openManager(entry: PromptLibraryEntry): void;
-    /** `<n|title>` -> entry, through `resolvePromptRef` (D-22). */
-    resolve(ref: string): PromptRefResolution;
-}
-/** A validated draft, ready for the store. Produced by `finishPromptEditor`. */
-export interface PromptDraftInput {
-    title: string;
-    content: string;
-    description?: string;
-    tags?: string[];
-    favorite?: boolean;
-}
-/**
- * The verdict of validating a draft (§4.4 / D-12).
- *
- * `field` is the row that should own focus after a refusal, so the editor can jump
- * there instead of leaving the user staring at a footer with an error code in it.
- */
-export type PromptDraftVerdict = {
-    ok: true;
-    input: PromptDraftInput;
-} | {
-    ok: false;
-    code: PromptWriteError;
-    field: 'title' | 'content' | 'description' | 'tags';
-};

package/dist/prompts/types.js

@@ -1,13 +0,0 @@
-/**
- * The quick-prompt library's data model (quick-prompt-library §6.1).
- *
- * ASCII ONLY - `src/prompts/**` is inside `glyphs.test.ts::inScope`. Chinese copy
- * lives in `copy.ts` as `\uXXXX` escapes, never as literal text in this tree.
- *
- * THE DISK SHAPE IS THE ONLY TRUTH (D-3 / I-6). `App` holds a `PromptLibrary`
- * snapshot for rendering, every mutation goes through `store.ts`, and the store
- * hands the new snapshot back. No component computes an optimistic library of its
- * own, because "the UI says it was added and the disk disagrees" is a failure
- * mode with no error message.
- */
-export {};

package/dist/team/activity.d.ts

@@ -1,67 +0,0 @@
-/**
- * Activity strings for the live roster (team-live-activity F-1).
- *
- * ASCII ONLY: `src/team/**` is inside the glyph scanner's scope. That rule binds
- * the LITERALS IN THIS FILE, not the runtime data flowing through it - a child
- * may well be reading a CJK path, and `run.description` already carries model
- * text into the same row.
- */
-/**
- * The only part of a tool call this module will ever render (P1-4).
- *
- * A PICKED SUBSET, NOT THE ARGS OBJECT. Storing `event.args` whole would put
- * `write_file`'s `content` - a whole file - on the run, and `TeamRuntime.publish`
- * shallow-copies the run into the live snapshot AND into every `agent_update`
- * event, and `dispatch()` copies it again into `DispatchOutcome.runs`, which
- * `TeamCard` holds in the transcript for the rest of the session. Two facts make
- * that unacceptable rather than merely wasteful: the retention is unbounded in
- * the file's size, and one `JSON.stringify` anywhere downstream would put a file
- * body into a log - the exact liability the logging section spends a paragraph
- * avoiding.
- *
- * This costs nothing in maintenance: the switch below is ALREADY a per-tool
- * table, so a new tool is one entry either way.
- */
-export interface ActivityArgs {
-    path?: string;
-    pattern?: string;
-    command?: string;
-    to?: string;
-    from?: string;
-}
-/** Pick at capture time. Called once per `tool_execution_start`. */
-export declare function pickActivityArgs(args: unknown): ActivityArgs;
-/**
- * Strip anything that could corrupt the frame, collapse whitespace, and clamp.
- *
- * THE CONTROL-CHARACTER STRIP IS A CORRECTNESS BOUNDARY, NOT TIDINESS. This
- * string is model-chosen and reaches an Ink <Text> unescaped. A child running
- * `bash` with an ANSI escape in the command line would otherwise write that
- * escape into the roster: at best a mangled row, at worst a cleared screen or a
- * moved cursor in the middle of someone's transcript. `bash`'s own output never
- * reaches the panel; its ARGUMENTS now do.
- *
- * SURROGATES ARE GUARDED AT BOTH ENDS (P2-3). The trailing guard is the obvious
- * one. The LEADING one is needed because the caller feeds this a rolling tail
- * built with `String.slice(-n)`, which cuts on a UTF-16 code-unit boundary and
- * can therefore hand us a lone LOW surrogate at index 0. Either half of a split
- * pair renders as a replacement character - the same failure `truncateBytes`
- * guards one layer down (report.ts).
- */
-export declare function sanitizeActivity(raw: string, maxChars: number): string;
-/**
- * One short phrase describing a tool call.
- *
- * `wide` false is the narrow-terminal form (D-4). For a path-valued argument
- * that is the basename; for `bash` it is the PROGRAM NAME (P1-6). Running the
- * command line through `basename` is wrong twice over: `basename` splits on `/`,
- * so `npm test -w cli` comes back whole and `./scripts/build.sh --prod` comes
- * back as `build.sh --prod`. Neither is shorter and the second is a lie about
- * what ran.
- *
- * Anything not in the table renders as its own name. That is the correct
- * degradation for `skill_find` and for any tool a later round registers on a
- * child: a name is always true, and inventing an argument mapping for a tool
- * this module has not been taught is how a formatter starts lying.
- */
-export declare function describeToolActivity(toolName: string, args: ActivityArgs | undefined, wide: boolean): string;

package/dist/team/activity.js

@@ -1,130 +0,0 @@
-/**
- * Activity strings for the live roster (team-live-activity F-1).
- *
- * ASCII ONLY: `src/team/**` is inside the glyph scanner's scope. That rule binds
- * the LITERALS IN THIS FILE, not the runtime data flowing through it - a child
- * may well be reading a CJK path, and `run.description` already carries model
- * text into the same row.
- */
-import { TEAM_LIMITS } from './limits.js';
-/** Pick at capture time. Called once per `tool_execution_start`. */
-export function pickActivityArgs(args) {
-    const a = (args ?? {});
-    const str = (v) => typeof v === 'string' && v.length > 0 ? v.slice(0, TEAM_LIMITS.activityArgChars) : undefined;
-    const picked = {};
-    const path = str(a.path);
-    const pattern = str(a.pattern);
-    const command = str(a.command);
-    const to = str(a.to);
-    const from = str(a.from);
-    if (path !== undefined)
-        picked.path = path;
-    if (pattern !== undefined)
-        picked.pattern = pattern;
-    if (command !== undefined)
-        picked.command = command;
-    if (to !== undefined)
-        picked.to = to;
-    if (from !== undefined)
-        picked.from = from;
-    return picked;
-}
-/**
- * Strip anything that could corrupt the frame, collapse whitespace, and clamp.
- *
- * THE CONTROL-CHARACTER STRIP IS A CORRECTNESS BOUNDARY, NOT TIDINESS. This
- * string is model-chosen and reaches an Ink <Text> unescaped. A child running
- * `bash` with an ANSI escape in the command line would otherwise write that
- * escape into the roster: at best a mangled row, at worst a cleared screen or a
- * moved cursor in the middle of someone's transcript. `bash`'s own output never
- * reaches the panel; its ARGUMENTS now do.
- *
- * SURROGATES ARE GUARDED AT BOTH ENDS (P2-3). The trailing guard is the obvious
- * one. The LEADING one is needed because the caller feeds this a rolling tail
- * built with `String.slice(-n)`, which cuts on a UTF-16 code-unit boundary and
- * can therefore hand us a lone LOW surrogate at index 0. Either half of a split
- * pair renders as a replacement character - the same failure `truncateBytes`
- * guards one layer down (report.ts).
- */
-export function sanitizeActivity(raw, maxChars) {
-    let src = raw;
-    const head = src.charCodeAt(0);
-    if (head >= 0xdc00 && head <= 0xdfff)
-        src = src.slice(1);
-    const flat = src
-        // eslint-disable-next-line no-control-regex
-        .replace(/[\x00-\x1f\x7f]/g, ' ')
-        .replace(/\s+/g, ' ')
-        .trim();
-    if (maxChars <= 0)
-        return '';
-    if (flat.length <= maxChars)
-        return flat;
-    if (maxChars <= 3)
-        return flat.slice(0, maxChars);
-    let cut = maxChars - 3;
-    const code = flat.charCodeAt(cut - 1);
-    if (code >= 0xd800 && code <= 0xdbff)
-        cut -= 1;
-    return `${flat.slice(0, cut)}...`;
-}
-/** The basename of a path, for the narrow form. Pure string work: no `path`. */
-function basename(p) {
-    const parts = p.split(/[\\/]/);
-    return parts[parts.length - 1] || p;
-}
-/** The program name of a command line, for the narrow form. */
-function program(commandLine) {
-    const first = commandLine.trim().split(/\s+/)[0] ?? '';
-    return basename(first) || commandLine;
-}
-/**
- * One short phrase describing a tool call.
- *
- * `wide` false is the narrow-terminal form (D-4). For a path-valued argument
- * that is the basename; for `bash` it is the PROGRAM NAME (P1-6). Running the
- * command line through `basename` is wrong twice over: `basename` splits on `/`,
- * so `npm test -w cli` comes back whole and `./scripts/build.sh --prod` comes
- * back as `build.sh --prod`. Neither is shorter and the second is a lie about
- * what ran.
- *
- * Anything not in the table renders as its own name. That is the correct
- * degradation for `skill_find` and for any tool a later round registers on a
- * child: a name is always true, and inventing an argument mapping for a tool
- * this module has not been taught is how a formatter starts lying.
- */
-export function describeToolActivity(toolName, args, wide) {
-    const a = args ?? {};
-    switch (toolName) {
-        case 'read_file':
-            return detail('read', a.path, wide, basename);
-        case 'write_file':
-            return detail('write', a.path, wide, basename);
-        case 'edit_file':
-            return detail('edit', a.path, wide, basename);
-        case 'list_dir':
-            return detail('list', a.path ?? '.', wide, basename);
-        case 'glob':
-            return detail('glob', a.pattern, wide, basename);
-        case 'grep':
-            return detail('grep', a.pattern, wide, basename);
-        case 'bash':
-            return detail('bash', a.command, wide, program);
-        case 'team_send': {
-            const to = (a.to ?? '').trim();
-            return to ? `messaging ${to}` : 'messaging';
-        }
-        case 'team_wait': {
-            const from = (a.from ?? '').trim();
-            return from ? `waiting for ${from}` : 'waiting for mail';
-        }
-        default:
-            return toolName;
-    }
-}
-function detail(verb, value, wide, narrow) {
-    const v = (value ?? '').trim();
-    if (v.length === 0)
-        return verb;
-    return `${verb}: ${wide ? v : narrow(v)}`;
-}