export interface TemplateDeployResult {
    /** Absolute target directory templates are deployed into. */
    targetDir: string;
    /** Filenames copied — newly created, or refreshed because the bundled
     *  content differed from the existing file. */
    deployed: string[];
    /** Filenames left untouched (already present with identical content). */
    skipped: string[];
    /** Non-fatal problems (e.g. permission denied). Deploy never throws. */
    errors: string[];
}
export interface DeployBundledTemplatesOptions {
    /**
     * Directory holding the bundled .hwpx templates. Defaults to the `assets/`
     * folder next to the server bundle (`<bundle>/assets`). In a `.mcpb` install
     * the compiled entry lives at `<ext>/server/index.js`, so assets resolve to
     * `<ext>/assets`. In a plain npm install this folder does not exist (npm only
     * ships `dist/`), so deploy is a silent no-op there.
     */
    assetsDir?: string;
    /** Override the deploy target (used in tests). Defaults to the user's
     *  Documents/skills/templates via collectUserPaths(). */
    targetDir?: string;
}
export declare function deployBundledTemplates(opts?: DeployBundledTemplatesOptions): TemplateDeployResult;