Add Client Name to Spectora Lite integration

Objective

• Ensure client name is available on ancillary reports (insurance and state-mandated reports, including state WDO forms) when jobs are created as Attik standalone orders and synced to Spectora via the Spectora Lite integration.
• Update the Spectora Lite integration so that the client's name is pulled from the Attik order and included in the data sent to Spectora, so report templates that require the client name (e.g. insurance and state WDO forms) can display it correctly.

Background

• Ancillary reports such as insurance and state-mandated (e.g. WDO) forms require the client's name to be populated on the report. For Attik standalone orders, the Spectora Lite integration currently pushes a minimal set of data into the Spectora order (e.g. only what is needed for the report template, with no client info in the current design). Product requirement: update the integration to include client name so these reports can be completed correctly in Spectora.

Scope

Backend

• Spectora job creation: The flow that builds and sends the job payload to Spectora for Attik-originated orders lives in attik-backend/src/util/functions/spectora/createSpectoraJob.ts. The request body type and payload shape are defined in attik-backend/src/util/functions/spectora/spectoraJobRequest.ts (e.g. SpectoraJobRequestBody, contact/client structures). The Spectora API types and inspection-post request shape are in attik-backend/src/util/functions/spectora/spectoraAPIReturnTypes.ts. Where the integration currently omits client info for "Spectora Lite" or standalone orders, add or pass through the client name (e.g. from the inspection's people/contacts or quote contact) so it is present in the payload sent to Spectora.
• Inspection/quote data: The inspection and quote models (e.g. attik-backend/src/models/inspectionSchema.ts, attik-backend/src/models/quoteSchema.ts) and any contact/people population used when creating the Spectora job are in scope. The dev must determine the correct source for "client" (e.g. a specific contact role on the order) and ensure that value is included in the Spectora payload for standalone/Lite flows.
• Routes: Any route that triggers Spectora job creation for standalone orders (e.g. inspection or quote booking that calls createSpectoraJob or the spectora route in attik-backend/src/routes/spectora.ts) is a touchpoint; ensure the client name is available when the payload is built.

Frontend

• If the client name is missing because it is never collected or sent from the scheduler/booking UI, the frontend flows that create or update orders (e.g. scheduling, quote conversion) may need to capture or pass it; the primary change is likely backend (what we send to Spectora). If the backend already has access to the client from inspection/quote/people data, no frontend change may be required.

References

• Spectora job creation: attik-backend/src/util/functions/spectora/createSpectoraJob.ts
• Spectora job request types: attik-backend/src/util/functions/spectora/spectoraJobRequest.ts
• Spectora API types: attik-backend/src/util/functions/spectora/spectoraAPIReturnTypes.ts
• Spectora routes: attik-backend/src/routes/spectora.ts
• Integration context (Spectora Light): attik-backend/docs/TRANSCRIPT_INTEGRATIONS_ROADMAP_2026-02-27.md (item 14 – current "no client info" design; this issue updates that for client name where required by reports)