fix: use macroTask before raf in delayFrame

The delayFrame function was using only raf, which could execute before
useWatch's React render completes. useWatch updates are scheduled via
macroTask (MessageChannel), and raf may run before or after macroTask
depending on the environment.

By adding macroTask before raf, we ensure the execution order is:
1. useWatch's macroTask executes → React setState
2. delayFrame's macroTask executes
3. raf executes → validation starts

This guarantees useWatch has updated before rules validation runs.

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

Author: zombieJ

src/hooks/useNotifyWatch.ts

@@ -5,7 +5,7 @@ import type { FormStore } from './useForm';
 /**
  * Call action with delay in macro task.
  */
-const macroTask = (fn: VoidFunction) => {
+export const macroTask = (fn: VoidFunction) => {
   const channel = new MessageChannel();
   channel.port1.onmessage = fn;
   channel.port2.postMessage(null);

src/utils/delayUtil.ts

@@ -1,9 +1,12 @@
+import { macroTask } from '../hooks/useNotifyWatch';
 import raf from '@rc-component/util/lib/raf';
 
 export default async function delayFrame() {
   return new Promise<void>(resolve => {
-    raf(() => {
-      resolve();
+    macroTask(() => {
+      raf(() => {
+        resolve();
+      });
     });
   });
 }