## Summary

- Adds **+ Add technician** to the WO board vendor dialog when a company context is known (from the row or the current selection).
- Creates the technician via the existing **`POST vendors`** REST endpoint (`vendorsApi.create` / `useCreateVendor`), reusing the selected company's profile fields and registering a new `contactName` under that company.
- After a successful create, the new technician is merged into the dialog options and auto-selected for the single-tech WO assignment.

## Backend

Uses the established vendor create API (`API_PATHS.rest.vendors` → `POST /vendors`). Each vendor record represents one technician; linking to an existing company is done by sending the same `companyName` (and optional `companyId` when available from facets elsewhere). **No new endpoint** — confirm with BE that duplicate `companyName` + distinct `contactName` rows are the intended model for multiple technicians per company.

## Test plan

- [ ] Open a WO with an assigned company on the board → vendor cell → **+ Add technician** is visible.
- [ ] Create a technician with name (+ optional phone) → new tech appears selected in the dialog.
- [ ] Save → WO row shows the new technician and vendor id.
- [ ] Open dialog on a row with no company → add affordance hidden until a company/tech context exists.
- [ ] `npm run verify`

## Out of scope

- Multi-POC, multi-tech arrays on WO, vendors directory redesign.