apply-findings

# Apply Findings Apply evaluated findings from the conversation context. Findings must have been through `/evaluate-findings` first. ## Step 1: Identify Findings Collect all findings from the conversation context. Findings should have Verdict columns (Apply, Skip, Escalate) from `/evaluate-findings`. If findings are unevaluated (raw output without verdicts), stop and say to run `/evaluate-findings` first. ## Step 2: Apply in File Order Group Apply findings by file path and apply in file order to minimize context switching. For each finding: 1. Read the full function or logical block at the referenced location 2. Verify the finding still applies to the current code 3. When the finding carries a suggested fix, treat the fix as a separate claim from the finding and verify it independently before applying it — trace it against the failure modes the finding names. If the fix does not hold up, treat the finding as Escalate (surface it in Step 3) and record why the remedy fails, rather than applying an unsound fix on the finding's authority. 4. When the fix would reverse a decision the user made earlier — in discussion or recorded in the artifact — treat the finding as Escalate (surface it in Step 3) and name the original decision. 5. Check what the fix you are about to make changes about the inputs the code accepts. When the change in accepted inputs is exactly the defect the finding names, apply it normally. When it turns away or newly admits anything beyond that defect — a...