/**
 * TemplateActivationStrategy - Strategy for template element activation
 *
 * Templates are stateless and activated on-demand when rendering.
 * This strategy provides information about available templates without
 * maintaining active state.
 */
import { TemplateManager } from '../../elements/templates/TemplateManager.js';
import { BaseActivationStrategy } from './BaseActivationStrategy.js';
import { ElementActivationStrategy, MCPResponse } from './ElementActivationStrategy.js';
export declare class TemplateActivationStrategy extends BaseActivationStrategy implements ElementActivationStrategy {
    private readonly templateManager;
    constructor(templateManager: TemplateManager);
    /**
     * "Activate" a template (actually just verify it exists and show info)
     * Extracted from ElementCRUDHandler.ts lines 208-228
     *
     * @throws {ElementNotFoundError} When template does not exist
     * @see Issue #275 - Handlers return success=true for missing elements
     */
    activate(name: string): Promise<MCPResponse>;
    /**
     * Deactivate a template (templates are stateless)
     * Extracted from ElementCRUDHandler.ts lines 543-550
     */
    deactivate(_name: string): Promise<MCPResponse>;
    /**
     * Get active templates (templates are stateless)
     * Extracted from ElementCRUDHandler.ts lines 414-421
     */
    getActiveElements(): Promise<MCPResponse>;
    /**
     * Get detailed information about a template
     * Extracted from ElementCRUDHandler.ts lines 691-728
     *
     * @throws {ElementNotFoundError} When template does not exist
     * @see Issue #275 - Handlers return success=true for missing elements
     */
    getElementDetails(name: string): Promise<MCPResponse>;
}
//# sourceMappingURL=TemplateActivationStrategy.d.ts.map