@aragon-agent/cli 0.6.47 → 0.6.48

package/dist/ui/overlays/ShortcutPanel.d.ts

@@ -1,39 +0,0 @@
-/**
- * The keyboard drawer (tui-shortcut-drawer-and-task-summary §4.5).
- *
- * ASCII ONLY: `src/ui/**` is inside `glyphs.test.ts::inScope`.
- *
- * IT OWNS NO CHROME AND NO ARITHMETIC. `OverlayFrame` draws the frame, the
- * window and the position indicator; `shortcut-panel-layout.ts` decides the
- * columns, the rows and which window contains the cursor. This component adds two
- * things and nothing else: its own key handling and the text-run colours. v1
- * planned 260 lines that re-implemented the frame's windowing and clamping - a
- * second source of truth for the one thing overlays have already been rewritten
- * once to unify.
- *
- * IT DOES NOT REGISTER `Esc` AND DOES NOT TOUCH ANY `ctrl`/`meta` COMBINATION:
- * `Esc` belongs to `App` (it closes every overlay and cancels the pending
- * question/plan), and `Ctrl+G` is handled there too. Two listeners both acting on
- * one byte is how a panel closes twice.
- */
-import React from 'react';
-import type { Theme } from '../theme.js';
-import type { TermCapabilities } from '../capabilities.js';
-import { type ShortcutTaskSection } from '../layout/shortcut-panel-layout.js';
-export interface ShortcutPanelProps {
-    /** The terminal width, which is what `OverlayFrame` needs to pick its form. */
-    cols: number;
-    maxRows: number;
-    theme: Theme;
-    caps: TermCapabilities;
-    isActive: boolean;
-    native: boolean;
-    running: boolean;
-    /** `/keys <query>` pre-filter. */
-    query?: string;
-    task: ShortcutTaskSection;
-    detailsExpanded: boolean;
-    onToggleDetails(): void;
-    onRefresh(): void;
-}
-export declare function ShortcutPanel(props: ShortcutPanelProps): React.ReactElement;

package/dist/ui/overlays/ShortcutPanel.js

