Follow-up under #548 and #416 after #657.
The pinned Zod 4.5.2 graph has 43 TS2344 diagnostics. Forty-one in src/v4/core/api.ts share one exact shape: a literal type argument such as "coerce" or "when" is checked against Exclude<keyof T["_zod"]["def"], ...> after T has been supplied as a concrete schema interface, but Home validates the literal against the unsubstituted declaration constraint.
A strict same-file reduction defines ExtraKey<T extends Base, K extends Exclude<keyof T["_zod"]["def"], "type" | "checks" | "error"> = never> and instantiates it with a concrete StringSchema. TypeScript 6.0.3 and native TypeScript 7.0.2 accept "coerce" and "when", then report exactly one TS2344 for appended "missing" with the resolved constraint "coerce" | "when". Current ReleaseFast Home reports three TS2344 diagnostics, including the two valid keys, and renders the unresolved generic constraint.
Resolve each later parameter constraint in the effective earlier-argument substitution environment before validating its explicit argument. Preserve dependent defaults, constraint provenance and diagnostic wording; keep the invalid literal rejected. Do not special-case key text, Zod names, Exclude, or suppress TS2344.
Add permanent positive/appended-negative controls calibrated against TS 6.0.3 and native TS 7.0.2, run the complete checker and Program suites, and compare every pinned Zod diagnostic identity against the current 489/484 checkpoint and immutable 602 baseline. Keep performance timing gated on zero under #548.