plan-reviselisted

# Plan Revise Take the critic's report, ground-truth each finding against the code (do not blindly trust either the critic OR the original plan), and produce a strengthened final plan ready for user approval. ## Required Inputs - The critic's structured report from `/forge:critic-review`, in conversation context. - The current master plan, in conversation context. - The original feature requirements as the user expressed them. ## Revision procedure For each critic finding, walk this loop: 1. **Read the cited code.** Invoke `Read` (and `Grep` if needed) on the `file:line` the critic referenced. Verify the critic's "Reality" claim against the actual code. 2. **Classify the finding** based on what you observed: - **Verified blocking** — code matches the critic's claim AND the consequence is real. MUST fix in the plan. - **Verified gap** — code shows the plan was missing a decision; the critic's suggested fix is sound. Fold it in. - **Refuted** — code does not match the critic's claim (critic misread). Note in the plan's "critique resolution" section with `file:line` evidence so the user sees you checked. - **Open question** — neither the plan nor the critic can resolve from code alone; bubble up to the user-approval step. 3. **Apply the change.** For verified items, rewrite the affected plan section in place — do NOT append a "v2" plan; the conversation should hold one canonical plan at a time. Keep all `file:line` citations. 4. **Append a "Critique resolution"