<!-- Replace every placeholder and remove all HTML comments before presenting the report. Keep each prose paragraph and list item on one source line. Do not add change-count tables, bot-update timestamps, reproduction-completeness bookkeeping, import-audit details, exhaustive traceability appendices, raw URLs, or artifact hashes. -->

PR #<number> ecosystem summary

<Summarize the distinct diagnostic behavior changes and their significance. Lead with the analysis readers need; do not describe how the report was generated.>

<Distinct behavior change>

Report entries:

• <project1 file1.py:line>
• <project1 file2.py:line>
• <project2 file1.py:line>

<Explain the exact behavior on the merge base and PR. Group additional entries here only when the same explanation and minimized reproducer account for all of them.> <!-- A minimal reproducer should annotate every line with a new, changed, or removed diagnostic using comments immediately above that line. Include the full error messages and error codes from both revisions, including duplicates. For example: ```python from typing import Final # Merge base: `[error-code-1] "Some error message"` # PR: no diagnostic x: Final = 42 if x: # Merge base: `[error-code-2] "Some error message"` # PR: `[error-code-2] "Some other error message"` Y = 56 ``` -->

Reproduction

• Detailed report: ecosystem-analyzer report
• Actions run: run <id>
• Ruff comparison: <merge-base> to <pr-revision>
• ecosystem-analyzer: <revision>
• mypy-primer: <revision>
• Project Python: <project: version, ...>
• Dependency cutoff: <EXCLUDE_NEWER>
• Comparison method: <concise exact commands or method used to run both copied ty binaries>