Date‑time input stored as UTC despite user‑entered local offset in Jetstream profile form

Goal: Ensure that date‑time values entered by users are stored and displayed according to their selected regional timezone.

Constraint: Jetstream’s registration and profile forms do not include a timezone selection field, so date‑time inputs are parsed using the server’s default timezone (typically UTC) without automatic offset conversion, requiring developers to add a custom user attribute and conversion logic.

Uncertainty: It remains unresolved whether Jetstream should supply a standardized timezone selector component, modify its validation rules to handle local offsets, or provide a middleware that sets the application timezone from the user’s preference.

Should Jetstream provide a reusable timezone selector component in the profile scaffold?

Should Laravel’s date validation rules automatically apply a user‑specific offset before persisting?

Should a middleware be standardized to set the application timezone based on the authenticated user's stored preference?