@@ -1,106 +0,0 @@
-import { jsx as _jsx } from "react/jsx-runtime";
-/**
- * The keyboard drawer (tui-shortcut-drawer-and-task-summary §4.5).
- *
- * ASCII ONLY: `src/ui/**` is inside `glyphs.test.ts::inScope`.
- *
- * IT OWNS NO CHROME AND NO ARITHMETIC. `OverlayFrame` draws the frame, the
- * window and the position indicator; `shortcut-panel-layout.ts` decides the
- * columns, the rows and which window contains the cursor. This component adds two
- * things and nothing else: its own key handling and the text-run colours. v1
- * planned 260 lines that re-implemented the frame's windowing and clamping - a
- * second source of truth for the one thing overlays have already been rewritten
- * once to unify.
- *
- * IT DOES NOT REGISTER `Esc` AND DOES NOT TOUCH ANY `ctrl`/`meta` COMBINATION:
- * `Esc` belongs to `App` (it closes every overlay and cancels the pending
- * question/plan), and `Ctrl+G` is handled there too. Two listeners both acting on
- * one byte is how a panel closes twice.
- */
-import { useMemo, useState } from 'react';
-import { Text, useInput } from 'ink';
-import { pickGlyphs } from '../glyphs.js';
-import { OverlayFrame, overlayBodyRows, overlayPageSize } from '../layout/OverlayFrame.js';
-import { buildShortcutRows, shortcutPanelWidth, } from '../layout/shortcut-panel-layout.js';
-import { filterShortcuts, isAvailable, SHORTCUTS } from '../shortcuts.js';
-/** Colour per tone. `dim` is `muted` plus the dim attribute, never a second colour. */
-function toneOf(row, theme) {
-    if (row.tone === 'accent')
-        return { color: theme.accent };
-    if (row.tone === 'primary')
-        return { color: theme.primary };
-    if (row.tone === 'dim')
-        return { color: theme.muted, dimColor: true };
-    return { color: theme.muted };
-}
-export function ShortcutPanel(props) {
-    const { cols, maxRows, theme, caps, isActive, native, running } = props;
-    const glyphs = pickGlyphs(caps);
-    const [cursor, setCursor] = useState(0);
-    const entries = useMemo(() => filterShortcuts(SHORTCUTS, props.query ?? ''), [props.query]);
-    const bodyRows = overlayBodyRows(maxRows, cols);
-    const page = overlayPageSize(maxRows, cols);
-    const result = useMemo(() => buildShortcutRows({
-        cols,
-        rows: bodyRows,
-        cursor,
-        entries,
-        task: props.task,
-        entryAvailable: (entry) => isAvailable(entry, { native, running }),
-        unavailableReason: native ? 'this mode leaves it to the terminal' : 'a run is in flight',
-        glyphs: {
-            ellipsis: glyphs.ellipsis,
-            cursor: glyphs.cursor,
-            hrule: glyphs.hrule,
-            midDot: glyphs.midDot,
-        },
-    }), [cols, bodyRows, cursor, entries, props.task, native, running,
-        glyphs.ellipsis, glyphs.cursor, glyphs.hrule, glyphs.midDot]);
-    const last = Math.max(0, entries.length - 1);
-    useInput((input, key) => {
-        // `ctrl`/`meta` ARE NOT OURS: `Ctrl+G` closes this panel and `Ctrl+C` owns the
-        // exit ladder, both in `App`. Consuming them here would double-handle a byte.
-        if (key.ctrl || key.meta)
-            return;
-        if (key.upArrow || input === 'k') {
-            setCursor((value) => Math.max(0, value - 1));
-            return;
-        }
-        if (key.downArrow || input === 'j') {
-            setCursor((value) => Math.min(last, value + 1));
-            return;
-        }
-        // PAGING MOVES THE CURSOR, one page minus one row of overlap - the same rule
-        // `overlayPageSize` uses for every other overlay, so a page turn keeps a row of
-        // context. An independent offset would let the selected row - and the detail
-        // line that explains it - slide off screen (P1-7).
-        if (key.pageUp) {
-            setCursor((value) => Math.max(0, value - Math.max(1, page - 1)));
-            return;
-        }
-        if (key.pageDown) {
-            setCursor((value) => Math.min(last, value + Math.max(1, page - 1)));
-            return;
-        }
-        if (input === 'd') {
-            props.onToggleDetails();
-            return;
-        }
-        if (input === 'r') {
-            props.onRefresh();
-        }
-    }, { isActive });
-    const rows = result.rows.map((row, index) => (_jsx(Text, { wrap: "truncate", ...toneOf(row, theme), children: row.text }, `${row.kind}-${row.entryId ?? 'x'}-${index}`)));
-    // THE `d` MARKER LIVES ON THE FRAME'S OWN TITLE LINE (D-6), which is chrome that is
-    // already paid for. It is spelled `d:on` / `d:off` rather than `details on|off`
-    // because the title row also carries the frame's position indicator (`v 1-13/37`,
-    // 13 cells) and the drawer's content is only 26 cells wide at 80 columns: the long
-    // form is truncated to `details...`, which is a marker that says nothing. The
-    // footer's `d details` clause names the key, so the pair reads as one sentence.
-    const title = `Keys  d:${props.detailsExpanded ? 'on' : 'off'}`;
-    return (_jsx(OverlayFrame, { title: title, hint: result.hint, maxRows: maxRows, cols: cols, width: shortcutPanelWidth(cols), align: "right", rows: rows, 
-        // THE WINDOW IS DERIVED FROM THE CURSOR, so the offset handed to the frame is
-        // a conclusion rather than state. `onScrollClamp` is deliberately not passed:
-        // there is nothing here that could drift out of step with it.
-        scrollOffset: result.window.start, theme: theme, caps: caps }));
-}

package/dist/ui/overlays/TeamFanoutPage.d.ts

