Release 0.8.3: fix DOB-carrier enrollment (date_of_birth nulled on submit)

[fuhrysteve]

Release of 0.8.3. Single fix; dev PR is LakeEriePartners/stream-connect-js-sdk#8.

Fix: carriers that ask for Date of Birth could never be connected

A member connecting a carrier whose credential form includes a Date of Birth field — Medical Mutual and SimplePay Health — could not complete enrollment. Whatever they typed was discarded before the request left the browser, the backend rejected the submission as missing a required field (HTTP 422), and the form came back with a red validation error. No input format worked, because the value never reached the server.

EnterCredentials.onSubmit spread the carrier's form values and then re-pinned SDK-controlled fields on top, including date_of_birth: values.dateOfBirth || null. Carrier form values are keyed by their JSON-schema property name — date_of_birth, snake_case — so the camelCase lookup was always undefined and the || null overwrote the member's input.

That line was inherited from 0.7.x, which spread ...formData last so the member's value won. 0.8.0 inverted the spread order so carrier schemas can't clobber payer_id / accept / tenants_accept, which silently promoted a dead line into data loss. The re-pin is gone; the payer_id / consent guards are unchanged.

Date fields also render as a native date input now. Carrier schemas mark them {"type": "string", "format": "date"}, which 0.8.x rendered as a bare text box with no format hint even though the backend's WTForms DateField only parses ISO YYYY-MM-DD.

The React Native hook (stream-connect-sdk-hook) kept the 0.7.x spread order and was never affected.

Impact

Introduced in 0.8.0 (2026-05-17), so roughly ten weeks in the field. It stayed invisible because the backend only validates the onboard form when creating a new policy holder — reconnecting an existing one was unaffected.

Measured on Medical Mutual: new policy holders carrying a date of birth ran 100% Jan–Apr (6/6, 7/7, 7/7, 3/3), then fell to 0/3 in May, 6/59 in June, 2/57 in July — the cliff lands on the 0.8.0 release. 184 SDK submissions over the last 60 days across four customers were affected.

Verification

npm run test (biome + tsc) passes. The affected carriers' generated schemas were confirmed to emit date_of_birth: {type: "string", format: "date", required: true}, so the new date branch fires. Both spread orders were replayed against the real value shape to confirm the regression reproduces and the fix corrects it, with the payer_id guard intact.