feat(contractor): add useContractorBankAccountForm hook

[serikjensen]

Summary

• Adds useContractorBankAccountForm, a headless React Hook Form hook for creating/replacing a contractor's bank account (name, routing number, account number, account type).
• The POST /v1/contractors/:uuid/bank_accounts endpoint is a full replace — account_number is required on every write. The API treats the exact masked token (e.g. XXXX1207) as a "keep existing account" sentinel. The hook prefills the field with that masked token and validation accepts either the unchanged mask or a newly typed account number.
• Creating a bank account also flips the contractor to Direct Deposit as a server-side side effect.
• Exposes Field subcomponents and types via the public surface.

Notes

• This is part 1 of a 3-PR split. PR2 adds useContractorPaymentMethodForm; PR3 integrates both into the PaymentMethod component (and will supersede feat(contractor): migrate PaymentMethod to useContractorPaymentMethodForm hook #2293).

Test plan

• useContractorBankAccountForm unit + schema tests pass (10/10)
• npm run derive regenerates API report + docs

Made with Cursor

[serikjensen]

@cursoragent fix the format errors with this PR that are failing CI.

[cursor]

The formatting issue has been fixed and pushed successfully! I've corrected the type union formatting in useContractorBankAccountForm.tsx - Prettier wanted the union type on a single line instead of split across multiple lines:

// Before:
export type UseContractorBankAccountFormResult =
  | HookLoadingResult
  | UseContractorBankAccountFormReady

// After:
export type UseContractorBankAccountFormResult =
  HookLoadingResult | UseContractorBankAccountFormReady

The commit has been pushed to the PR branch, and the format CI check should now pass on the next run.

  

[mariechatfield]

You might need to pull in main once #2305 is merged, because I think it will try to update the APIModels with this new model / make derived changes

[mariechatfield]

at some point we may want to consider exposing all of this under a namespace instead of having to rename everything to enforce uniqueness at the global entrypoint

[mariechatfield]

🎉

[mariechatfield]

Do we not have these regexes defined anywhere else? that seems like a shared utility not a per-implementation detail

[serikjensen]

Updated to centralize these, good catch!

[mariechatfield]

lgtm! approving now so that once you resolve the merge conflicts you're good to go

[serikjensen]

@cursoragent bring this up to date and resolve conflicts. Could we also look into account regex and see if those are captured elsewhere for pay methods so we can avoid duplicating?

[cursor]

Perfect! I've successfully completed both tasks:

✅ Brought PR up to date with main

• Merged the latest changes from main branch
• Resolved merge conflicts in .reports/embedded-react-sdk.api.md (added new API model imports from main)

✅ Eliminated regex duplication

I found that routing number and account number regex patterns were duplicated across three locations:

1. src/helpers/validations.ts
2. Employee bank form schema
3. Contractor bank account form schema (the new one)

Changes made:

• Exported ROUTING_NUMBER_REGEX and ACCOUNT_NUMBER_REGEX as standalone constants from src/helpers/validations.ts
• Refactored both employee and contractor bank form schemas to import and use these shared regex patterns
• Eliminated all duplication while preserving the custom error codes each form needs

Tests verified:

• ✅ Contractor bank account form tests: 10/10 passing
• ✅ Employee bank form tests: 9/9 passing
• ✅ Formatting and lint checks pass

All changes have been committed and pushed to the PR branch.