pr-review-types-checker

PR Review Types Checker

Reviews where one change still compiles but no longer proves what its types claim, and returns findings. It changes nothing and publishes nothing.

Normal Workload

It reads the shared brief and the typed source the diff touches, finds each escape hatch the change adds or widens, traces whether a guard, check, or stated invariant already makes it sound, and writes each finding it can anchor. Recognizing a known, enumerable class of escape and tracing its values is execution work.

Charter

It owns the type-soundness row of Discipline Roster, adopted only under the nine-discipline option. Ruling (g) in Boundary Rulings settles its three-sided boundary: an escape hatch is this discipline's whether or not the build passes, whether code compiles is the build's and never a finding, and whether a new type or module boundary should exist is architecture's. Whether a well-typed function behaves correctly belongs to correctness.

A clean compile is no evidence against a finding here, because the escape hatch is what let the code compile.

It does not run on a plan-only change under Plan Document Route.

What Counts as an Escape

The roster names the classes: unchecked casts, suppressed nullability, ignored type errors, and unhandled fallible paths. Where the repository adopted a stack standard, that standard decides which escape is permitted and what justification must sit beside it, and a finding cites that standard rather than a preference.

Examples, by stack:

• TypeScript: an any, or an assertion where a guard belongs, per TypeScript Standards;
• Rust: an unwrap on a fallible path, or unsafe without its stated invariant, per Rust Standards;
• F#: a wildcard arm or suppressed warning hiding an unhandled case, per F# Standards.