@aragon-agent/cli 0.6.47 → 0.6.48

package/dist/fast/limits.d.ts

@@ -1,152 +0,0 @@
-/**
- * FAST_LIMITS — the single authority on every bound the fast tier enforces
- * (fast-model-tier §5.5).
- *
- * ASCII ONLY: `src/fast/**` is inside the glyph scanner's scope
- * (`glyphs.test.ts`), so no literal in this tree may hold a non-ASCII byte. The
- * regex there is a hardcoded directory list, which is why adding this tree and
- * adding `fast` to that list are the SAME change (C-4 / AC-27) - a scanner that
- * silently stops scanning is worse than no scanner.
- *
- * TWO KINDS OF NUMBER, AND THEY ARE NOT INTERCHANGEABLE - the distinction
- * `TEAM_LIMITS` and `TODO_LIMITS` both state:
- *
- *  - The entries below are STRUCTURAL. They describe what a review call, a
- *    digest and a card can physically carry. A user has no business tuning them.
- *  - The ten `fast.*` keys in `config/schema.ts` are POLICY: which model, how
- *    often, how long a critique may be. Those are clamped, persisted and
- *    user-facing.
- *
- * `reviewMaxChars` therefore lives in the CONFIG and not here: it is the one
- * number whose right value depends on how much of their own context the user is
- * willing to spend on advice. `reviewOutputTokens` stays here because 512 tokens
- * is a bound on a protocol, not a preference.
- */
-export declare const FAST_LIMITS: {
-    /**
-     * The flat input cost of one review (D-6 / R-2).
-     *
-     * THIS NUMBER IS THE WHOLE ECONOMIC ARGUMENT. The reviewer builds its own
-     * bounded frame ring and never reads `agent.state.messages`, which after four
-     * 60 KB file reads carries 240 KB of file bodies; shipping that to the "cheap"
-     * model would make a review cost MORE than the turn it is reviewing.
-     */
-    readonly digestMaxChars: 4000;
-    /** The user's request for the run, clamped. Without it the reviewer is asked
-     *  whether work is on track without being told what the track is. */
-    readonly goalChars: 500;
-    /** Per-frame assistant-text tail. Rolling, clipped on every append. */
-    readonly turnTailChars: 600;
-    /** Per picked tool argument. Mirrors `TEAM_LIMITS.activityArgChars`. */
-    readonly toolArgChars: 120;
-    /** Frames kept per run. `>=` the max of `reviewContextTurns`, with slack. */
-    readonly maxFramesRetained: 12;
-    /** Hard cap on the review's own output. */
-    readonly reviewOutputTokens: 512;
-    /**
-     * Wall-clock budget for ONE review call INCLUDING RETRIES (D-H11).
-     *
-     * THE BUDGET HAS TWO TERMS AND ONLY ONE OF THEM SHRANK. Round 1 set 30 s as
-     * IF-3's fallback: `ProviderRegistry.complete()` routed through a retrying
-     * `stream()` with `maxRetries: 10`, so the budget covered
-     * `attempts x (call + backoff)`. Round 2 gives the reviewer its own
-     * `maxRetries: 1` registry (`wiring.ts`), which collapses that term to about
-     * one call plus a one-second backoff - but it does nothing at all to the
-     * other term, THE FAST MODEL'S OWN GENERATION LATENCY. The review asks for up
-     * to `reviewOutputTokens` from a `digestMaxChars` prompt, and the tier is by
-     * construction pointed at the cheapest endpoint the user has: the population
-     * where a 15-25 s completion is ordinary rather than pathological.
-     *
-     * SO THIS IS 20 000 AND NOT 12 000. A timeout IS a strike (see `runReview`),
-     * and `maxConsecutiveFailures` is 3, so a 12 s bound would convert "slow but
-     * healthy provider" into a tier that self-disables for the session and
-     * reports itself as MISCONFIGURED - the one register D-24 reserves for faults
-     * that never self-heal, spent on one that does. 20 s keeps a margin over a
-     * slow completion and still cuts a stuck review's occupancy of the
-     * single-flight slot by a third. Lower it only with a measured p99, which
-     * `manual-test.md` row 6 exists to produce.
-     */
-    readonly reviewTimeoutMs: 20000;
-    /** Reviews STARTED per run. A 40-turn run at cadence 5 would otherwise buy 8
-     *  critiques the lead increasingly ignores. */
-    readonly maxReviewsPerRun: 6;
-    /** Consecutive NON-TRANSIENT failures before the reviewer self-disables. */
-    readonly maxConsecutiveFailures: 3;
-    /**
-     * A critique waiting for its injection window goes stale (RV-12).
-     *
-     * The window is not guaranteed to be prompt: one `task` dispatch is a single
-     * tool call that can run for as long as its children need, so a critique triggered
-     * just before one arrives at the far side describing a state five children
-     * have since rewritten. Advice that is merely late is worse than no advice,
-     * because the lead cannot tell that it is late.
-     */
-    readonly pendingMaxAgeMs: 120000;
-    /** ... or is overtaken by the run itself, in turns. */
-    readonly pendingMaxTurnsBehind: 2;
-    /** Rows the transcript card renders before eliding. */
-    readonly cardTextRows: 4;
-    /** Below this many columns the status chip drops (D-20's treatment, not
-     *  `agentMode`'s - the guaranteed reporting surface is `/fast status`). */
-    readonly statusCompactCols: 100;
-};
-/**
- * Bumped whenever the wording of `<fast_tier>` or the review system prompt
- * changes, so a behaviour report can be tied to a block revision with one grep -
- * exactly what `TEAM_BLOCK_VERSION` and `TODO_BLOCK_VERSION` are for.
- */
-export declare const FAST_BLOCK_VERSION = "v2-2026-10";
-/**
- * The bounds one task-summary label may consume
- * (tui-shortcut-drawer-and-task-summary D-11).
- *
- * STRUCTURAL, NOT POLICY, for the reason this file's header records: these say
- * what a one-line header label can PHYSICALLY carry, not what the user prefers.
- * The two user switches (`taskSummary.enabled` / `.fallback`) live in
- * `config/schema.ts` and are not interchangeable with these.
- *
- * THE THREE CAPS HAVE THREE DIFFERENT JOBS, and v1 left that implicit (P1-8):
- *
- *  - GENERATION (the system prompt in `summary-prompt.ts`): at most 6 words in
- *    space-separated languages, at most 12 characters in CJK. The normal path is
- *    constrained by this and by nothing else.
- *  - NORMALISATION (`normalizeTaskSummary`): `summaryMaxWords` and
- *    `cjkMaxGraphemes` are applied first, then `summaryMaxChars` catches the one
- *    case those two cannot - a long run with no whitespace. That order is
- *    asserted by `task-summary-normalize.test.ts`.
- *  - RENDERING: `maxCells` is the hard ceiling on the header cell. The header
- *    fits within whatever width is left; the drawer WRAPS instead of cutting.
- */
-export declare const TASK_SUMMARY_LIMITS: {
-    /** Hard cap on the call's own output. A label is not a paragraph. */
-    readonly outputTokens: 64;
-    /**
-     * Wall-clock budget for ONE summary call, INCLUDING the fast registry's single
-     * retry. Short on purpose: the label is decoration on the header row, and a
-     * user waiting for the first token must never wait on it - the call is fired
-     * after `prompt()` has been started and nothing awaits it (AC-13).
-     */
-    readonly timeoutMs: 8000;
-    /** How much of the user's message is sent. Long prompts are summarised from the head. */
-    readonly anchorMaxChars: 2000;
-    /** Storage ceiling. Only ever reached by a model that ignored the prompt rules. */
-    readonly summaryMaxChars: 60;
-    /** Space-separated languages: the label is at most this many words. */
-    readonly summaryMaxWords: 8;
-    /** CJK: the label is at most this many grapheme clusters. */
-    readonly cjkMaxGraphemes: 12;
-    /**
-     * The header cell's hard ceiling in terminal COLUMNS (not characters).
-     *
-     * Shared by `ui/layout/header-left.ts` and the drawer so the two cannot
-     * disagree about how wide a label is allowed to be. v1 referenced this
-     * constant without defining it (P1-8).
-     */
-    readonly maxCells: 28;
-};
-/**
- * Bumped whenever the task-summary system prompt's wording changes, so a
- * behaviour report can be tied to a revision with one grep - the same purpose
- * `FAST_BLOCK_VERSION` serves for the review prompt.
- */
-export declare const TASK_SUMMARY_PROMPT_VERSION = "v1-2026-10";