@@ -1,51 +0,0 @@
-/**
- * Settings > Team: four arrows-adjustable rows (subagent-fanout 3.4.3, extended
- * by team-command-forced-dispatch §3.9).
- *
- * ASCII ONLY - `src/ui/**` is inside `glyphs.test.ts::inScope`.
- *
- * THE PAGE OWNS ONE PIECE OF STATE: its cursor. Every value comes from
- * `props.view.rows`, which `SettingsScreen` derives from the reducer state - so
- * this page cannot hold a second copy of the draft and then disagree with the
- * root page about what is about to be saved (the discipline
- * `model-profile-state.ts` records at its own head).
- *
- * FOUR ROWS, NOT THREE: `Team mode` moved here from `/team on|off`, because a
- * command that both configures and executes leaves the user unable to predict
- * what it did. The switch is the FIRST row - the other three describe a capability
- * it turns on.
- *
- * IT DOES NOT LISTEN FOR Ctrl+S, AND THE FOOTER SAYS SO (R-P1-13).
- * `useRootSettingsInput` gates its `useInput` on `state.page === 'root'`, so a
- * subpage has no save listener at all - the kit page included. A footer
- * promising "Ctrl+S saves here" would therefore be a lie the user acts on. The
- * honest instruction is the one already in their fingers: Esc back, Ctrl+S on the
- * main page.
- */
-import React from 'react';
-import { type ProfileFrameProps } from './ModelProfilePicker.js';
-import type { TeamFanoutField, TeamFanoutView } from './team-fanout-state.js';
-/** What the page may ask the screen to change. */
-export interface TeamFanoutAction {
-    type: 'team-fanout';
-    field: TeamFanoutField;
-    delta: -1 | 1;
-}
-interface TeamFanoutPageProps extends ProfileFrameProps {
-    view: TeamFanoutView;
-    dispatch: (action: TeamFanoutAction) => void;
-    /** Esc: back to the settings root. The draft is NOT discarded here. */
-    onBack: () => void;
-    /**
-     * Whether `task` is in this SESSION's tool list (`--no-team` is the false case).
-     *
-     * OPTIONAL, like every other pass-through on this screen: fixtures build
-     * `ProfileFrameProps` by literal, and "absent" honestly means "not disclosed"
-     * rather than "registered". When it is `false` and the draft says `on`, the
-     * `Team mode` row reads `on (next launch)` - the tool array is immutable, so
-     * that is the truth about what saving will achieve (I-7 / AC-9).
-     */
-    teamRegistered?: boolean;
-}
-export declare function TeamFanoutPage(props: TeamFanoutPageProps): React.ReactElement;
-export {};

package/dist/ui/overlays/TeamFanoutPage.js

@@ -1,90 +0,0 @@
-import { jsx as _jsx } from "react/jsx-runtime";
-/**
- * Settings > Team: four arrows-adjustable rows (subagent-fanout 3.4.3, extended
- * by team-command-forced-dispatch §3.9).
- *
- * ASCII ONLY - `src/ui/**` is inside `glyphs.test.ts::inScope`.
- *
- * THE PAGE OWNS ONE PIECE OF STATE: its cursor. Every value comes from
- * `props.view.rows`, which `SettingsScreen` derives from the reducer state - so
- * this page cannot hold a second copy of the draft and then disagree with the
- * root page about what is about to be saved (the discipline
- * `model-profile-state.ts` records at its own head).
- *
- * FOUR ROWS, NOT THREE: `Team mode` moved here from `/team on|off`, because a
- * command that both configures and executes leaves the user unable to predict
- * what it did. The switch is the FIRST row - the other three describe a capability
- * it turns on.
- *
- * IT DOES NOT LISTEN FOR Ctrl+S, AND THE FOOTER SAYS SO (R-P1-13).
- * `useRootSettingsInput` gates its `useInput` on `state.page === 'root'`, so a
- * subpage has no save listener at all - the kit page included. A footer
- * promising "Ctrl+S saves here" would therefore be a lie the user acts on. The
- * honest instruction is the one already in their fingers: Esc back, Ctrl+S on the
- * main page.
- */
-import { useState } from 'react';
-import { Text, useInput } from 'ink';
-import { pickGlyphs } from '../glyphs.js';
-import { OverlayFrame } from '../layout/OverlayFrame.js';
-import { clipProfileText, useProfileScroll } from './ModelProfilePicker.js';
-/**
- * Label column, matching the root page's `padEnd(18)` rows above and below this
- * one. `Team mode` is 9 characters and `Max subagents` is 13, so 18 keeps the
- * value column aligned with `Subagent model` on the root page - measured, not
- * guessed.
- */
-const LABEL_PAD = 18;
-/**
- * The two rows `Enter` toggles, and nothing else (R-P1-12).
- *
- * A stray Return that silently changed a NUMBER is indistinguishable from a bug,
- * and the arrow keys are already the obvious control there.
- */
-const TOGGLE_FIELDS = new Set(['enabled', 'overseer']);
-export function TeamFanoutPage(props) {
-    const [index, setIndex] = useState(0);
-    const rows = props.view.rows;
-    const count = Math.max(1, rows.length);
-    const cursor = Math.min(index, count - 1);
-    const focused = rows[cursor];
-    const offset = useProfileScroll(props, cursor);
-    const nudge = (delta) => {
-        if (!focused)
-            return;
-        props.dispatch({ type: 'team-fanout', field: focused.field, delta });
-    };
-    useInput((_input, key) => {
-        if (props.isActive === false)
-            return;
-        if (key.escape) {
-            props.onBack();
-            return;
-        }
-        if (key.upArrow || (key.tab && key.shift)) {
-            setIndex((cursor - 1 + count) % count);
-            return;
-        }
-        if (key.downArrow || key.tab) {
-            setIndex((cursor + 1) % count);
-            return;
-        }
-        if (key.leftArrow || key.rightArrow) {
-            nudge(key.leftArrow ? -1 : 1);
-            return;
-        }
-        // `Enter` toggles the two boolean rows and does NOTHING on a numeric row.
-        if (key.return && focused && TOGGLE_FIELDS.has(focused.field))
-            nudge(1);
-    });
-    const lines = rows.map((row) => `${row.label.padEnd(LABEL_PAD)}${row.value}`);
-    const glyphs = pickGlyphs(props.caps);
-    const body = lines.map((line, at) => (_jsx(Text, { wrap: "truncate", color: at === cursor ? props.theme.accent : props.theme.muted, children: `${at === cursor ? glyphs.caret : ' '} ${clipProfileText(line, props.cols - 8)}` }, at)));
-    // The hint explains the FOCUSED row rather than decorating the frame: numbers
-    // whose meaning is not obvious ("per dispatch" versus "at once") are the reason
-    // this page exists at all.
-    if (focused) {
-        body.push(_jsx(Text, { wrap: "truncate", color: props.theme.muted, children: clipProfileText(focused.hint, props.cols - 8) }, "hint"));
-    }
-    return _jsx(OverlayFrame, { ...props, rows: body, scrollOffset: offset, title: props.view.error ?? 'Team', hint: "Arrows adjust. Esc goes back; Ctrl+S on the main page saves." });
-}

