/**
 * Skill version incrementing on accepted mutations (Task 7.4).
 *
 * Authoritative source: `docs/opensquid-real-design.md` §"Phases 2–7 summary"
 * Phase 7 + §"Skill format" `version` field + `feedback_pre1_versioning`
 * (memory) — every change is a patch bump.
 *
 * When a lesson clears both gates (capture + promote), the skill it mutates
 * gets a patch bump on its `version:` field. The YAML rewrite goes through
 * the `yaml` package's Document API (`parseDocument` → `doc.set` →
 * `doc.toString()`) so comments + key ordering + anchor info survive the
 * round-trip — that's the difference between this and `JSON.parse` /
 * `JSON.stringify`, which would shred user-authored comments inside the
 * skill manifest.
 *
 * Failure modes:
 *
 *   - File missing → fs error propagates (caller's job to handle).
 *   - Missing `version:` key → defaults to `0.0.0` (so first bump produces
 *     `0.0.1`). Per `project_opensquid_out_of_the_box`, undefined fields
 *     should DTRT, not fail.
 *   - Invalid semver string → throws explicitly. The agent should never bump
 *     a malformed version silently; the throw forces the user to fix the
 *     manifest before the wedge gate can mutate it.
 *
 * Imports from: node:fs/promises, yaml, semver.
 * Imported by: src/runtime/wedge/index.ts, Phase 8 mutation pipeline.
 */
export declare function bumpSkillVersion(skillYamlPath: string): Promise<string>;
//# sourceMappingURL=mutate_skill.d.ts.map