package/dist/fast/limits.js

@@ -1,152 +0,0 @@
-/**
- * FAST_LIMITS — the single authority on every bound the fast tier enforces
- * (fast-model-tier §5.5).
- *
- * ASCII ONLY: `src/fast/**` is inside the glyph scanner's scope
- * (`glyphs.test.ts`), so no literal in this tree may hold a non-ASCII byte. The
- * regex there is a hardcoded directory list, which is why adding this tree and
- * adding `fast` to that list are the SAME change (C-4 / AC-27) - a scanner that
- * silently stops scanning is worse than no scanner.
- *
- * TWO KINDS OF NUMBER, AND THEY ARE NOT INTERCHANGEABLE - the distinction
- * `TEAM_LIMITS` and `TODO_LIMITS` both state:
- *
- *  - The entries below are STRUCTURAL. They describe what a review call, a
- *    digest and a card can physically carry. A user has no business tuning them.
- *  - The ten `fast.*` keys in `config/schema.ts` are POLICY: which model, how
- *    often, how long a critique may be. Those are clamped, persisted and
- *    user-facing.
- *
- * `reviewMaxChars` therefore lives in the CONFIG and not here: it is the one
- * number whose right value depends on how much of their own context the user is
- * willing to spend on advice. `reviewOutputTokens` stays here because 512 tokens
- * is a bound on a protocol, not a preference.
- */
-export const FAST_LIMITS = {
-    /**
-     * The flat input cost of one review (D-6 / R-2).
-     *
-     * THIS NUMBER IS THE WHOLE ECONOMIC ARGUMENT. The reviewer builds its own
-     * bounded frame ring and never reads `agent.state.messages`, which after four
-     * 60 KB file reads carries 240 KB of file bodies; shipping that to the "cheap"
-     * model would make a review cost MORE than the turn it is reviewing.
-     */
-    digestMaxChars: 4_000,
-    /** The user's request for the run, clamped. Without it the reviewer is asked
-     *  whether work is on track without being told what the track is. */
-    goalChars: 500,
-    /** Per-frame assistant-text tail. Rolling, clipped on every append. */
-    turnTailChars: 600,
-    /** Per picked tool argument. Mirrors `TEAM_LIMITS.activityArgChars`. */
-    toolArgChars: 120,
-    /** Frames kept per run. `>=` the max of `reviewContextTurns`, with slack. */
-    maxFramesRetained: 12,
-    /** Hard cap on the review's own output. */
-    reviewOutputTokens: 512,
-    /**
-     * Wall-clock budget for ONE review call INCLUDING RETRIES (D-H11).
-     *
-     * THE BUDGET HAS TWO TERMS AND ONLY ONE OF THEM SHRANK. Round 1 set 30 s as
-     * IF-3's fallback: `ProviderRegistry.complete()` routed through a retrying
-     * `stream()` with `maxRetries: 10`, so the budget covered
-     * `attempts x (call + backoff)`. Round 2 gives the reviewer its own
-     * `maxRetries: 1` registry (`wiring.ts`), which collapses that term to about
-     * one call plus a one-second backoff - but it does nothing at all to the
-     * other term, THE FAST MODEL'S OWN GENERATION LATENCY. The review asks for up
-     * to `reviewOutputTokens` from a `digestMaxChars` prompt, and the tier is by
-     * construction pointed at the cheapest endpoint the user has: the population
-     * where a 15-25 s completion is ordinary rather than pathological.
-     *
-     * SO THIS IS 20 000 AND NOT 12 000. A timeout IS a strike (see `runReview`),
-     * and `maxConsecutiveFailures` is 3, so a 12 s bound would convert "slow but
-     * healthy provider" into a tier that self-disables for the session and
-     * reports itself as MISCONFIGURED - the one register D-24 reserves for faults
-     * that never self-heal, spent on one that does. 20 s keeps a margin over a
-     * slow completion and still cuts a stuck review's occupancy of the
-     * single-flight slot by a third. Lower it only with a measured p99, which
-     * `manual-test.md` row 6 exists to produce.
-     */
-    reviewTimeoutMs: 20_000,
-    /** Reviews STARTED per run. A 40-turn run at cadence 5 would otherwise buy 8
-     *  critiques the lead increasingly ignores. */
-    maxReviewsPerRun: 6,
-    /** Consecutive NON-TRANSIENT failures before the reviewer self-disables. */
-    maxConsecutiveFailures: 3,
-    /**
-     * A critique waiting for its injection window goes stale (RV-12).
-     *
-     * The window is not guaranteed to be prompt: one `task` dispatch is a single
-     * tool call that can run for as long as its children need, so a critique triggered
-     * just before one arrives at the far side describing a state five children
-     * have since rewritten. Advice that is merely late is worse than no advice,
-     * because the lead cannot tell that it is late.
-     */
-    pendingMaxAgeMs: 120_000,
-    /** ... or is overtaken by the run itself, in turns. */
-    pendingMaxTurnsBehind: 2,
-    /** Rows the transcript card renders before eliding. */
-    cardTextRows: 4,
-    /** Below this many columns the status chip drops (D-20's treatment, not
-     *  `agentMode`'s - the guaranteed reporting surface is `/fast status`). */
-    statusCompactCols: 100,
-};
-/**
- * Bumped whenever the wording of `<fast_tier>` or the review system prompt
- * changes, so a behaviour report can be tied to a block revision with one grep -
- * exactly what `TEAM_BLOCK_VERSION` and `TODO_BLOCK_VERSION` are for.
- */
-export const FAST_BLOCK_VERSION = 'v2-2026-10';
-/**
- * The bounds one task-summary label may consume
- * (tui-shortcut-drawer-and-task-summary D-11).
- *
- * STRUCTURAL, NOT POLICY, for the reason this file's header records: these say
- * what a one-line header label can PHYSICALLY carry, not what the user prefers.
- * The two user switches (`taskSummary.enabled` / `.fallback`) live in
- * `config/schema.ts` and are not interchangeable with these.
- *
- * THE THREE CAPS HAVE THREE DIFFERENT JOBS, and v1 left that implicit (P1-8):
- *
- *  - GENERATION (the system prompt in `summary-prompt.ts`): at most 6 words in
- *    space-separated languages, at most 12 characters in CJK. The normal path is
- *    constrained by this and by nothing else.
- *  - NORMALISATION (`normalizeTaskSummary`): `summaryMaxWords` and
- *    `cjkMaxGraphemes` are applied first, then `summaryMaxChars` catches the one
- *    case those two cannot - a long run with no whitespace. That order is
- *    asserted by `task-summary-normalize.test.ts`.
- *  - RENDERING: `maxCells` is the hard ceiling on the header cell. The header
- *    fits within whatever width is left; the drawer WRAPS instead of cutting.
- */
-export const TASK_SUMMARY_LIMITS = {
-    /** Hard cap on the call's own output. A label is not a paragraph. */
-    outputTokens: 64,
-    /**
-     * Wall-clock budget for ONE summary call, INCLUDING the fast registry's single
-     * retry. Short on purpose: the label is decoration on the header row, and a
-     * user waiting for the first token must never wait on it - the call is fired
-     * after `prompt()` has been started and nothing awaits it (AC-13).
-     */
-    timeoutMs: 8_000,
-    /** How much of the user's message is sent. Long prompts are summarised from the head. */
-    anchorMaxChars: 2_000,
-    /** Storage ceiling. Only ever reached by a model that ignored the prompt rules. */
-    summaryMaxChars: 60,
-    /** Space-separated languages: the label is at most this many words. */
-    summaryMaxWords: 8,
-    /** CJK: the label is at most this many grapheme clusters. */
-    cjkMaxGraphemes: 12,
-    /**
-     * The header cell's hard ceiling in terminal COLUMNS (not characters).
-     *
-     * Shared by `ui/layout/header-left.ts` and the drawer so the two cannot
-     * disagree about how wide a label is allowed to be. v1 referenced this
-     * constant without defining it (P1-8).
-     */
-    maxCells: 28,
-};
-/**
- * Bumped whenever the task-summary system prompt's wording changes, so a
- * behaviour report can be tied to a revision with one grep - the same purpose
- * `FAST_BLOCK_VERSION` serves for the review prompt.
- */
-export const TASK_SUMMARY_PROMPT_VERSION = 'v1-2026-10';

