/**
 * Replace a pattern only in the current milestone section of ROADMAP.md.
 *
 * Port of replaceInCurrentMilestone from core.cjs lines 1013-1022.
 *
 * Semantics (byte-for-byte CJS parity):
 *   • No `</details>` in the content  → plain `content.replace(pattern, replacement)`.
 *   • Otherwise → split at the last `</details>` and replace only in the
 *     content AFTER it.
 *
 * INTENTIONALLY DOES NOT fall back to "search the last <details> block when
 * the after-slice didn't match." That fallback existed in an earlier SDK
 * port and would silently corrupt shipped-milestone content when the current
 * milestone is itself wrapped in `<details open>...</details>` and there's
 * nothing after the close tag. CJS callers handle the "milestone inside
 * <details>" case by passing the unscoped `content.replace(...)` directly
 * (see phase.cjs:1080 for plan-count update). Keep this function in
 * lockstep with core.cjs — deviations are how bug-2005 slipped in.
 */
export declare function replaceInCurrentMilestone(content: string, pattern: string | RegExp, replacement: string): string;
/**
 * Atomic read-modify-write for ROADMAP.md.
 *
 * Holds a lockfile across the entire read -> transform -> write cycle.
 */
export declare function readModifyWriteRoadmapMd(projectDir: string, modifier: (content: string) => string | Promise<string>, workstream?: string): Promise<string>;
//# sourceMappingURL=phase-roadmap-mutation.d.ts.map