code-harden-types

To add runtime validation to TypeScript webhook payloads, you parse untrusted boundary inputs using the project's existing validator, preferably zod. This enforces type safety and ensures the codebase typechecks after each file-level edit.

Removing unsafe typing in changed files involves scanning TypeScript and TSX sources to classify occurrences, applying safe mechanical fixes to redundant casts and suppressed type errors, and surfacing structural risks for human review without broad refactoring.

Yes, this type hardening approach works with existing validators other than zod. It requires using the project's existing validator to parse and validate boundary inputs, preferring zod but supporting any validator already integrated into the codebase.

To typecheck your codebase after fixing suppressed type errors, you apply safe mechanical fixes to changed files and ensure the project typechecks after each file-level edit, preventing type regressions from weak typing patterns at untrusted input boundaries.

You should not use automated type hardening for structural risks that require human review. The process applies only safe mechanical fixes to changed files and explicitly surfaces structural and legitimate cases rather than automatically refactoring them.