@dsptch-work/api-client 0.35.0 → 0.37.0

package/CHANGELOG.md

@@ -5,6 +5,335 @@ All notable changes to `@dsptch-work/api-client` are documented here. The format
 [Semantic Versioning](https://semver.org) — currently `0.x`, so breaking changes may land in a
 minor bump until `1.0.0`. See [RELEASING.md](./RELEASING.md) for the release and versioning process.
 
+## [0.37.0] - 2026-10-14
+
+### Added
+
+- `Jobs` adds `listJobDocuments()`, `createJobDocument()`, `getJobDocument()`,
+  `updateJobDocument()`, and `deleteJobDocument()`, with corresponding operation types and Zod
+  schemas. Use `path: { job_id }` for list/create and `path: { job_id, id }` for the others.
+  `JobDocumentParameters` and `JobDocumentUpdateParameters` support an external `url` or an
+  uploaded `file`; supply exactly one source on create and retain exactly one after an update.
+  Although create's generated fields are optional, the server requires nonblank `type` and `name`.
+  Register files through `DirectUploads.createDirectUpload()` with
+  `DirectUploadParameters.resource: 'jobs.documents'`, then send its signed ID as `file`.
+  `JobDocumentResponseObject` exposes nullable `url` and `file` download metadata;
+  `JobDocumentsResponseObject` wraps the list, and `ListJobDocumentsData.query` accepts
+  `'filter[type]'`. PWA documents are always `admin_only`; callers without job financial access
+  cannot read them. Grant the appropriate `jobs.documents:read` / `:create` / `:update` / `:delete`
+  scope. Deletion resolves `204` with no body.
+- `PositionParameters.pay_rates_rule_package_id` accepts a nullable package ID through
+  `Jobs.createPosition()` / `updatePosition()`. Choose a selectable package belonging to the path
+  job; an inaccessible, hidden, or other-job package returns `404`. Omit it on create to leave the
+  assignment unset, omit it on update to retain it, or send null to clear it. A cash-fringe package
+  on a non-PWA position returns `422`.
+- `SiteCheckInResponseObject` and `zSiteCheckInResponseObject` add required nullable
+  `duration_minutes`, the elapsed whole minutes between check-in and check-out, rounded to the nearest minute. It is null until the
+  visitor checks out. Add the field to typed fixtures for `OversiteSiteCheckIns` reads.
+- `TodoInboxTodoResponseObject` and `zTodoInboxTodoResponseObject` add required `priority`
+  (`'critical' | 'high' | 'medium' | 'low' | null`) and `category` (the same ten categories used by
+  compliance checks). `Todos.listTodoInbox()` now carries them on `kind: 'todo'` entries;
+  add both fields to typed fixtures. These are read fields, without new SDK write methods or
+  query filters.
+
+### Changed
+
+- **Breaking:** `UserParameters`, `UserCompanyCreateParameters`,
+  `UserCompanyScheduledChangesParameters`, `UserCompanyScheduledChange`, and `UserResponseObject`
+  replace `hourly_rate`, `training_annual_amount`, `employer_combined_health_amount`, and
+  `employer_combined_savings` with the corresponding `_cents` fields. Update calls to
+  `Users.createUser()`, `createCompany()`, `createUserCompanyScheduledChange()`, and
+  `updateScheduledChange()` and consumers of user and scheduled-change responses. Send decimal
+  strings in cents: `hourly_rate_cents: '3250'` replaces `hourly_rate: '32.50'`.
+  Response values are decimal-string cents such as `'3250.0'`, without a currency symbol;
+  obtain the currency from `People.getEmployment()`. Omitted amounts remain unset on create
+  or unchanged on scheduled updates, null clears them, and `'0'` sets zero. Old dollar-field
+  names return `400 unknown_key`; corresponding Zod schemas now expose only the cents names.
+- **Breaking:** `ProjectParameters` and `ProjectUpdateParameters` replace `budget` with
+  `budget_cents` for `Projects.createProject()` / `updateProject()`, including their Zod schemas.
+  Send `'123450'` for a budget of $1,234.50, rather than the former dollar string `'1234.50'`.
+  Null clears it and omission retains it on update. `budget` now returns `400 unknown_key`.
+  A budget, including null, still returns `422` while federal PWA tracking is off.
+  `ProjectResponseObject.budget_cents` and `budget_currency` are now optional nullable fields:
+  handle their absence when the caller cannot see project financials instead of assuming null.
+- **Breaking:** `ApprenticeshipWageScheduleParameters` / `ApprenticeshipWageScheduleUpdateParameters`
+  make `journeyworker_wage_cents`, `journeyworker_fringe_cents`, and `end_wage_cents` decimal
+  strings. `ApprenticeshipWageSchedulePeriodParameters` /
+  `ApprenticeshipWageSchedulePeriodUpdateParameters`, including nested `periods_attributes`,
+  likewise make `wage_cents`, `fringe_cents`, `wage_percent`, and `fringe_percent` strings.
+  Update the `ApprenticeshipWageSchedules` and `ApprenticeshipWageSchedulePeriods` write calls
+  to send `'2800.5'` cents or `'62.5'` percent, or echo the string from a read. JSON numbers
+  now return `422` at the field pointer; nullable fringe fields still accept null.
+  The corresponding Zod schemas enforce nonnegative decimal strings.
+- **Breaking:** `AssetsItemParameters.purchase_price_cents` and
+  `AssetsItemUpdateParameters.purchase_price_cents` change from `number | null` to
+  `string | null` for `AssetsItems.createItem()` / `updateItem()`. Send `'2800'` or `'2800.5'`,
+  or null to clear it. JSON numbers now return `422`; the corresponding Zod schemas enforce
+  nonnegative decimal strings. Purchase-price storage rounds beyond two decimal places in cents.
+- **Breaking:** `PositionParameters` now requires decimal strings for `cash_fringe_rate_cents`,
+  `hourly_rate_cents`, `pwa_wage_pay_rate_cents`, and `wage_adder_rate_cents` in
+  `Jobs.createPosition()` / `updatePosition()`. `start_time` / `end_time` no longer accept null;
+  supply real `YYYY-MM-DD` dates or omit the keys to retain dates on update or leave a new
+  position unscheduled. A supplied `pwa_details_attributes` object requires
+  `skill_level: 'journeyman' | 'foreman' | null`; use `{ skill_level: null }` rather than `{}`.
+  Send `pwa` as a boolean and nonblank string IDs, using null to clear nullable references.
+  Use `zPositionParameters` to validate these forms locally.
+- **Breaking:** `UserParameters` now types `enrolled_in_t_and_a` and `overtime_eligible` as
+  booleans, and `worked_annual_minutes`, `pto_annual_minutes`, `holiday_annual_minutes`, and
+  `training_annual_minutes` as nullable numbers instead of strings. Send whole-minute integers
+  and real booleans through `Users.createUser()`. `roles` no longer accepts null; omit it or
+  send `[]` to grant no roles, and send unique nonblank role strings. `company_user_pwa_info`
+  must be an object when supplied, without null. `zUserParameters` also checks nonblank names
+  and IDs and a date-only nullable `birth_date`. The old contact union is removed from the
+  generated type and schema, but the server still requires an email or phone unless
+  `skip_invite: true`; missing names return `400`, and invalid values return `422` with pointers.
+  Optional nullable profile fields now match accepted nulls. Omitted or null pay amounts now
+  remain unset rather than becoming zero. Send explicit '0' to designate zero: an unset
+  `training_annual_amount_cents` can fail the PWA designation check, and an unset
+  `hourly_rate_cents` can cause aggregate imports to return `HOURLY_RATE_NOT_FOUND` when no
+  position rate exists.
+- **Breaking:** `JobCreateParameters` and `JobUpdateParameters` are standalone objects.
+  `created_by_user_id` is optional in the create type so template copies can inherit it; plain
+  creates still need a creator and requesting company. Job feature-allocation flags,
+  `job_work_types_attributes`, `job_address_attributes`, and address `verified` no longer accept
+  null; omit them to retain current values. `region` now accepts null.
+  `time_card_start_day` is a number, with `zJobCreateParameters` / `zJobUpdateParameters`
+  requiring an integer from 0 through 6. `Jobs.createJob()` / `updateJob()` now refuse wrong
+  JSON types and malformed nested fields with `422` pointers. Send lowercase PWA mode keys
+  (`'all'`, `'pw_only'`, `'ap_only'`, `'none'`), booleans for flags, nonblank IDs, and declared
+  nested keys. Null can still clear nullable schedule dates and references.
+- **Breaking:** monetary write Zod schemas now reject malformed strings before submission,
+  matching server-side `422 validation_failed` errors with exact field pointers. Use plain
+  decimal strings with digits before the decimal point; blanks, whitespace, currency symbols,
+  scientific notation, and values such as `'.5'` are refused. This applies to employment pay,
+  time-entry and position rates, wage determinations, per diems, payroll amounts, project
+  budgets, asset prices, and production scope prices. Most values must be nonnegative;
+  `PaystubLineItemParameters.amount_cents` and `PositionParameters.pwa_wage_pay_rate_cents`
+  allow a leading minus. `RateRuleEffect.amount_cents` requires nonnegative whole-cent strings
+  such as `'300'`, without a decimal part. Handle these refusals through `Problem.errors`.
+- **Breaking:** `PaystubLineItems.createPaystubLineItem()` / `updatePaystubLineItem()` enforce
+  the documented string `amount_cents`, nonblank reference IDs, and lowercase
+  `contributor: 'employee' | 'employer'`. JSON-number amounts now return `422`, and omitting any
+  of create's four required fields returns `400 parameter_missing`. Send decimal-string cents;
+  negative and fractional amounts remain supported. `zPaystubLineItemParameters` /
+  `zPaystubLineItemUpdateParameters` now validate the ID and money patterns.
+- **Breaking:** `Users.createUser()`, `createCompany()`, `updateCompany()`,
+  `People.createEmployment()`, and `updateEmployment()` return `404` for a newly assigned
+  `manager_user_id` outside the key's visible people. Choose a visible manager. Employment
+  updates can still omit or resend an already held legacy manager; method signatures are unchanged.
+- **Breaking:** `Users.removeUserFromCompany()` now requires
+  `headers: { 'If-Match': etag }` in `RemoveUserFromCompanyData`. Read the employment ID from
+  `UserResponseObject.employment_id`, then obtain its validator through
+  `People.listEmploymentHistory()` or, while a version covers now, `People.getEmployment()`.
+  A key without those read scopes may send `'*'` to delete whatever state exists.
+  `RemoveUserFromCompanyErrors` adds `412` and `428`: re-read after a stale validator and add
+  the header when it is missing. Success remains `200` with the user body.
+- **Breaking at runtime:** `TimeEntries.createTimeEntry()` / `updateTimeEntry()` now interpret
+  `start_time` / `end_time` without an offset in the time card's pay schedule zone. If you mean
+  UTC, append `Z`; explicit `Z` or `±HH:MM` values retain their prior meaning. A bare date-time
+  now represents local wall time, including DST resolution and pay-period edge validation.
+  Request types remain strings, so TypeScript cannot catch a missing offset.
+- **Breaking:** `CompetenciesAssessmentCriteria.listAssessmentCriteria()` /
+  `getAssessmentCriterion()` replace the assessment key-activity read methods. The new
+  `CompetencyAssessmentCriterionResponseObject` uses `competencies_criterion_id`.
+  `CompetenciesEvidenceItems.listEvidenceItems()` / `getEvidenceItem()` keep their method names
+  but replace `path.key_activity_id` with `path.criterion_id`; evidence responses replace
+  `competencies_assessment_key_activity_id` with `competencies_assessment_criterion_id`.
+  Grant `competencies.assessments.criteria:read` and
+  `competencies.assessments.criteria.evidence_items:read` in place of the retired key-activity
+  scopes. These reads remain available to companies with Competencies enabled.
+  `CompetencyCriterionParameters` / `CompetencyCriterionResponseObject` replace nullable
+  `assessment_method` with nonnullable `assessment_methods`, an array of the same eight method
+  values. Use `[]` for no suggested methods; corresponding Zod schemas follow the new shapes.
+
+### Removed
+
+- **Breaking:** `JobParameters` and `zJobParameters` are removed. Import
+  `JobCreateParameters` / `zJobCreateParameters` or `JobUpdateParameters` /
+  `zJobUpdateParameters` for the owning write.
+- **Breaking:** `PositionParameters.per_diem_rate_cents` is removed, including from
+  `zPositionParameters`; sending it now returns `400 unknown_key`. Select `per_diem_id`
+  instead, since the rate comes from that per diem.
+- **Breaking:** `CompetenciesAssessmentKeyActivities`,
+  `CompetencyAssessmentKeyActivityResponseObject`, `ListAssessmentKeyActivities*`,
+  `GetAssessmentKeyActivity*`, and their corresponding Zod exports are removed. Migrate to
+  `CompetenciesAssessmentCriteria`, `CompetencyAssessmentCriterionResponseObject`,
+  `ListAssessmentCriteria*`, and `GetAssessmentCriterion*`.
+- **Breaking:** `ProblemTypeCatalog` and `zProblemTypeCatalog` remove `non_numeric_cents`.
+  Delete that case from exhaustive switches and handle malformed money as `validation_failed`
+  with field pointers instead.
+
+### Fixed
+
+- **Breaking response correction:** `AssetsItems.deleteDocument()` now resolves `204`
+  with no body. `DeleteDocumentResponses` replaces its `200: AssetsDocumentResponseObject`
+  arm with `204: void`, and `zDeleteDocumentResponse` validates void. Remove code that reads
+  the deleted document from the response; read it before deletion if needed.
+- `DirectUploads.createDirectUpload()` now stores `resource: 'assets.items.documents'` uploads
+  on protected storage, matching the asset document attachment. Request and response types
+  stay unchanged; continue attaching the returned purpose-bound signed ID to an asset document.
+
+See the [API changelog](https://dsptch.app/support/docs/developers/api-changelog#2026-10-14) for the
+complete REST contract details and error behavior.
+
+## [0.36.0] - 2026-10-13
+
+### Added
+
+- New class `ProjectDocuments`: `listProjectDocuments()`, `createProjectDocument()`,
+  `getProjectDocument()`, `updateProjectDocument()`, `deleteProjectDocument()`, and
+  `listProjectDocumentVersions()`. `ProjectDocumentParameters` requires `file` and
+  `performed_by_user_id`; get the signed file id through `DirectUploads.createDirectUpload()`
+  with `DirectUploadParameters.resource: 'projects.documents'`. `ProjectDocumentUpdateParameters`
+  accepts an optional replacement file and nullable `filename` / `description`.
+  `ProjectDocumentResponseObject.file` is nullable and exposes download metadata and `url`.
+  `ProjectDocumentVersionResponseObject` records audit events (`'create' | 'update' | 'destroy'`),
+  actor, and timestamp. List methods support cursor pagination; documents also support created/updated
+  date filters. Grant the appropriate `projects.documents:read` / `:create` / `:update` / `:delete`
+  scopes and `projects.documents.versions:read` for history. Corresponding operation types and Zod
+  schemas are exported.
+- `PayPeriods.getPayPeriod()` reads an individual period with `path: { id }` and the existing
+  `pay_periods:read` scope. New `PayPeriodResponseObject` and `zPayPeriodResponseObject` are shared
+  by show and list responses. `ListPayPeriodsData.query` adds
+  `'filter[timekeeping_pay_period_config_id]'` to select a pay schedule family; use the same id each
+  period returns as `timekeeping_pay_period_config_id`.
+- `ListEmploymentsData.query` adds `'filter[companies_department_id]'`. It selects the department
+  in the employment version at now or the supplied `'as_of[valid]'` time, so historical queries
+  follow historical assignments.
+
+### Changed
+
+- **Breaking:** `TimeEntryCreateParameters` is now a standalone object requiring
+  `timekeeping_time_card_id`, `start_time`, and `end_time` for
+  `TimeEntries.createTimeEntry()`. `TimeEntryUpdateParameters` keeps every field optional for
+  `updateTimeEntry()`. Both make `feature_ids` a nonnullable array; create's
+  `feature_allocation_acknowledged` and update's `confirm_allocation_conflict` accept booleans only.
+  Pass `[]` to clear feature allocations and omit the field to retain them on update. The generated
+  Zod schemas validate the split objects and required create timestamps; timestamp strings are
+  parsed by the server rather than restricted to Zod's ISO date-time format. Missing required
+  fields return `400`; wrong JSON types return `422` with field pointers, and unparseable timestamp
+  strings return `422 invalid_date`. Correct the values before retrying.
+- **Breaking:** `Users.updateCompany()` and `removeUserFromCompany()` take
+  `path: { user_id, id }` rather than `path: { user_id, company_id }`.
+  Update `UpdateCompanyData` / `RemoveUserFromCompanyData` call sites and their path-schema inputs;
+  `id` still holds the company id, so the actual HTTP URL is unchanged.
+- **Breaking:** `UserCompanyParameters.type` and `UserCompanyCreateParameters.type` are
+  `'EMPLOYEE' | 'CONTRACTOR'`, without `null`. Omit the value for the create default or to retain it
+  on update. `Users.createCompany()` / `updateCompany()` now reject wrong JSON types before saving:
+  send pay and benefit amounts as decimal strings, minute amounts as integers, and enrollment /
+  overtime flags as booleans. Creating requires a valid `hire_date`; on an administrative update,
+  null or blank `hire_date` still retains the employment start. Custom-field rows require nonblank
+  `custom_field_config_id` and string-or-null `value`; send a list of row objects, not an indexed
+  object. Malformed values return `422` with a field pointer; missing required fields return `400`.
+- **Breaking:** `UserParameters.group_ids` no longer accepts `null`. `Users.createUser()`,
+  `Groups.addUsersToGroup()`, `TimeEntries.createTimeEntry()` / `updateTimeEntry()`,
+  `ComplianceChecks.updateCheck()`, and form-assignment writes require unique nonblank IDs in
+  their group, feature, and assignee arrays. Null, blank, duplicate, or wrong-typed members now
+  return `422` before any write. Omit optional replacement arrays to retain them on update or send
+  `[]` to clear them; `UserGroupParameters.user_ids` must contain at least one ID. Corresponding
+  Zod schemas validate nonblank members and the group-add minimum; uniqueness remains server-side.
+- **Breaking:** `AssetsTransfers.createTransfer()` validates endpoint IDs and `line_items`
+  before moving stock. Supply at most one endpoint per side and at least one side; endpoint IDs
+  must be nonblank strings. Supply a nonempty array of rows with `assets_item_id` and integer
+  `quantity >= 1`; indexed row objects, fractional quantities, numeric strings, and unknown row
+  keys return `422` with pointers. Missing `line_items` or required row fields returns `400`.
+  `AssetsTransferParameters.from_assets_sub_location_id` / `to_assets_sub_location_id` now allow
+  `null` for unbinned stock, matching their generated Zod schemas.
+- **Breaking:** `ApprenticeshipWageSchedules.createWageSchedule()` / `updateWageSchedule()` and
+  `ApprenticeshipWageSchedulePeriods.createPeriod()` / `updatePeriod()` validate JSON types,
+  nullable fields, units, and nonnegative period values before saving. Send `periods_attributes`
+  as an array of row objects. Missing required fields return `400`; malformed or unknown nested
+  fields return `422` with pointers. A period must retain at least one of `min_minutes`,
+  `max_minutes`, or `num_competencies`, including after clearing values. `UpdateWageScheduleErrors`
+  now declares `422: Problem`; `CreatePeriodErrors` now declares `404: Problem` for a missing or
+  inaccessible schedule.
+- **Breaking:** `AssetsAttributes.createAttribute()` / `updateAttribute()`,
+  `Certifications.createCertification()` / `updateCertification()`,
+  `Projects.createProject()` / `updateProject()`, `ComplianceChecks.updateCheck()`, and
+  `Users.updateUser()` reject wrong JSON types and undeclared body fields before saving.
+  Supply nonblank required names, booleans for flags, and only declared keys; nested option-row
+  failures return `422` with a row pointer instead of `400`. The corresponding generated Zod
+  schemas validate nonblank names and IDs. Project date fields require real `YYYY-MM-DD` strings
+  or null; timestamps, loose dates, and empty strings return `422 validation_failed` with a pointer.
+  Send an IANA zone or null for `tz_name` and an integer `0`–`6` or null for `billing_start_day`.
+  `zUserUpdateParameters.birth_date` now validates
+  a `YYYY-MM-DD` calendar date or null; timestamps are not dates.
+- **Breaking:** `Timecodes` writes validate documented flags as booleans and reject blank names,
+  malformed values, and undeclared fields before saving. The create, correction, scheduled-change,
+  and genesis Zod schemas accept temporal strings for server parsing rather than enforcing ISO
+  date-time syntax locally. Omit create's `effective_date` to use now; sending null now returns
+  `422 validation_failed` instead of defaulting. Unparseable strings return `422 invalid_date`.
+  `updateTimecode()`, `scheduleTimecodeChange()`, and `shiftTimecodeGenesis()` validate the body
+  before `If-Match`, so malformed requests can return `400` / `422` ahead of `428`. Preserve the
+  header for valid writes and correct body errors before retrying.
+- **Breaking:** `UserCertifications.approveUserCertification()` requires a company key to name
+  a nonblank `UserCertificationApprovalParameters.approved_by_user_id`; a user key must omit it
+  and approves as itself. A company key's omitted approver is `400`; supplied null or malformed
+  values are `422` with `#/approved_by_user_id`, while a user key naming an approver is `403`.
+  Correct the body for the key type rather than retrying a refused actor.
+- **Breaking:** `People.updateCustomField()` requires a nonempty `custom_fields` array.
+  Missing the list or either row field (`custom_field_config_id` / `value`) now returns
+  `400 parameter_missing`, and extra row keys return `422 validation_failed` with a row-field
+  pointer. Body validation precedes `If-Match`; keep the precondition header for valid batches.
+- **Breaking:** `JobWageDeterminations` and `ProjectWageDeterminations` writes validate
+  subtype fields before saving. Send decimal-string cents, nonblank classifications and trade
+  IDs, and lowercase `construction_category` values. Required create-field omissions now return
+  `400 parameter_missing`; malformed values return `422 validation_failed` with exact pointers.
+  Federal create requests must omit `regional_fields`; even `{}` is refused. On edits,
+  scheduled changes, and genesis shifts, invalid calendar dates (`effective_from` /
+  `effective_date`) now return `validation_failed` instead of `invalid_date`, before `If-Match`
+  failures. Send real `YYYY-MM-DD` dates and handle `Problem.errors` before retrying.
+- **Breaking:** manager and safety-manager user keys no longer receive selectable packages from
+  `PayRateRulePackages.listPayRateRulePackages()`. `getPayRateRulePackage()` and the corresponding
+  `PayRateRules.listPayRateRules()`, `getPayRateRule()`, and `listPayRateRuleHistory()` lookups return
+  `404`. Use an administrator user key for reusable recipe details. Administrator user keys,
+  company keys, and existing reads of hidden determination packages retain their access.
+
+### Removed
+
+- **Breaking:** `TimeEntryParameters` and `zTimeEntryParameters` are removed. Use
+  `TimeEntryCreateParameters` / `zTimeEntryCreateParameters` for creates and
+  `TimeEntryUpdateParameters` / `zTimeEntryUpdateParameters` for edits.
+- **Breaking:** `RegionalWageDeterminationFields` and `zRegionalWageDeterminationFields` are
+  removed. Regional write fields are inline in the owning create, update, or scheduled-change
+  type. Derive a reusable type with
+  `NonNullable<RegionalJobWageDeterminationParameters['regional_fields']>` or its project
+  counterpart. Categorized-fringe fields now allow null in the TypeScript and Zod shape; the
+  server still requires nonnull fringe values for regions that require them and rejects fields
+  the region does not support.
+
+### Fixed
+
+- `TimecodeScheduledChangeParameters.name` is optional. `Timecodes.scheduleTimecodeChange()`
+  can change flags or another attribute without resending the name; only `effective_date` is
+  required. `zTimecodeScheduledChangeParameters` matches this accepted partial write.
+- `ApprenticeshipWageScheduleParameters.periods_attributes` makes `period_number`, `wage_percent`,
+  and `wage_cents` optional in nested rows, including edits or removals of existing periods.
+  Standalone `ApprenticeshipWageSchedulePeriods.createPeriod()` still requires all three.
+  `ApprenticeshipWageScheduleUpdateParameters.periods_attributes` and
+  its Zod schema now use simple row objects, so partial edits need not repeat a progression
+  threshold. The server validates the resulting period rather than just the supplied fields.
+- `ProjectParameters.budget` and `ProjectUpdateParameters.budget` allow null, including through
+  their generated Zod schemas. Send null to clear a budget, a decimal string to set it, or omit
+  it on update to retain it.
+- `FederalJobWageDeterminationParameters` and `FederalProjectWageDeterminationParameters`
+  expose optional nullable `overtime_package_id`. `RegionalJobWageDeterminationParameters` and
+  `RegionalProjectWageDeterminationParameters` expose optional nullable `class_code` and
+  `construction_category`. Corresponding create Zod schemas retain those fields instead of
+  stripping them. Regional `class_code` / `construction_category` remain ignored by the server,
+  and Federal creates still refuse a non-null overtime package; these are schema corrections.
+  Method names and response types are unchanged.
+- `zComplianceCheckParameters.time_due` accepts a string or null instead of requiring ISO
+  date-time syntax. The server parses supplied dates and returns a validation problem for
+  malformed input; consumers using the schema can submit the server's accepted date forms.
+- `AssetsProducts` writes with an out-of-range `default_minimum_quantity` and
+  `ProductionCompletions` writes with an out-of-range `quantity_completed` now return
+  `422 validation_failed` instead of `500 internal_error`. These range problems have no field
+  `errors` array; correct the number rather than retrying a server failure.
+
+See the [API changelog](https://dsptch.app/support/docs/developers/api-changelog#2026-10-13) for the
+complete REST contract details and error behavior.
+
 ## [0.35.0] - 2026-10-12
 
 ### Added