specflow-receive-reviewlisted

# Specflow: Receive Review ## When to use Process review feedback with technical rigor instead of performative agreement — verify each suggestion against the spec, the compass rules, and the code as it actually is before applying it, and reject the ones that do not hold, with the reason. Use when a review has come back, when the user says "here's the feedback", "the reviewer said", "address these comments", or when specflow-develop's review ladder returns findings. Pairs with specflow-request-review. Disagreements are settled by the spec, a rule, or a command someone can run — never by who sounded more certain. ## The Iron Law NO SUGGESTION APPLIED WITHOUT VERIFYING IT FIRST Violating the letter of this law is violating the spirit. If you find yourself constructing a reading under which this suggestion is obviously right and needs no check, that construction is the violation. Hardening mechanisms per `skills/_conventions/hardening.md`. ## The failure this prevents Agreeing is cheap and checking is not, so an agent under review drifts toward agreement. It thanks the reviewer, applies the suggestion, and the transcript looks excellent. Two of the five suggestions were wrong, and working code is now broken in a way that reads, in the diff, as responsiveness. A review suggestion is a **claim about your code made by someone who read less of it than you did**. Claims get checked. ## The loop, per suggestion Take them one at a time. **1. Understand it.** What exactly is