Make the expectation explicit
When a test adapts to a UI change, inspect what it actually did. Verify it selected the intended control and did not bypass an error or weaken an assertion just to finish.
Put it into practice
Keep the original acceptance criteria in the AuraCheck case. Review inconsistent runs and refine ambiguous instructions. “Self-healing” should never mean silently accepting incorrect behavior.
Try this on your next release
Choose one journey, define the expected result, and inspect the evidence from a completed run. Expand the suite after the first test is useful.