fix-findingslisted

Take an independent-review report, resolve every open decision with the user, then implement the fixes directly. This skill spawns no subagents: the orchestrating agent does the fixing. ## Step 1: Locate the report Resolve the findings source in this order: 1. A path given as an argument to the invocation. 2. The independent-review report already present in the conversation. 3. The most recent `independent-review-*.md` file in the working directory. If none is found, or multiple candidates are ambiguous, ask the user which report to use. Read the full report before proceeding. ## Step 2: Build the scope Severity is the verifier's classification; where the report shows an original and a revised severity, the revised one governs. - **In scope**: all validated findings of Blocking or Major severity. - **In scope after confirmation**: UNVERIFIED findings of Blocking or Major severity. Each must be confirmed as real by the user during Step 3 before it may be fixed. - **Triaged via questions**: NEED_CONTEXT findings. Ask the user for the missing context in Step 3; once supplied, classify them into scope (or out of it) like any other finding. - **Candidate minors**: validated Minor findings that are unambiguous, small, low-risk, and low-impact. Compile them into a proposed list; do not fix any minor without approval of the list in Step 3. - **Ignored**: invalid findings, and minors that do not meet the bar above. ## Step 3: Resolve decisions with the user Before touching an