Challenge Every Guard

Every guard is a claim that a failure happens. Keep the guards evidence supports, place them where the sibling code places them, and delete the rest. A change shaped this way is smaller, matches its neighbours, and reviews in one sitting.

Copy the sibling first

For every file the change touches, read three or more existing files of the same kind and match the majority shape: naming and placement, imports, test setup, fakes and fixtures, assertions, errors and logging, wiring, helpers. When files disagree, follow the majority and name the minority drift instead of copying it.