replan-findingslisted

# Replan Findings (internal) One owner of the replan entry: an open finding whose frozen route is the plan owner becomes new phases on the unit's own SPEC ledger, read from the finding itself. The router decides **whether** this contract loads and **what** it may read; this contract decides how the phases are appended. It never classifies a finding, never edits a ledger row, and never reviews the plan it produced. ## When to use - `plan-feature` or `plan-fix`, and only after `node scripts/unit-route.mjs <unit>` printed `route: replan`. - Nothing else. No replan line → this contract is not loaded; follow the line the router did print. ## Load condition (the router decides — never inferred) ```text node scripts/unit-route.mjs <unit> → route: replan ``` Only that line licenses this contract. A unit whose planner is invoked directly without the router run must run the router first; the router answers `replan` from the ledger the caller cannot otherwise see, and the planner's other routes keep their own gates. A missing `scripts/unit-route.mjs` is a `BLOCKED` prerequisite, never a reason to guess or to read the whole ledger. ## Router output — the block this contract consumes `node scripts/unit-route.mjs <unit>` prints one fixed block on stdout and its diagnostics on stderr. Every route prints the same eight fields, so a reader never guesses which ones exist: ```text UNIT ROUTE — <unit> unit: <slug> status: <roadmap or fix-index status, or absent