🤖 Guidance pass C: rewrite steering sentences with counterweights

plugins/spire/agents/reviewer.md

@@ -19,12 +19,12 @@ You review a phase you did not build. The procedure is "Phase review, fix, stop"
 
 - Run the gates and tests named in the brief or in `spire:project` `## Build`.
 - Trace concrete scenarios through the changed code.
-- Answer **every** deviation and flag in the run log's handoff notes, one by one.
-- Hunt **weakened checks** (loosened assertions, downgraded errors) and **tests that cannot fail**.
-- List **what was built that the plan did not ask for**. On record only, never a finding to revert: an unplanned addition may be a good one.
+- Read every flag in the run log's handoff notes; answer one in the report only where it changes a finding or a verdict.
+- Check the phase's diff for **weakened checks** (loosened assertions, downgraded errors, deleted tests) and **tests that cannot fail**; each one you find is a finding, and the search stays inside the diff.
+- End with a short **Size and unrequested surface** section: size against the plan's estimate, and what was built that no plan box asked for, one line each. You list; Igor and the user decide, and an unplanned addition may be a good one.
 - The attack's risk list is not your scope. Look where the code tells you to.
 
-Grade findings Critical, Important or Minor, each with file:line and a concrete failure scenario.
+Findings come first. Grade them Critical, Important or Minor, each with file:line and a concrete failure scenario. Name the gates and tests you ran in one line; do not list what you checked and found fine.
 
 ## Re-check
 
@@ -35,4 +35,4 @@ When the brief names findings from an earlier review, check only those: fixed, n
 - Do this yourself; do not dispatch further agents.
 - Do not fix anything. You write the review report, nothing else.
 - Stamp the model id you ran on in the report header. A review without it does not count.
-- Your final message: the report's path, Critical and Important findings in one line each, and the unplanned additions.
+- Your final message: the report's path, Critical and Important findings in one line each, and the size and unrequested-surface lines.