Upgrade ty to 0.0.63 and fix new MRO-based method-override diagnostics

[davegaeddert]

Summary

• Bump ty from 0.0.61 to 0.0.63 (see 0.0.62 and 0.0.63 changelogs).
• ty 0.0.62 added MRO-based checking for inherited method conflicts, which surfaced 51 new invalid-method-override diagnostics in plain-postgres and 6 in plain-email.
• plain-postgres: fixed the actual signature mismatches in the shared base classes instead of suppressing per subclass:
  • RegisterLookupMixin.get_lookup/get_transform (query_utils.py) and BaseExpression.get_lookup/get_transform (expressions.py) had mismatched parameter names (lookup_name vs lookup/name) — renamed to match.
  • RegisterLookupMixin.get_transform's declared return type included Callable[..., Any] even though its own body could never return a bare callable — narrowed to type[Transform] | None, then further corrected (along with BaseExpression.get_transform, EncryptedFieldMixin.get_transform, and JSONField.get_transform) to Callable[..., Transform] | None, since JSONField.get_transform genuinely returns a KeyTransformFactory instance alongside Transform subclasses. This also let a pre-existing # ty: ignore[invalid-return-type] in expressions.py be removed, since the types now agree.
  • Lookup.resolve_expression was declared to return the concrete Lookup type instead of Self, which conflicted with BaseExpression.resolve_expression -> Self. Its body already returns a copy of self, so Self is the accurate annotation.
  • Fixing the root base classes cascaded the fix to every subclass in the MRO (math/text/datetime functions, Exact, GreaterThan, DataContains, etc.) — no new ignores were needed for plain-postgres.
  • Also renamed ForeignObjectRel.get_lookup's parameter for naming consistency with the rest of the package (flagged in review; this one isn't part of the affected MRO chain, so it wasn't required by ty, but keeps the convention consistent).
• plain-email: added # ty: ignore[invalid-method-override] on the three SafeMIME* classes, consistent with the existing ignore already used on set_payload in the same file — MIMEMixin intentionally diverges from stdlib email.message.Message's as_bytes/as_string signature (linesep param instead of policy) to avoid mangling From lines, which can't be reconciled without changing behavior.

Test plan

• ./scripts/type-check . (repo-wide ty check) passes with zero diagnostics
• ./scripts/test plain-postgres — 754 passed, 1 skipped
• ./scripts/test plain-email — 13 passed
• uv run ruff check / ruff format --check on all changed files
• Ran /simplify (reuse, simplification, efficiency, altitude review) — no issues found
• Ran /code-review — one style-consistency nit (the reverse_related.py param name), applied

🤖 Generated with Claude Code

https://claude.ai/code/session_01VXaR5tbB8DjR3dLDzsDALA

---

Generated by Claude Code

[pullapprove5]

PASS: 1 review scope passed

	Scope	Progress
✅	all	0/0

View in PullApprove

Next steps:

• @davegaeddert: Merge or close

[github-actions]

Codex second opinion — not run: Claude did not approve (review state: none).