/**
 * SearchHooCode — retrieval over hoocode's own docs and the capabilities this
 * session actually has.
 *
 * The system prompt already lists every shipped doc with a one-line summary
 * (see `core/self-docs.ts`), which answers "which file covers extensions?".
 * What it cannot answer is anything *inside* a file: `extensions.md` alone is
 * over a thousand lines, and reading it whole to find one heading costs more
 * context than the rest of the prompt put together. This indexes docs at the
 * heading level so a question lands on a section and a line number.
 *
 * It also registers the capability kinds the registry has always declared but
 * nobody ever filled — `skill`, `command`, `agent`, `plugin-installed`
 * (registry.ts notes §6.4 left them eager). Those are eager in the prompt, so
 * indexing them is not about reachability; it is about "what can you do?"
 * having one place that answers it rather than the model reciting whichever
 * list happens to be in front of it.
 *
 * `mcp-tool` is deliberately out of scope: ResolveMcpTools owns that kind
 * because finding an MCP tool and making it callable are the same action
 * there, and a second searcher that returns un-resolvable names would be a
 * worse answer, not an extra one.
 */
import type { ExtensionAPI } from "../../core/extensions/types.js";
export declare function setupSelfKnowledge(hoo: ExtensionAPI): void;
/** Tests, and anything that relocates the package root mid-process. */
export declare function resetSelfKnowledge(): void;
//# sourceMappingURL=self-knowledge.d.ts.map