package/dist/fast/resolve.d.ts

@@ -1,44 +0,0 @@
-/**
- * `resolveFastTier` — THE single authority on whether a fast tier exists and
- * what it points at (fast-model-tier §3.2).
- *
- * ASCII ONLY: `src/fast/**` is inside the glyph scanner's scope.
- *
- * EVERY CONSUMER READS THE TIER THROUGH THIS FUNCTION AND NOWHERE ELSE - the
- * controller, the subagent factory, the reviewer, `/fast`, the settings screen
- * and the status bar. Four call sites recomputing "is fast usable?" from raw
- * config keys is exactly how a UI ends up showing a chip for a tier that refuses
- * every call.
- *
- * IT IS ALSO RE-RUN ON EVERY CONFIG MUTATION, NOT ONCE (rule 8 / RV-3). Rules 2
- * and 6 make `fast.provider: ''` and `fast.baseUrl: ''` INHERIT from
- * `config.provider` / `config.baseUrl`, and rule 5 reads `apiKeys`. All of those
- * are live: `/model`, `/provider`, the settings screen's save, `/reload` and a
- * one-shot key edit each rewrite one of them mid-session. A tier resolved once
- * at construction is a tier that can be describing a provider the session no
- * longer uses.
- */
-import type { ModelRole } from '../config/model-profiles.js';
-import { type CliConfig } from '../config/schema.js';
-import type { FastTier } from './types.js';
-/**
- * Resolve the fast tier from the CURRENT config.
- *
- * @param config The live effective config. Read fresh; never snapshot it.
- * @param hasKey `AgentController.hasApiKey`, which already resolves the
- *   config-file key, the provider environment variable and the one-shot
- *   `--api-key` override. Injected rather than reimplemented, because a second
- *   key resolver is a second answer to "why does it say no key?".
- */
-export declare function resolveFastTier(config: CliConfig, hasKey: (providerId: string, role?: ModelRole) => boolean): FastTier;
-/**
- * The one-line notice for a tier the user switched on that cannot resolve, or
- * `null` when there is nothing worth saying.
- *
- * `disabled` returns `null` - the tier being off because the user left it off is
- * not news. The other three are CONFIGURATION MISTAKES that are otherwise
- * completely invisible: nothing else in the session would ever mention them.
- */
-export declare function describeFastTierProblem(tier: FastTier, provider: string): string | null;
-/** The provider a tier resolution was about, for the notice above. */
-export declare function fastProviderOf(config: CliConfig): string;

