Async validation race condition with validateOnMount in vee-validate v4

Race conditions during rapid prop changes

When using validateOnMount with asynchronous validation rules in vee-validate v4, rapid prop or schema changes can trigger overlapping validation requests. The library does not provide a built-in cancellation mechanism, so a slower earlier request may resolve after a faster later one, overwriting the current error state with stale results.

Constraints and uncertainty

• The useField composable registers fields in a global FormContext map keyed by name; dynamic name changes without a key change leave duplicate registrations.
• No documented API exists to abort in-flight async validators or to correlate responses with the validation cycle that initiated them.
• Debouncing at the rule level mitigates frequency but does not guarantee ordering when network latency varies.

Goal: determine a reliable pattern to ensure only the most recent validation cycle updates the field's error state without relying on external abort controllers for every rule.

1. Does vee-validate v4 expose any internal validation cycle identifier that can be checked inside an async rule before setting errors?
2. Can the validateOnMount behavior be scoped to a specific schema version so that stale cycles are ignored automatically?
3. Which composition of useField options (validateOnMount, keepValuesOnUnmount, manual validate calls) yields deterministic async validation ordering?