<!-- Replace every placeholder and remove all HTML comments before presenting the report. Keep each prose paragraph and list item on one source line. Number retained change subsections consecutively within each section, restarting at 1 for each section. Do not mention the absence of new panics, overflows, or timeouts. 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 meaningful changes to project failures and diagnostic behavior, including changes involving intermittent severe failures, along with their significance. Lead with the analysis readers need; do not describe how the report was generated.>

<!-- Omit this entire section if no stable project failures changed. Repeat its numbered subsection for each distinct failure. -->

Project failures

1. <New, fixed, or changed project failure>

Affected projects:

• <project>: merge base: <base outcome>; PR: <PR outcome>.

<Explain the crash, panic, overflow, timeout, or abnormal exit, including relevant stderr where applicable.>

<!-- Omit this entire section if no severe failure involving intermittent outcomes changed. Repeat its numbered subsection for each distinct change. -->

Intermittent severe failures

1. <New or changed intermittent panic, crash, overflow, or timeout>

Affected projects:

• <project>: merge base: <base outcome and count/runs, or not present>; PR: <PR outcome and count/runs, or not present>.

<Explain the change in failure behavior and relevant stderr. Do not include unchanged failures or frequency-only fluctuations.> <!-- Omit this entire section if no stable diagnostic behavior changed. Repeat its numbered subsection for each distinct behavior change. -->

Affected projects

1. <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.> <!-- If this diagnostic change exposes an existing ty shortcoming, search astral-sh/ty for issues covering that exact shortcoming. Include the following paragraph only when a matching issue exists. -->

Existing ty issues: ty#<issue-number>

<!-- 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>, attempt <attempt>
• Ruff comparison: <merge-base> to <pr-revision>
• ecosystem-analyzer: <revision>
• mypy-primer: <revision>
• Dependency cutoff: <EXCLUDE_NEWER>
• Project Python: <project: version, ...>
• Project analysis mode: <project: strict or non-strict, ...>
• Comparison method: <concise exact commands or method used to run both copied ty binaries, including --config analysis.strict-equality-semantics=true and --config analysis.strict-generic-narrowing=true for strict projects>