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. Before applying a fix that stops a failure, whether the finding suggested it or you derived it, confirm the fix makes the failure the finding describes unreachable rather than only defeating the finding's reproduction: construct an input that clears the point the fix guards, trace whether it still reaches that failure further along, and write any regression test the fix adds from that input. When the fix encodes, escapes, quotes, or otherwise sanitizes untrusted input, construct such inputs from every character class the target interpreter treats specially and name what in the fix blocks each one; a class with no blocker means the fix is incomplete, including when it reproduces the finding's suggested wording. When the finding carries a suggested fix, also treat the fix as a separate claim from the finding...