package/dist/fast/resolve.js

@@ -1,107 +0,0 @@
-/**
- * `resolveFastTier` — THE single authority on whether a fast tier exists and
- * what it points at (fast-model-tier §3.2).
- *
- * ASCII ONLY: `src/fast/**` is inside the glyph scanner's scope.
- *
- * EVERY CONSUMER READS THE TIER THROUGH THIS FUNCTION AND NOWHERE ELSE - the
- * controller, the subagent factory, the reviewer, `/fast`, the settings screen
- * and the status bar. Four call sites recomputing "is fast usable?" from raw
- * config keys is exactly how a UI ends up showing a chip for a tier that refuses
- * every call.
- *
- * IT IS ALSO RE-RUN ON EVERY CONFIG MUTATION, NOT ONCE (rule 8 / RV-3). Rules 2
- * and 6 make `fast.provider: ''` and `fast.baseUrl: ''` INHERIT from
- * `config.provider` / `config.baseUrl`, and rule 5 reads `apiKeys`. All of those
- * are live: `/model`, `/provider`, the settings screen's save, `/reload` and a
- * one-shot key edit each rewrite one of them mid-session. A tier resolved once
- * at construction is a tier that can be describing a provider the session no
- * longer uses.
- */
-import { isAdapterProvider } from '../config/schema.js';
-/**
- * Resolve the fast tier from the CURRENT config.
- *
- * @param config The live effective config. Read fresh; never snapshot it.
- * @param hasKey `AgentController.hasApiKey`, which already resolves the
- *   config-file key, the provider environment variable and the one-shot
- *   `--api-key` override. Injected rather than reimplemented, because a second
- *   key resolver is a second answer to "why does it say no key?".
- */
-export function resolveFastTier(config, hasKey) {
-    const fast = config.fast;
-    // 1. The switch.
-    if (!fast || fast.enabled !== true)
-        return { ok: false, reason: 'disabled' };
-    // 2. An empty provider INHERITS the main one. This is what makes `fast.model`
-    //    alone a complete configuration for the overwhelmingly common case ("same
-    //    vendor, cheaper model").
-    const provider = fast.provider.trim().length > 0 ? fast.provider.trim() : config.provider;
-    // 3. An empty model is NOT CONFIGURED, and deliberately does not inherit
-    //    (D-4). Silently falling back to the main model would make R-e - opting in
-    //    to fast == main, which is legal - indistinguishable from a typo.
-    const modelId = fast.model.trim();
-    if (modelId.length === 0)
-        return { ok: false, reason: 'no_model' };
-    // 4 / 5. Both are reported separately because they send the user to two
-    //        different settings.
-    if (!isAdapterProvider(provider))
-        return { ok: false, reason: 'no_adapter' };
-    if (!hasKey(provider, 'fast'))
-        return { ok: false, reason: 'no_key' };
-    // 6. A fast tier on the SAME provider inherits the session's base URL: a user
-    //    pointing the CLI at a gateway means both models, not one. A fast tier on
-    //    a DIFFERENT provider does not, because that base URL belongs to another
-    //    API and would be an immediate 404.
-    const explicitBaseUrl = fast.baseUrl.trim();
-    const baseUrl = explicitBaseUrl.length > 0
-        ? explicitBaseUrl
-        : config.modelProfiles?.fastId && !config.modelProfileState?.fast.invalid
-            ? undefined
-            : provider === config.provider
-                ? config.baseUrl
-                : undefined;
-    const ref = {
-        providerId: provider,
-        modelId,
-        ...(baseUrl ? { baseUrl } : {}),
-    };
-    return {
-        ok: true,
-        ref,
-        thinkingLevel: fast.thinkingLevel,
-        // 7. DISPLAY ONLY, and no branch anywhere may read it (R-13). "The two tiers
-        //    resolve to the same model, so skip the work" is the tempting
-        //    optimization that silently turns R-e into a no-op: the user is allowed
-        //    to choose it, and the cost of the review is real either way.
-        sameAsMain: provider === config.provider && modelId === config.model,
-    };
-}
-/**
- * The one-line notice for a tier the user switched on that cannot resolve, or
- * `null` when there is nothing worth saying.
- *
- * `disabled` returns `null` - the tier being off because the user left it off is
- * not news. The other three are CONFIGURATION MISTAKES that are otherwise
- * completely invisible: nothing else in the session would ever mention them.
- */
-export function describeFastTierProblem(tier, provider) {
-    if (tier.ok)
-        return null;
-    switch (tier.reason) {
-        case 'no_model':
-            return 'fast.enabled is on but fast.model is empty - the fast tier is off. ' +
-                'Set it with /fast model <id>.';
-        case 'no_adapter':
-            return `Provider "${provider}" has no adapter - the fast tier is off.`;
-        case 'no_key':
-            return `No API key for ${provider} - the fast tier is off.`;
-        default:
-            return null;
-    }
-}
-/** The provider a tier resolution was about, for the notice above. */
-export function fastProviderOf(config) {
-    const explicit = config.fast?.provider.trim() ?? '';
-    return explicit.length > 0 ? explicit : config.provider;
-}

