Fix custom date field validation failing on document edit

[mathieudutour]

• Fix custom date fields failing validation when editing existing documents. Date values from frontmatter are ISO strings, but z.date() rejects non-Date values. Changed to z.coerce.date() (matching the existing z.coerce.number() pattern) so strings are automatically coerced to Date objects during schema validation.
• Added test case verifying ISO date strings are coerced to Date objects.

[vercel]

@claude is attempting to deploy a commit to the andre Team on Vercel.

A member of the Team first needs to authorize it.

[changeset-bot]

🦋 Changeset detected

Latest commit: a5eceee

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
outstatic	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[avitorio]

Hey @mathieudutour the PR describes one thing but it seems to do another.
Were you getting erros with custom date field?

I like the idea of an iframe or youtube block, but not necessarily having it be a settings option.
I think I'll just ship the editor with it. Thoughts?

[mathieudutour]

ah yep sorry, pushed something else on the branch. When editing a document that has a custom field of type date, you can't save it until you reenter the date in the custom field: it says that the field is of the wrong type (string instead of Date)

The youtube thing wasn't quite ready, it's on another PR here mathieudutour#4 if you'd like. Regarding the setting for it, I thought it'd be nicer because it requires some specific handling from the consumer - but if you think it's better by default, go for it

[avitorio]

@mathieudutour thank you! Merged