-
Notifications
You must be signed in to change notification settings - Fork 0
Date parser rejects toDateString output and one-digit month strings #313
Copy link
Copy link
Open
Labels
agent-readyReady for autonomous Symphonika dispatchReady for autonomous Symphonika dispatchenhancementNew feature or requestNew feature or requestsym:claimedSymphonika has claimed this issue for an orchestrated run.Symphonika has claimed this issue for an orchestrated run.sym:failedA Symphonika run reached a deterministic failed state.A Symphonika run reached a deterministic failed state.sym:staleA Symphonika claim exists without a live local run.A Symphonika claim exists without a live local run.
Description
Metadata
Metadata
Assignees
Labels
agent-readyReady for autonomous Symphonika dispatchReady for autonomous Symphonika dispatchenhancementNew feature or requestNew feature or requestsym:claimedSymphonika has claimed this issue for an orchestrated run.Symphonika has claimed this issue for an orchestrated run.sym:failedA Symphonika run reached a deterministic failed state.A Symphonika run reached a deterministic failed state.sym:staleA Symphonika claim exists without a live local run.A Symphonika claim exists without a live local run.
Summary
Zod v4.4.3
z.coerce.date()exposes Date string inputs that Node accepts but jsse turns into Invalid Date. This accounts for one failure in each mode of the #279 corpus.Reproduction
The remaining Zod coercion matrix (ISO, UTC, numeric, boolean, null, invalid values) behaves as expected for the test.
Expected
Date string parsing accepts the implementation-produced
Date.prototype.toDateString()form and the legacy one-digit month form used by web-compatible engines. Relevant specification surface: Date.parse / the Date constructor string branch; the spec requires round-trippingtoString,toUTCString, andtoISOStringoutputs when milliseconds are zero.