/**
 * The intent-based command index — `scai`'s curated map of "what am I
 * trying to do" → "which commands to run, in order".
 *
 * The `--help` tree is alphabetical; this list groups commands by
 * *workflow* ("why won't this delete?", "clean up after a site
 * removal") so operators and agents reinventing an existing primitive
 * because they didn't know what to grep for is the discoverability bug
 * this addresses.
 *
 * Curated, hand-edited data — not auto-generated. It lives in `shared/`
 * (a leaf, no imports) so both surfaces consume ONE copy: the CLI
 * `scai cli topics` command renders it as text/JSON, and the MCP
 * `scai://help/topics` resource renders it as markdown. Keeping a single
 * source is the point — a topic list that drifts between the CLI and
 * the agent surface is worse than none.
 *
 * The cost is keeping this in sync when commands move; the payoff is
 * groupings that reflect workflows, not the command-tree layout.
 */
export interface TopicCommand {
    command: string;
    description: string;
}
export interface Topic {
    /** Short slug for `scai cli topics <name>`. */
    name: string;
    /** One-line description shown in the index. */
    description: string;
    /** Commands grouped under the topic, in recommended-run order. */
    commands: TopicCommand[];
}
export declare const TOPICS: Topic[];