fix-reviewlisted

Repair findings from the most recent review report in this conversation. Selection: $ARGUMENTS ## Select - When the selection names findings (`F1 F3`, "the high ones", a title), repair exactly those. - When the selection is empty, repair every finding in the most recent report that is Blocker, High or Medium with high confidence and a single obvious repair. Leave out any finding whose fix direction offers alternatives or depends on a product decision, and list it under "Not repaired". - When this conversation has no review report and the selection does not describe a defect precisely enough to locate it, say so in one sentence and stop. This is the only case where you stop without editing. Do not run a review from here. ## Repair For each selected finding, in severity order: 1. Open the location and confirm the defect still exists as described. When the code has moved on and it no longer applies, record it as "No longer applies" and do not edit. 2. Make the smallest complete change that removes the consequence for the stated trigger. Follow the surrounding code's patterns. Do not refactor, rename, reformat or tidy anything else, and do not weaken a test, type, lint rule or validation to make something pass. 3. When the finding named unprotected behaviour and the repository has tests for that area, add or adjust one focused test that fails without the repair. Stay inside the selection. When you notice another problem while repairing, do not fix it: mention it in one line