package/dist/fast/task-summary-types.d.ts

@@ -1,66 +0,0 @@
-/**
- * The task-summary types (tui-shortcut-drawer-and-task-summary §6.1).
- *
- * ASCII ONLY: `src/fast/**` is inside the glyph scanner's scope.
- *
- * WHY THIS FILE EXISTS AT ALL (v2 P1-3). `fast/summary-call.ts` and
- * `fast/summary-prompt.ts` produce and consume these shapes, and the header cell,
- * the reducer and the controller only display them. Declaring them in
- * `agent/controller.ts` - the v1 plan - would make `fast/` import `agent/` while
- * `agent/` imports `fast/`, and `.claude-index/config.md` already records one
- * real cycle in this package (`agent <-> compaction`). One more is not a style
- * question: a cycle makes the import graph unusable for ordering, and it is
- * exactly what `shortcut-table.test.ts` scans for. So the types live DOWN here,
- * in the lowest layer that needs them, and `agent/**` reaches them with
- * `import type` only.
- */
-/** How the label was produced. `fallback` is the user's own words, never a guess. */
-export type TaskSummaryTone = 'model' | 'fallback';
-/**
- * The dominant character class of a string, by letter majority.
- *
- * A NAMED UNION rather than the free-form `Script` v1 mentioned (and never
- * defined, P1-8). Only three answers are actionable: the label must be CJK, must
- * be Latin, or is neither (a prompt in Cyrillic, or only punctuation).
- */
-export type TaskSummarySpan = 'cjk' | 'latin' | 'other';
-/**
- * Why a label is what it is.
- *
- * THE FIRST NINE VALUES ALL MEAN "the model did not give us a label" and every
- * one of them converges on the SAME deterministic floor (D-9); they are kept
- * apart only so the drawer and `/task` can say which one happened. `empty` is
- * the tenth and means there was no floor to show either (fallback disabled).
- */
-export type TaskSummaryReason = 'tier-off' | 'no-model' | 'no-adapter' | 'no-key' | 'timeout' | 'aborted' | 'error' | 'bad-output' | 'language-mismatch' | 'empty';
-/**
- * The one task label a session has, as the header and the drawer read it.
- *
- * A PURE VIEW: it is never persisted, never enters the conversation history and
- * never touches `config.json` (§0-2). Everything a surface needs to explain the
- * label without a second lookup is on this record.
- */
-export interface TaskSummaryView {
-    /** Normalised, width-safe, at most `TASK_SUMMARY_LIMITS.maxCells` columns. */
-    text: string;
-    tone: TaskSummaryTone;
-    /** `null` exactly when `tone === 'model'`. */
-    reason: TaskSummaryReason | null;
-    /** The anchor's dominant script, so the drawer can disclose a mismatch. */
-    script: TaskSummarySpan;
-    /** Epoch ms of the attempt. The drawer renders `12s ago` from it, no clock of its own. */
-    at: number;
-    /** `provider:model` that produced it; `''` for a fallback. */
-    by: string;
-}
-/**
- * What one attempt produced.
- *
- * `view: null` happens in exactly one case: the call failed AND
- * `taskSummary.fallback` is false. That is a deliberate "show nothing" rather
- * than an empty string, because an empty header cell would read as a broken
- * feature (D-9).
- */
-export interface TaskSummaryOutcome {
-    view: TaskSummaryView | null;
-}

package/dist/fast/task-summary-types.js

@@ -1,17 +0,0 @@
-/**
- * The task-summary types (tui-shortcut-drawer-and-task-summary §6.1).
- *
- * ASCII ONLY: `src/fast/**` is inside the glyph scanner's scope.
- *
- * WHY THIS FILE EXISTS AT ALL (v2 P1-3). `fast/summary-call.ts` and
- * `fast/summary-prompt.ts` produce and consume these shapes, and the header cell,
- * the reducer and the controller only display them. Declaring them in
- * `agent/controller.ts` - the v1 plan - would make `fast/` import `agent/` while
- * `agent/` imports `fast/`, and `.claude-index/config.md` already records one
- * real cycle in this package (`agent <-> compaction`). One more is not a style
- * question: a cycle makes the import graph unusable for ordering, and it is
- * exactly what `shortcut-table.test.ts` scans for. So the types live DOWN here,
- * in the lowest layer that needs them, and `agent/**` reaches them with
- * `import type` only.
- */
-export {};