[athul-rs]

What

• The v1 form system under frontend/src/v1/components/patterns/form/:
  • useAppForm({schema, defaultValues}): react-hook-form with a zod schema. A field validates when it first loses focus, then on every change. A failed submit focuses the first invalid field.
  • FormField: binds one value to the v1 Field from P1-T03, so its error shows under the control and marks it invalid.
  • applyServerErrors(form, body): puts each backend error (drf_standardized_errors) under the field its attr names when that field is on screen. Every other error, and any body of another shape, becomes one form-level message.
  • FormFooter: No changes / N unsaved changes / Saving / Cannot save, with Save changes and Discard.
  • useLeaveGuard(dirty, confirm): the browser asks before the tab closes while the form is dirty, and the returned function asks confirm before a dialog closes or the caller navigates.
• New dependencies: @hookform/resolvers ^7.0.3 and zod ^4.6.7. react-hook-form is already on main.

Why

• P1-T06 (UN-4288): every v1 form validates, reports errors and guards unsaved work the same way. P1-T20 (schema-driven forms) and the Profile, Human Review settings, LLMWhisperer profile and API Hub admin pages build on it.

How

• Errors go to a field only when a field for that path is mounted, so an error for a value no field shows, or a schema rule with no path, appears in the footer instead of disabling Save with no message. A field that is hidden drops its error; the next submit validates again.
• Several errors on one attr are joined. {detail} (middleware), {error} (SDK handler) and malformed bodies fall back to their message or "Could not save. Try again."
• Callers call form.reset(saved) after a successful save. Discard and the change count compare against the last reset.

Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)

• No. Everything is new code under frontend/src/v1, which no route renders yet. v0 does not import it. The two new packages are only imported from v1.

Database Migrations

• None

Env Config

• None

Relevant Docs

• Spec: P1-T06 · Form system (version 5)
• Built against designs 83e4fff

Related Issues or PRs

• Stacked on UN-4287 [FEAT] Add the v1 text inputs on one field frame #2416 (UN-4287, P1-T03 text inputs). After UN-4287 [FEAT] Add the v1 text inputs on one field frame #2416 merges, this retargets to main.
• Jira also lists P1-T04 (UN-4301) and P1-T05 (UN-4300, UN-4300 [FEAT] Add the v1 toggles: Checkbox, Radio and RadioGroup, Switch and Slider (P1-T05) #2462) as blockers. The form core does not import them; their controls work inside FormField when they land.
• Deferred, with owners:
  • Route-change blocking needs a data router (useBlocker). v0 mounts a BrowserRouter, so useLeaveGuard covers tab close and caller-awaited dialog closes for now.
  • The confirm dialog is P1-T07 (UN-4316). useLeaveGuard takes confirm: () => Promise<boolean>; the shape is to be agreed.
  • The footer layout and colours follow the Profile and Platform frames once design picks one of the two drawn variants. It is plain status text for now.
  • applyServerErrors reads the raw backend body; it switches to the P0-T05 HTTP client's normalised error when that exists.

Dependencies Versions

• @hookform/resolvers ^7.0.3 (new)
• zod ^4.6.7 (new)

Notes on Testing

• form.test.tsx, 35 tests covering:
  • on-blur then on-change validation;
  • first-invalid focus;
  • server errors on fields, nested fields, hidden fields and form level;
  • malformed bodies;
  • footer states and button states while saving;
  • Discard;
  • the leave guard.
• Each guard was checked by mutation: 19 mutants, each fails the suite.
• typecheck:v1, lint:v1 and bun install --frozen-lockfile pass.

Screenshots

• None: no v1 route renders a form yet. The sample form lives in the tests.

Checklist

I have read and understood the Contribution Guidelines.

🤖 Generated with Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud