402 - Test Correction

Start from a failing automated test and determine the correct correction path before editing anything.

This workflow exists for the cases where a red test does not immediately tell you whether the defect is:

1. a broken or stale test
2. a real source-code defect
3. an intentional product behavior change that now conflicts with the old test

The job of 402 is to classify the failure, explain why, and only then apply the smallest correct fix.

Output: Corrected test files, corrected source files, or a blocking user decision when the failing test exposes an intended behavior change or product-capability ambiguity.