apply-findingslisted

Apply only behavior-preserving findings whose exact patch can be guarded. Leave design and product decisions unchanged. ## Scope and mode Resolve scope in this order: 1. files or PR explicitly named by the user; 2. staged and unstaged task changes; 3. current branch versus the repository's verified default/base branch. If nothing changed, report that and stop. Do not include unrelated dirty files. An explicit review-only/no-edit request or inspection of another contributor's PR without edit authorization means **review-only**. Authorship, Git user name, tool availability, and branch ownership do not grant or remove edit authority. When a PR head differs from the current checkout, inspect it in an isolated temporary worktree and verify its tracked files are unchanged before removal. Do not switch the user's active checkout. If remote metadata is unavailable, use a supplied/local head and state what remains unknown. ## Collect findings Use, when available: - findings from the preceding code review; - repository-local explicit instructions applicable to changed files; - configured lint diagnostics; - clear majority conventions in the same file, then sibling files, excluding the target itself. If no preceding review exists, label a fallback review and inspect the diff for correctness, security/authorization, error paths, and applicable repository rules. Do not invoke another review workflow implicitly. Before classifying, reread the current source/target and revalidate