packages/vee-validate/src/useForm.ts:248

• useFormMeta is passed !!opts?.validationSchema, but validationSchema supports refs/computed (see isRef(schema) watcher). !!opts.validationSchema will be true for a ref even when unref(schema) is currently null/undefined, and it won’t update if the schema ref toggles. Consider passing a reactive boolean derived from unref(schema) (or passing schema into useFormMeta and unref’ing inside) so meta.valid reflects whether a schema is actually active.

  // form meta aggregations
  const meta = useFormMeta(pathStates, formValues, originalInitialValues, errors, !!opts?.validationSchema);

packages/vee-validate/src/useForm.ts:1131

• The vacuous-truth override (flag === 'valid' && hasSchema && !states.length) depends on hasSchema, but validationSchema supports refs/computed. If the schema ref toggles while there are no path states, a non-reactive boolean can make meta.valid incorrect. Consider making hasSchema reactive (derived from unref(schema) each time) so this stays in sync.

        if (flag === 'valid' && hasSchema && !states.length) {
          acc[flag] = false;
        } else {
          acc[flag] = states[mergeMethod](s => s[flag]);

packages/vee-validate/tests/useFieldArray.spec.ts:192

• This test no longer asserts the initial form.meta.value.valid state; it was replaced by a comment. Since the behavior change in #4855 is specifically about the initial meta.valid value when a schema exists and no path states are registered, add an explicit expectation here (before arr.push) so the regression is actually covered by the test.

  await flushPromises();
  // With a schema and no registered field path states, meta.valid is false (#4855)
  arr.push('');
  await flushPromises();

packages/vee-validate/tests/useFieldArray.spec.ts:248

• This test removed the assertion of the initial form.meta.value.valid value and left only a comment. Add an explicit expect(form.meta.value.valid).toBe(false) (before arr.prepend) to ensure the updated #4855 behavior is actually exercised.

  await flushPromises();
  // With a schema and no registered field path states, meta.valid is false (#4855)
  arr.prepend('');
  await flushPromises();

packages/vee-validate/tests/useFieldArray.spec.ts:304

• This test similarly replaced the initial meta.valid assertion with a comment. Add an explicit expectation before arr.insert so the initial invalid state with a schema and no registered path states is verified (not just implied).

  await flushPromises();
  // With a schema and no registered field path states, meta.valid is false (#4855)
  arr.insert(1, '');
  await flushPromises();

packages/vee-validate/tests/useForm.spec.ts:1502

• This test registers a field (useField('name')), so it doesn’t exercise the useFormMeta vacuous-truth fix (schema present + pathStates still empty). Add a test that provides validationSchema but registers no fields, and assert form.meta.value.valid is false initially.

        form = useForm({
          initialValues: { name: '' },
          validationSchema: {
            name(value: string) {
              return value ? true : 'Name is required';

packages/vee-validate/tests/useForm.spec.ts:1499

• These new tests type form as Record<string, any>, while the rest of this file commonly uses FormContext<...> for useForm() results. Using FormContext here would keep the test typings consistent and provide better compile-time checking of the API surface.

    let form!: Record<string, any>;
    mountWithHoc({
      setup() {
        form = useForm({
          initialValues: { name: '' },