fix: useField validated-only mode for arrays (#5029)

Fix useField.validate() to properly handle 'validated-only' mode by
checking the field's validated flag. Previously, validated-only mode
was treated the same as force mode in useField, causing unintended
side effects when useFieldArray triggered form-wide validation after
mutations. Now, fields that haven't been interacted with yet will only
get their valid flag updated (silent validation) without incorrectly
marking them as validated or setting error messages prematurely.

Also adds comprehensive test coverage for useFieldArray with object
items including schema validation, meta updates (valid/dirty), nested
property mutations via computedDeep, and interaction with useField.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: logaretm

.changeset/fix-5029-fieldarray-schema-objects.md

@@ -0,0 +1,5 @@
+---
+"vee-validate": patch
+---
+
+Fix useFieldArray schema validation and meta updates for object items (#5029)

packages/vee-validate/src/useField.ts

@@ -207,6 +207,12 @@ function _useField<TValue = unknown>(
       return validateValidStateOnly();
     }
 
+    // In validated-only mode, only validate fields that have been previously validated
+    // This prevents showing errors on fields the user hasn't interacted with yet (#5029)
+    if (opts?.mode === 'validated-only' && !meta.validated) {
+      return validateValidStateOnly();
+    }
+
     return validateWithStateMutation();
   }