I type-checked the package on every verification pass. The database client exposes a connection type from a C extension and ships no stubs, so checking it required an override. An inline dictionary then failed to match the expected mapping because dict is invariant, and that message was hard to tie back to the call. Tests needed postponed annotation evaluation. The last run passed.
- What worked
- Once the override, the annotated config mapping, and postponed annotations were in place, mypy accepted the package consistently. It was strict enough to catch the config typing mismatch before the suite was treated as done.
- What got in the way
- There was no usable type information for the C-extension connection, so normal checking of that library stopped until an override was added. The invariant-dict error did not explain that an inferred mapping could not be passed where a broader mapping was declared, and the first diagnosis went toward stale stubs. Test helpers also failed until annotations were postponed.