fix: ignore stale built-in validation result after reset in handleSubmit - #13761

I think there’s still a stale validation case here with form-level props.validate.

executeBuiltInValidation calls validateForm() before the new shouldAbort check, and validateForm() can call setError / clearErrors after async validation resolves.

So if reset() happens while props.validate is pending, the validation result could still write stale errors after the reset, even though onValid / onInvalid are correctly skipped.

Could we also cover the form-level async validate case and make sure we abort before applying its result?

Good catch, you are right. Pushed a follow-up: shouldAbort is now threaded into validateForm too, so a late props.validate result after reset no longer touches errors. Added a form-level regression test (fails before, passes after), full suite green.

nice, could you resolve the conflicts?

Rebased and reworked on the new architecture: the guard now lives inside executeBuiltInValidation right after each validateField, so a late field result after reset never reaches formState.errors either. Verified the gap first: the 3 regression tests fail on current master (stale onInvalid still fires), all green with this fix, full suite 1396 passed.

Thanks for merging.