@aragon-agent/cli 0.6.47 → 0.6.48

package/dist/prompts/fill.d.ts

@@ -1,51 +0,0 @@
-/**
- * How a prompt lands in the composer (quick-prompt-library D-6 / §4.6).
- *
- * ASCII ONLY - `src/prompts/**` is inside `glyphs.test.ts::inScope`.
- *
- * PURE, AND IT KNOWS NOTHING ABOUT THE DRAFT'S REAL SHAPE. It is handed the current
- * buffer and caret, and it answers "what should be inserted, or what should the new
- * buffer be". It deliberately does NOT return the resulting buffer: a draft may
- * hold paste-collapse TOKENS (`[Pasted text #1 +8 lines]` plus a payload map), so
- * "the buffer after applying this plan" is a fact only `editorReducer` can compute.
- * Recomputing it here would be a second authority, and the two would drift exactly
- * on the drafts this feature exists to append to.
- *
- * WHY `insert` IS THE DEFAULT (and why the decision lives here rather than in
- * `App`): the only place that knows what the draft currently holds is the editor
- * (the host has no copy of the text), and silently discarding what someone has
- * already typed is the one thing a "fill" gesture must never do.
- */
-export interface PromptFillInput {
-    /** The current draft buffer. */
-    draft: string;
-    /** Caret offset into `draft`, in UTF-16 units. */
-    cursor: number;
-    /** The prompt body. */
-    content: string;
-    /** `insert` unless the user configured `prompts.insertMode = 'replace'` (D-19). */
-    mode?: 'insert' | 'replace';
-}
-export interface PromptFillPlan {
-    mode: 'replace' | 'insert';
-    /**
-     * `replace`: the new buffer in full.
-     * `insert`: only the fragment to insert, separators included.
-     */
-    text: string;
-    /**
-     * `replace`: where the caret goes afterwards (past the body).
-     * `insert`: ignored - the reducer owns the caret and the token snapping.
-     */
-    cursor: number;
-}
-/**
- * Decide between replacing and inserting, and build the fragment.
- *
- * A blank draft is replaced even in `insert` mode: "insert at the caret" into an
- * empty buffer and "replace the empty buffer" are the same edit, and saying so
- * keeps the caller from having to special-case it.
- */
-export declare function planPromptFill(input: PromptFillInput): PromptFillPlan;
-/** Lines a body occupies, for the "8 lines, editable" acknowledgement. */
-export declare function promptLineCount(content: string): number;

package/dist/prompts/fill.js

@@ -1,46 +0,0 @@
-/**
- * How a prompt lands in the composer (quick-prompt-library D-6 / §4.6).
- *
- * ASCII ONLY - `src/prompts/**` is inside `glyphs.test.ts::inScope`.
- *
- * PURE, AND IT KNOWS NOTHING ABOUT THE DRAFT'S REAL SHAPE. It is handed the current
- * buffer and caret, and it answers "what should be inserted, or what should the new
- * buffer be". It deliberately does NOT return the resulting buffer: a draft may
- * hold paste-collapse TOKENS (`[Pasted text #1 +8 lines]` plus a payload map), so
- * "the buffer after applying this plan" is a fact only `editorReducer` can compute.
- * Recomputing it here would be a second authority, and the two would drift exactly
- * on the drafts this feature exists to append to.
- *
- * WHY `insert` IS THE DEFAULT (and why the decision lives here rather than in
- * `App`): the only place that knows what the draft currently holds is the editor
- * (the host has no copy of the text), and silently discarding what someone has
- * already typed is the one thing a "fill" gesture must never do.
- */
-/** Two newlines, so the typed text and the prompt read as two paragraphs. */
-const SEPARATOR = '\n\n';
-/**
- * Decide between replacing and inserting, and build the fragment.
- *
- * A blank draft is replaced even in `insert` mode: "insert at the caret" into an
- * empty buffer and "replace the empty buffer" are the same edit, and saying so
- * keeps the caller from having to special-case it.
- */
-export function planPromptFill(input) {
-    const cursor = Math.max(0, Math.min(input.draft.length, Math.floor(input.cursor)));
-    const blank = input.draft.trim().length === 0;
-    if (input.mode === 'replace' || blank) {
-        return { mode: 'replace', text: input.content, cursor: input.content.length };
-    }
-    const before = input.draft.slice(0, cursor);
-    const after = input.draft.slice(cursor);
-    // A SEPARATOR IS ADDED ONLY WHERE ONE IS MISSING, which is what keeps the plan
-    // from producing three newlines when the caret already sits on a blank line.
-    const lead = before.length > 0 && !before.endsWith(SEPARATOR) ? SEPARATOR : '';
-    const trail = after.length > 0 && !after.startsWith(SEPARATOR) ? SEPARATOR : '';
-    const text = `${lead}${input.content}${trail}`;
-    return { mode: 'insert', text, cursor: cursor + lead.length };
-}
-/** Lines a body occupies, for the "8 lines, editable" acknowledgement. */
-export function promptLineCount(content) {
-    return content.split('\n').length;
-}

package/dist/prompts/limits.d.ts

@@ -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 declare const PROMPT_LIMITS: {
-    /** Entries one library may hold. The 201st create is REFUSED, never truncated. */
-    readonly maxPrompts: 200;
-    /** Title, without surrounding whitespace. */
-    readonly titleMaxChars: 80;
-    /** Body. Large enough for a 40-line procedure, small enough to rewrite cheaply. */
-    readonly contentMaxChars: 8000;
-    /** Optional one-line note under the title. */
-    readonly descriptionMaxChars: 200;
-    /** Tags per entry. */
-    readonly maxTags: 6;
-    /** Characters per tag. */
-    readonly tagMaxChars: 24;
-    /** Body preview lines the list page's detail block may spend (read-only). */
-    readonly detailPreviewLines: 3;
-    /** Rows the list page's detail block may occupy, preview lines included. */
-    readonly detailMaxLines: 6;
-    /** Characters of a body shown on ONE preview line. */
-    readonly 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 declare const PROMPT_PICKER_LIMITS: {
-    /** Longest query the filter accepts; further typing is ignored. */
-    readonly queryMaxChars: 64;
-    /** `1`-`9` pick directly, so nine. */
-    readonly quickDigits: 9;
-    /** Rows the picker's detail block may occupy. */
-    readonly detailMaxLines: 4;
-};

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 {};