Adversarial review

Independently reconstruct the affected system, then hunt for the decision that would make a whole family of code or planned work unnecessary. Ask what stronger invariant, different owner, or smaller promise would let the system collapse. Passing tests and individually defensible abstractions do not settle whether the model deserves to survive.

Hold the user's desired outcome steady while challenging the implementation, remaining plan, and inherited requirements. Reconstruct from actual callers so the implementer's explanation does not become the reviewer's frame. Even when no bugs are apparent, construct a concrete smaller alternative to stress-test the current design. Zoom out when local cleanup leaves the machinery intact.

Success is a better-supported next decision. Count complexity introduced as well as removed, including work transferred to the user. Keeping the design is valid after testing the alternative; neither forced disagreement nor deletion at any cost is the job.