fix(zod): sanitize extracted definition refs

[FU-max-boop]

• I understand that this repository is auto-generated and my pull request may not be merged

Summary

• normalize whitespace to _ when zod v3 schemas extract reused definitions to root refs
• keep $ref values and definitions keys aligned after normalization
• add a regression test for reused schemas under property names containing spaces

Why

zodResponseFormat can currently produce $ref values such as #/definitions/example-scope_properties_group_properties_Thing With Spaces. Those literal spaces can be rejected by the API and make the generated schema harder to consume.

Fixes #1679.

Testing

• npx -y [email protected] test tests/helpers/zod.test.ts --runInBand
• npx -y [email protected] prettier --check src/_vendor/zod-to-json-schema/parseDef.ts tests/helpers/zod.test.ts
• npx -y [email protected] eslint src/_vendor/zod-to-json-schema/parseDef.ts tests/helpers/zod.test.ts
• npx -y [email protected] build
• git diff --check

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6ad9563f79

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Preserve unique names when normalizing refs

When a schema contains two distinct reused definitions whose extracted paths differ only by whitespace vs underscores, this normalization maps both to the same definition name. For example, reused properties named Thing With Spaces and Thing_With_Spaces now both emit refs ending in Thing_With_Spaces, so the later refs.definitions[name] = item.def overwrites the earlier definition and existing $refs can resolve to the wrong schema. The sanitizer needs to escape or otherwise disambiguate normalized names instead of using a lossy replacement.

Useful? React with 👍 / 👎.

[FU-max-boop]

Fixed in d3c808dc: extracted definition path parts now encode non-alphanumeric characters instead of replacing whitespace with underscores, so Thing With Spaces and Thing_With_Spaces stay distinct. The test now covers both names.