/**
 * healing.skill.ts
 *
 * Generates candidate locators for a failed step by scanning the current page's
 * elements for any that semantically match the step description.
 *
 * This skill is activated by the SkillOrchestrator when a failureContext is
 * present in the SkillContext. It does a fuzzy keyword match between the step
 * description and the text/label/placeholder of each interactive element on the
 * page, then proposes alternative locator expressions for those matches.
 *
 * This is different from HealingEngine (which operates on a live page at runtime)
 * — HealingSkill operates on the already-extracted PageAnalysis data structure
 * and is used as part of the generate_test flow when a failure context is provided.
 *
 * Confidence is 0.75 when candidates are found, 0.1 otherwise.
 *
 * Role in the overall flow:
 *   SkillOrchestrator.autoExecute() → HealingSkill.execute() (when failureContext present)
 *   → candidate locators returned to caller
 */
import { SkillContext, SkillResult } from '../types';
import { BaseSkill } from './base.skill';
/**
 * Suggests alternative locators for a failing step by matching the step
 * description against visible page elements.
 */
export declare class HealingSkill extends BaseSkill {
    readonly name = "healing";
    /**
     * Scan the page elements for fuzzy keyword matches with the failed step description
     * and return candidate locator expressions.
     *
     * If no failureContext is present, returns an empty result with zero confidence.
     *
     * @param ctx - The skill context, expected to include a failureContext with
     *              stepDescription and failureReason.
     * @returns A SkillResult with candidate locators and metadata about the failure.
     */
    execute(ctx: SkillContext): Promise<SkillResult>;
}
//# sourceMappingURL=healing.skill.d.ts.map