react-doctor/zod-v4-no-deprecated-schema-apis

Migrate deprecated Zod 4 schema APIs: z.object().strict() to z.strictObject(), z.nativeEnum to z.enum, z.record(value) to z.record(key, value), z.function().args().returns() to z.function({ input, output }).

Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

Fires only when an import binding resolves to zod (named, aliased, default, or namespace import) and the call/member matches one of: a deprecated top-level factory call z.nativeEnum/promise/ostring/onumber/oboolean/oarray; a .create() call on a dropped factory like z.string.create() or z.object.create(); a single-argument z.record(value); z.literal(Symbol(...)) or z.literal(Symbol.iterator); a z.function().args(...)/.returns(...) chain; z.object().strict()/strip()/passthrough()/nonstrict()/merge()/deepPartial() (including computed form z.object({})["strict"]()); z.number().safe(); .refine() whose SECOND argument is a function/arrow; or .Enum/.Values accessed off a z.enum() call. The detector requires a DIRECT method call on the factory call expression and resolves the import binding, so it does NOT fire on: z.strictObject({}), z.enum(Role), two-argument z.record(key, value), or z.function({ input, output }) (already Zod 4 forms); .strict()/.safe() called on a stored variable rather than inline on the factory call (e.g. const s = z.object({}); s.strict()); identically-named methods on non-zod objects (createValidator().object({}).strict()); dynamic bracket access with a variable key (schema.object({})[method]()); refine with an options object second arg ({ error: "..." }) or single-arg refine; and retained chains like z.number().int().min(0).max(100).

Evidence boundary

The diagnostic proves only that the detector’s modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.

Establish the environment, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.

Record one outcome:

• Confirmed failure: The required evidence establishes the violation.
• Rejected: A documented exception or false-positive predicate applies.
• Needs evidence: Named evidence can still be collected.
• Unavailable: Required evidence cannot be collected in this run.
• Waived with evidence: An authorized, scoped exception applies to an established failure.
• Observation: The review records an optional tradeoff without claiming a defect.

A waiver records its scope, authority, evidence, and review condition. It is not a pass or false positive.

Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.

Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

Replace the deprecated form with its Zod 4 equivalent: z.object({...}).strict() becomes z.strictObject({...}) (and .passthrough() to z.looseObject, .merge(b) to a.extend(b.shape) or spread); z.nativeEnum(X) and z.enum(["a"]).Enum/.Values become z.enum(X) reading members off the schema directly; z.string.create()/factory.create() drops .create() to just z.string(); single-arg z.record(valueSchema) gains an explicit key schema z.record(z.string(), valueSchema); z.function().args(z.string()).returns(z.number()) becomes z.function({ input: [z.string()], output: z.number() }); z.number().safe() uses .int() or explicit .min/.max bounds; z.literal(Symbol(...)) uses a dedicated symbol schema; and a function passed as refine's second argument moves to an options object z.string().refine(fn, { error: "..." }). See https://zod.dev/v4/changelog

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.