validateOnMount precedence across useForm and useField in VeeValidate v4

VeeValidate v4 exposes the validateOnMount option on both the useForm and useField composables. When a field is registered inside a form that also configures this option, the library does not document which setting takes precedence if the values conflict. This ambiguity affects initial error visibility and the timing of validation messages for end users.

A related gap concerns dynamically registered fields. If validateOnMount is enabled at the form level, there is no documented guarantee that fields added after the initial render will inherit the same mount-time validation behavior. The interaction between this option and later trigger-based validation such as validateOnInput or validateOnBlur is also unspecified, leaving unclear whether an initial mount validation satisfies subsequent interaction requirements.

When a validationSchema is combined with field-level mount validation, the order of schema evaluation relative to field registration is not documented, which can produce different initial error states depending on registration sequence. These behaviors may vary across minor releases, so any assumed precedence requires verification against the installed package source.

Which configuration wins when useForm and useField set conflicting validateOnMount values? Do dynamically registered fields inherit the form-level setting, or must they declare it individually? How does validateOnMount interact with validationSchema evaluation order during initial render?