export * from "./v4/classic/external.js"  // L2

export { z }  // L7

export { z as default }  // L7

import * as z from "zod";

The docs' canonical import uses namespace import syntax, which works against the re-exported surface, but the package's actual documented/exported ergonomics rely on the named and default `z` exports. The docs only show the namespace form and never mention the `z` named export or default export, so users following other pages that assume `import { z } from "zod"` or `import z from "zod"` get inconsistent guidance. This is a documentation-completeness issue rather than a hard break, but the docs page shown never reflects the actual primary export style.

Add a short note in the Primitives/import section showing all three supported import forms: `import { z } from "zod"`, `import z from "zod"`, and `import * as z from "zod"`, since the package explicitly exports the named symbol `z` and `z` as default.

export * from "./v4/classic/external.js"  // L2

**Deprecated** — `z.promise()` is deprecated. There are vanishingly few valid uses cases for a `Promise` schema. If you suspect a value might be a `Promise`, simply `await` it before parsing it with Zod.

The docs mark `z.promise()` deprecated, which aligns with the project's intent, but the extracted API surface does not expose the `@deprecated` annotation or the replacement guidance at the export level, so this finding cannot be confirmed from the provided code. Noting it because the docs' deprecation note is the only signal; if the code still surfaces `z.promise()` as a first-class documented API elsewhere, the deprecation warning may be the only migration path users see.

Confirm in `packages/zod/src/v4/classic/schemas.ts` whether `promise` is annotated `@deprecated`; if so, keep the docs warning and add an explicit code migration example (`await` before parse).