minimizing-ty-ecosystem-changes

# Minimizing Ty Ecosystem Changes ## Invariants 1. Use the exact Ruff revisions, user-level PR config, dependency cutoff, mypy-primer revision, project Python version, and strictness settings from the Actions run. 2. Reproduce the reported project difference before explaining it or writing a smaller example. 3. Treat copied binaries and config as read-only, and verify every reduction against both binaries. 4. Derive every candidate from the preceding verified candidate; NEVER substitute an independently constructed example. 5. Preserve the underlying trigger, not merely the diagnostic rule, message, or displayed type. Start each investigation from fresh artifacts. Do not trust retained memories, previous minimizations, current upstream project state, or the helper script's default lockfile. Prefix every direct or indirect `gh` invocation with `GH_TELEMETRY=false`; each Codex tool call may start a new shell. ## Collect Exact-Run Metadata If the primary agent supplied an immutable `TY_ECOSYSTEM_RUN_METADATA` manifest, verify that its run ID and attempt match the frozen report and that it contains each assigned project. All subagents reuse the same read-only manifest; never modify it or generate another shared manifest. Otherwise, run the bundled helper once with the Actions run ID or URL, matching attempt, and every affected mypy-primer project name: ```bash GH_TELEMETRY=false uv run --script scripts/collect_ty_ecosystem_run_metadata.py \ <actions-run> <project-name>....