package/dist/ui/overlays/governance-settings.d.ts

@@ -1,79 +0,0 @@
-/**
- * Settings > Governance: the pure half of the page (governance-mode 11.1).
- *
- * ASCII ONLY - `src/ui/**` is inside `glyphs.test.ts::inScope`.
- *
- * FIELD DEFINITIONS AND THE ARROW-KEY STEP, NOTHING ELSE. `SettingsScreen.tsx` is far past
- * the size limit, so the page lists its rows from here and adds wiring only, mirroring
- * `team-fanout-state.ts`. Every value a step produces goes back through
- * `clampGovernanceConfig`, so the page, `config set` and a hand-edited `config.json` can
- * never disagree about a range.
- *
- * THE PAGE MAY WRITE THE ELEVEN POLICY KEYS AND NOTHING ELSE. The structural bounds
- * (`GOV_LIMITS`) are not settings: a number a user can tune past what the store and the
- * panel can carry is not a preference, it is a crash.
- */
-import { type GovernanceConfig } from '../../config/governance-config.js';
-import type { ModelSettingsDraft } from '../../config/model-profile-store.js';
-export type GovernanceSettingKey = keyof GovernanceConfig;
-export type GovernanceSettingKind = 'toggle' | 'number' | 'choice';
-export interface GovernanceSettingDef {
-    key: GovernanceSettingKey;
-    /** At most 17 columns: the page pads labels to 18, like the Team page. */
-    label: string;
-    /** One line, at most 60 columns: WHY this setting, not a restatement of the label. */
-    description: string;
-    kind: GovernanceSettingKind;
-    /** Inclusive; numbers only. Read from the clamp, never repeated here. */
-    range?: {
-        min: number;
-        max: number;
-    };
-    /** Arrow-key increment; numbers only. */
-    step?: number;
-    /** Cycle order; choices only. */
-    choices?: readonly string[];
-}
-/** The rows in cursor order. The switch is first: the rest describe what it turns on. */
-export declare const GOVERNANCE_SETTING_DEFS: readonly GovernanceSettingDef[];
-export interface GovernanceSettingRow {
-    key: GovernanceSettingKey;
-    label: string;
-    /** The value as the page prints it (`'on'` / `'3'` / `'unlimited'`). */
-    value: string;
-    /** Description plus the range, one line. */
-    hint: string;
-}
-/** The page's rows for the CLAMPED section, so the screen shows what would be saved. */
-export declare function governanceSettingRows(values: unknown): GovernanceSettingRow[];
-/**
- * The PATCH FRAGMENT for one arrow press, for a section the screen already shows
- * (`current`). Exactly one key, so a step can never carry a second one into the draft.
- * Toggles flip on either arrow, as on the Team page: a direction means nothing for two
- * states. An unknown key yields an empty patch rather than throwing.
- */
-export declare function stepGovernanceSetting(current: unknown, key: GovernanceSettingKey, delta: -1 | 1): Partial<GovernanceConfig>;
-/**
- * The governance section this draft would save: the patch over the disk baseline, then the
- * clamp (governance-mode-v1-1 5.2). Same order as `teamFanoutValues`, and the clamp is not
- * cosmetic: it is what makes the number on screen the number `Ctrl+S` writes, whatever a
- * hand-edited `config.json` or an old patch carried.
- */
-export declare function draftGovernance(draft: ModelSettingsDraft): GovernanceConfig;
-/**
- * The one-line summary the settings root row prints. A DERIVED row, never a control: the
- * values change on the page Enter opens, so the root row cannot be moved by a stray arrow.
- * `off` alone when the switch is off, because the numbers then describe a capability that
- * is not there (the `teamSummary` rule).
- */
-export declare function governanceSummary(config: GovernanceConfig): string;
-export type GovernanceRestartNote = string | null;
-/**
- * Whether saving the `enabled` switch would not take effect in THIS session. The tool array
- * is immutable after construction (v1 D-22), so a draft that disagrees with what was
- * registered at launch only applies next launch, and the page says so rather than letting a
- * user believe a toggle summoned `gov_run` into the running session. `undefined` means the
- * host did not say, and the page then discloses nothing (every fixture builds props by
- * literal).
- */
-export declare function governanceRestartNote(enabledInDraft: boolean, registeredAtLaunch: boolean | undefined): GovernanceRestartNote;

