replanlisted

# Replan User-invoked only (`/drydock:replan <plan-path>`). Auto-triggered replanning is how plans get silently mutated mid-execution — that is why model invocation is disabled. If Claude believes a replan is needed, it recommends the command; the human runs it. Contract: `${CLAUDE_PLUGIN_ROOT}/skills/planwright/reference/plan-format.md`. ## Scope discipline — the whole point Replan is a PATCH operation, never regeneration. Hard invariants: - Decision Log: append-only. Prior decisions stand unless the human explicitly reverses one (append the reversal as a new entry; never rewrite). - Completed waves and their wavecheck reports: immutable history. - Task ids: never reused. A replaced task gets a new id with suffix (`T2.3.1r1`); the original is struck through with a pointer, not deleted. ## Process 1. **Assumption sweep.** Run every Assumptions Register verification command. Mark each entry verified-today or FAILED. Add register entries for any new load-bearing facts you discover while sweeping. 2. **Blast radius.** For each FAILED assumption and each unresolved BLOCK, compute the affected task set: tasks whose `owns`, `instructions`, `acceptance`, or `depends_on` reference the failed fact. Everything outside that set is untouchable — resist the urge to "improve" healthy tasks. 3. **Patch.** For affected tasks only: rewrite the task block (new id), re-derive its wave placement, and re-validate disjoint ownership across the affected waves. If p