/** * Per-task plan-note naming (2026-10). * * Every planning pass used to upload a note literally named `plan.md` into * `agents//tasks//`, so the Documents tab filled with * indistinguishable `plan.md` rows and nobody could tell which plan belonged * to which task. Plan notes are now named `-plan.md`, where the slug * comes from the task title - descriptive, folder-unique, and still matched * by every existing reader (`findPlanDocuments` matches folder + * `/plan/i` on the name, so no reader needs to change). * * Rules the prompts repeat (kept here so the wording cannot drift): * - derive the slug from the TASK TITLE, lowercase, non-alphanumerics to `-`; * - cap the slug at 50 chars so the full name stays well under limits; * - on a re-plan, LIST the folder first and REUSE the existing `*-plan.md` * name (create_document upserts on project+folder+name+uploader, so reuse * writes a new VERSION instead of a second file); * - never a bare `plan.md`. */ /** Max slug chars - keeps `-plan.md` short in listings. */ export declare const PLAN_NOTE_SLUG_MAX = 50; /** Lowercase kebab slug of a task title (`'Fix the login bug!'` -> `'fix-the-login-bug'`). */ export declare function slugifyTaskTitle(title: string): string; /** * Exact plan-note name for a task (`'Fix the login bug!'` -> * `'fix-the-login-bug-plan.md'`). Prompts inject this verbatim so the model * never invents its own variant. */ export declare function planNoteName(taskTitle: string): string;