package/dist/ui/overlays/governance-settings.js

@@ -1,140 +0,0 @@
-/**
- * Settings > Governance: the pure half of the page (governance-mode 11.1).
- *
- * ASCII ONLY - `src/ui/**` is inside `glyphs.test.ts::inScope`.
- *
- * FIELD DEFINITIONS AND THE ARROW-KEY STEP, NOTHING ELSE. `SettingsScreen.tsx` is far past
- * the size limit, so the page lists its rows from here and adds wiring only, mirroring
- * `team-fanout-state.ts`. Every value a step produces goes back through
- * `clampGovernanceConfig`, so the page, `config set` and a hand-edited `config.json` can
- * never disagree about a range.
- *
- * THE PAGE MAY WRITE THE ELEVEN POLICY KEYS AND NOTHING ELSE. The structural bounds
- * (`GOV_LIMITS`) are not settings: a number a user can tune past what the store and the
- * panel can carry is not a preference, it is a crash.
- */
-import { clampGovernanceConfig, governanceRangeOf, } from '../../config/governance-config.js';
-import { PROFILE_IDS } from '../../governance/types.js';
-function numeric(key, label, description, step = 1) {
-    return { key, label, description, kind: 'number', range: governanceRangeOf(key), step };
-}
-/** The rows in cursor order. The switch is first: the rest describe what it turns on. */
-export const GOVERNANCE_SETTING_DEFS = [
-    { key: 'enabled', label: 'Governance', kind: 'toggle',
-        description: 'Off removes it entirely. Turning it on needs a restart.' },
-    { key: 'shiftTab', label: 'Shift+Tab cycle', kind: 'toggle',
-        description: 'Off keeps Shift+Tab on BUILD/PLAN; /gov still works.' },
-    { key: 'panel', label: 'Legion panel', kind: 'toggle',
-        description: 'Off shows the status chip only, no panel.' },
-    { key: 'profile', label: 'Profile', kind: 'choice', choices: PROFILE_IDS,
-        description: 'Domain wording for the roles and their checklists.' },
-    numeric('maxWorkPackages', 'Work packages', 'Most work packages one run may define.'),
-    numeric('maxPhases', 'Phases', 'Most dev/review/test rounds one run may take.'),
-    numeric('maxRework', 'Rework rounds', 'Rework rounds per work package before escalation.'),
-    numeric('maxFixCycles', 'Fix cycles', 'Fix cycles per phase after integration fails.'),
-    numeric('minAskRounds', 'Ask rounds', 'Questions PLAN+GOVERN asks before a plan is allowed.'),
-    numeric('budgetTokens', 'Token budget', 'Per-run token ceiling; 0 means unlimited.', 100_000),
-    { key: 'confirmCharter', label: 'Confirm charter', kind: 'toggle',
-        description: 'On asks you to approve the run plan before any dispatch.' },
-];
-function formatValue(def, config) {
-    const value = config[def.key];
-    if (def.kind === 'toggle')
-        return value ? 'on' : 'off';
-    if (def.key === 'budgetTokens')
-        return value === 0 ? 'unlimited' : String(value);
-    return String(value);
-}
-function formatHint(def) {
-    if (def.range === undefined)
-        return def.description;
-    return `${def.description} (${def.range.min}-${def.range.max})`;
-}
-/** The page's rows for the CLAMPED section, so the screen shows what would be saved. */
-export function governanceSettingRows(values) {
-    const config = clampGovernanceConfig(values);
-    return GOVERNANCE_SETTING_DEFS.map((def) => ({
-        key: def.key,
-        label: def.label,
-        value: formatValue(def, config),
-        hint: formatHint(def),
-    }));
-}
-function stepNumber(config, def, delta) {
-    const key = def.key;
-    // NO WRAPAROUND: a form control is not a ring, and Left at the floor jumping to the
-    // ceiling would be a way to raise a limit while trying to lower it. The clamp does it.
-    const next = clampGovernanceConfig({ ...config, [key]: config[key] + delta * (def.step ?? 1) });
-    return { [key]: next[key] };
-}
-function stepChoice(config, def, delta) {
-    const choices = def.choices ?? [];
-    const at = choices.indexOf(String(config[def.key]));
-    const next = choices[(at + delta + choices.length) % choices.length];
-    // Through the clamp, so a choice list that ever drifts from the clamp's vocabulary cannot
-    // write a value the read path would silently repair.
-    const stored = clampGovernanceConfig({ ...config, [def.key]: next })[def.key];
-    return { [def.key]: stored };
-}
-/**
- * The PATCH FRAGMENT for one arrow press, for a section the screen already shows
- * (`current`). Exactly one key, so a step can never carry a second one into the draft.
- * Toggles flip on either arrow, as on the Team page: a direction means nothing for two
- * states. An unknown key yields an empty patch rather than throwing.
- */
-export function stepGovernanceSetting(current, key, delta) {
-    const config = clampGovernanceConfig(current);
-    const def = GOVERNANCE_SETTING_DEFS.find((candidate) => candidate.key === key);
-    if (def === undefined)
-        return {};
-    if (def.kind === 'toggle')
-        return { [key]: !config[key] };
-    return def.kind === 'number' ? stepNumber(config, def, delta) : stepChoice(config, def, delta);
-}
-/**
- * The governance section this draft would save: the patch over the disk baseline, then the
- * clamp (governance-mode-v1-1 5.2). Same order as `teamFanoutValues`, and the clamp is not
- * cosmetic: it is what makes the number on screen the number `Ctrl+S` writes, whatever a
- * hand-edited `config.json` or an old patch carried.
- */
-export function draftGovernance(draft) {
-    return clampGovernanceConfig({ ...draft.baseline.governance, ...draft.patch.governance });
-}
-/** `0` is unlimited; otherwise a compact figure (`500k`, `1.2M`). */
-function budgetText(tokens) {
-    if (tokens <= 0)
-        return 'unlimited';
-    if (tokens >= 1_000_000)
-        return `${Number((tokens / 1_000_000).toFixed(1))}M`;
-    return `${Math.round(tokens / 1_000)}k`;
-}
-/**
- * The one-line summary the settings root row prints. A DERIVED row, never a control: the
- * values change on the page Enter opens, so the root row cannot be moved by a stray arrow.
- * `off` alone when the switch is off, because the numbers then describe a capability that
- * is not there (the `teamSummary` rule).
- */
-export function governanceSummary(config) {
-    if (!config.enabled)
-        return 'off';
-    return [
-        'on',
-        `${config.maxWorkPackages} WP`,
-        `${config.maxPhases} phases`,
-        `rework ${config.maxRework}`,
-        `budget ${budgetText(config.budgetTokens)}`,
-    ].join(' | ');
-}
-/**
- * Whether saving the `enabled` switch would not take effect in THIS session. The tool array
- * is immutable after construction (v1 D-22), so a draft that disagrees with what was
- * registered at launch only applies next launch, and the page says so rather than letting a
- * user believe a toggle summoned `gov_run` into the running session. `undefined` means the
- * host did not say, and the page then discloses nothing (every fixture builds props by
- * literal).
- */
-export function governanceRestartNote(enabledInDraft, registeredAtLaunch) {
-    if (registeredAtLaunch === undefined || enabledInDraft === registeredAtLaunch)
-        return null;
-    return 'Governance is registered at launch; this change applies next launch.';
-}

