Precognition + Inertia <Form> — prefer adapter hooks in Inertia, or wrapper in laravel/precognition?

[kaspernowak]

Context
Laravel starter kits moved from useForm to the new Inertia <Form>; Precognition currently targets useForm, so there’s no first-class live-validation path for <Form>. I created two PRs with separate approaches to solve this problem:

Option A — Adapter in Inertia (provider-driven)

• PR: Vue 3 Form Provider‑driven Live Validation #2555
• Adds opt-in live validation to Vue <Form> (precognitive, validateOn, validationTimeout) and a provider registry so integrations like Precognition can plug in without hard-coding Laravel specifics. Keeps Inertia agnostic.

Option B — Wrapper in laravel/precognition

• PR: Vue-Inertia: Precognition-enabled Inertia Form component laravel/precognition#128
• Ships a <PrecognitionForm> that composes Inertia’s <Form> and wires live validation (per-field opt-in, debounce, normalized errors). Keeps changes out of Inertia; Precognition owns the integration.

Questions for Inertia maintainers

1. Would Inertia accept a generic validation adapter surface (event-delegated field changes + setError/clearErrors bridge) in core? This enables Laravel Precognition (and others) while staying framework-agnostic.
2. If not, is the preferred approach to keep this in laravel/precognition as a wrapper, with Inertia remaining unchanged?