/**
 * Three report-tier checks for roadmap items filed in the wrong status
 * (doctor-flags-misfiled-items/AC-1, AC-4, AC-7, AC-10 … AC-13).
 *
 * `roadmap next --autopilot` offers what is in `backlog/`, so a mis-filed item is built
 * unattended — `fieldmodel-apps` had one at rank 3 whose own Recommendation read "Do later, at
 * Stage 1 after the Stage 0 gate". Its project skill caught that by hand; the check is generic.
 *
 * **Why `report` and not `confirm`.** Every remedy here is a decision: parked or declined, park
 * now or start, still waiting or ready. Doctor never moves an item or writes a reason for the same
 * reason it never writes an executive summary (`roadmap-item-summary`): an invented decision reads
 * exactly like a real one. And a no-op `apply` at confirm tier would make `aidlc doctor` exit 1
 * for as long as one item sat in the wrong place.
 *
 * **Three ids, not one.** Each condition has a different fix, and one sentence naming three
 * fixes is the report people scroll past.
 *
 * The roadmap is read from `ctx.primaryProjectRoot`, resolved once by doctor, rather than
 * `primaryCheckout()`, which shells out to `git rev-parse` — the rule `roadmap-sync-gh-missing`
 * follows. Like every migration here, `check` is the single source of pending-ness.
 */
import type { Migration } from '../types.js';
export declare const roadmapHoldReason: Migration;
export declare const roadmapBacklogNotNow: Migration;
export declare const roadmapParkedDepsDone: Migration;
//# sourceMappingURL=roadmap-misfiled-items.d.ts.map