package/dist/ui/overlays/kit-picker-state.d.ts

@@ -1,87 +0,0 @@
-/**
- * The `ctrl+K` list, as a pure view model (agent-model-kits §4.6 / D-10).
- *
- * ASCII ONLY - `src/ui/**` is inside `glyphs.test.ts::inScope`.
- *
- * WHY THE ROWS ARE COMPUTED HERE AND NOT IN THE COMPONENT: three surfaces print
- * the same three connections (this list, the settings manager, `/kit list`).
- * One function produces them, so the wording of "the fast tier is off" cannot
- * differ between the key the user pressed and the command they typed.
- */
-import type { CliConfig, TeamConfig } from '../../config/schema.js';
-import type { ModelProfilesConfig } from '../../config/model-profiles.js';
-import { type KitConnection, type KitSlot } from '../../config/model-kits.js';
-import { type ActiveKit } from '../../config/kit-resolution.js';
-export interface KitPickerRow {
-    /** `null` = `Current setup` (the release action). */
-    id: string | null;
-    /** The one-line label, markers included. */
-    label: string;
-    /** Machine-checkable markers, so tests never grep a rendered string. */
-    markers: {
-        inUse: boolean;
-        isDefault: boolean;
-        modified: boolean;
-    };
-    /** Non-empty when a referenced profile is gone. */
-    missing: KitSlot[];
-}
-export interface KitPickerInput {
-    library?: ModelProfilesConfig | undefined;
-    active: ActiveKit;
-}
-/** `provider:model` plus the endpoint clause shared by every surface. */
-export declare function connectionText(connection: KitConnection): string;
-/**
- * Rows in a FIXED order: `Current setup` first, then the library's own order.
- *
- * The first row never moves (AC-24) - it is the only row that can always be
- * chosen, and a list whose "off" entry wanders with the data is a list a user
- * has to read every single time.
- */
-export declare function kitRows(input: KitPickerInput): KitPickerRow[];
-/**
- * The three bindings `Current setup` describes.
- *
- * STRUCTURAL, NOT `CliConfig`: the caller hands in the PERSISTED config for this
- * block (§4.6), because the live config no longer holds the file's bindings once
- * a session kit is applied - it mirrors the kit (I-6). Both shapes satisfy this
- * interface, so neither layer has to convert anything.
- */
-export interface KitConnectionsSource {
-    provider: string;
-    model: string;
-    team?: {
-        model: TeamConfig['model'];
-        modelProfileId?: string | null;
-    } | undefined;
-    fast: {
-        enabled: boolean;
-        provider: string;
-        model: string;
-    };
-    modelProfiles?: ModelProfilesConfig | undefined;
-}
-/** The three lines under the focused row (§4.6). */
-export declare function kitDetail(input: {
-    row: KitPickerRow;
-    library?: ModelProfilesConfig | undefined;
-    config: CliConfig;
-    /** The config file's copy of the bindings; see the `Current setup` note below. */
-    diskConfig?: KitConnectionsSource | undefined;
-}): string[];
-/**
- * The footer. `busy` is a warning, never a reason to hide the list (§4.7).
- *
- * THE LAST CLAUSE IS D-7, VERBATIM: this overlay is a session-only surface, so it
- * says where the persistence actually lives. Without it the natural reading of
- * `Enter` is "make this my default", and D-7 exists to keep that action one
- * deliberate trip to `/settings` instead of one keystroke next to a browse key.
- * It is LAST so that a 40-column terminal clips the pointer, never the action.
- */
-export declare function kitPickHint(input: {
-    busy: boolean;
-    hasKits: boolean;
-}): string;
-/** The one guidance row an empty library renders (AC-26). */
-export declare const NO_KITS_HINT = "No kits yet. Create one in /settings (Settings > Kit pack).";