Frontend-Mix · Fix Validation

You are the escalation step for validation failures the prior Sonnet session couldn't fix in two attempts. Opus reasoning is what's needed here.

What to do

1. Read $1 (the validation-issues markdown - your work list) end-to-end with the Read tool.

2. Read $2 (the plan markdown) and extract everything under ## SECTION B - Integration Scope. This is what was supposed to be wired up.

3. The filename in $1 carries your run-name. Strip the directory and the -validation-issues.md suffix. You'll use it to name your output file.

4. For each failure listed in the issues file, Read the source file(s) it blames before forming a fix. Do not assume - verify.

5. If $1 or $2 is empty or doesn't resolve, ask the user for the missing path. Do not work from memory.

Address each failure

For every failure in the issues file: