DeepBlueCoding

Adds a new MCP tool to the mcp-replay-dota2 Dota 2 replay-analysis server end to end (service method -> Pydantic response model -> register_<domain>_tools registration -> tool-selection instructions -> mkdocs page -> real-values test). Use whenever the user wants to add, expose, register, or wire up an MCP tool, a new @mcp.tool, a get_* tool, a tool that returns match/replay data, or "expose this analysis as a tool" for the dota MCP server, even if they don't spell out every step. Knows the non-obvious services-dict wiring, the NO-MCP-deps service boundary, and the mandatory per-change docs+test discipline.

Adds a new analysis service (collector) to the mcp-replay-dota2 services layer — a new domain like farming/jungle/rotation/lane that extracts data from a ParsedReplayData and returns service-layer Pydantic models. Use whenever the user wants to add a new service, a collector for replay data, a new analysis domain, a new src/services subdir, or asks to "extract X from the replay" / "analyze Y from the match" in this Dota 2 MCP server. Knows the service+model+constructor-injection pattern, the ParsedReplayData input contract, the strict NO-MCP-dependencies boundary, and the entry-point singleton wiring.

Cuts a release of the mcp-replay-dota2 Dota 2 MCP server. Use whenever the user wants to release a new version, cut/ship a release, bump the version, publish to PyPI/TestPyPI, tag a release, or push a Docker image for this project. Encodes the strict tag==pyproject-version check, the PEP440 prerelease routing (TestPyPI vs PyPI), the commitizen bump flow that keeps pyproject + CHANGELOG in sync, and the GitHub-release + Docker fan-out so a release is not pushed broken.

Runs the local CI gate (ruff + mypy + pytest) and writes/maintains real-values golden-master tests against the session-scoped replay fixtures for mcp-replay-dota2. Use whenever the user wants to run the tests, run CI locally, write or fix a test, add a fixture, test against real match data, run ruff/mypy/pytest, or check things "before pushing" in this Dota 2 MCP server. Encodes the exact commands, the uv-sync (not uv-pip) gotcha, the fixtures-only rule, the golden-master verified constants, the stable-ID-vs-display-name lesson, the pytest markers, and why CI runs only the smaller replay.

Writes and updates the mkdocs-material documentation for mcp-replay-dota2: places tool docs on the correct API category page, registers new pages in the mkdocs.yml nav, follows the AI-Summary admonition style, and keeps the TWO separate changelogs straight. Use whenever the user wants to update the docs, document a tool/feature/integration, add a nav entry, write an mkdocs page, edit docs/api, or add a changelog entry for this Dota 2 MCP server. Encodes the mandatory docs-per-change discipline and the docs/changelog.md vs CHANGELOG.md distinction.

Adds a new single-pass data collector to python-manta end-to-end (Go CGO layer, Python Pydantic models, parse() kwarg, fixture, scenario test, docs) so it becomes reachable as parser.parse(<name>={...}). Use whenever the user wants to add a new collector, track or capture a new kind of event/entity during parsing (wards-style, attacks-style), expose new dotabuff/manta data through parse(), add a parse() collector kwarg, or create a new *Result/*Config result type. Use this even if the user only describes the data they want surfaced (e.g. "track every tower attack", "capture courier deaths") without saying the word "collector".

Adds or modifies the Pydantic models and game-data enums in python-manta's manta_python.py (heroes, items, neutral items, rune/entity/combat-log/damage types) following the project's strict canonical-enum-plus-alias philosophy. Use whenever the user wants to add a new hero/item/enum, add an alias for an internal replay name, add or change a Pydantic model field, add a display_name, resolve npc_dota_hero_* / item_* names, or update enums for a new Dota patch. Use this even when the user just says "map this name", "add this hero", or "the enum is missing X".

Cuts a python-manta release (dev build to TestPyPI or final to PyPI) and/or bumps the locked upstream dotabuff/manta version, using the correct PEP 440 4-part version scheme and the exact git tag format the GitHub Actions CI keys on. Use whenever the user wants to release a new version, bump the version, publish to PyPI/TestPyPI, cut a dev/prerelease, tag a release, upgrade or sync the manta version, or change .manta-version. Use this even if the user just says "ship it", "make a dev build", or "update manta to vX.Y.Z".

Writes and debugs python-manta tests that parse real Dota replays without re-parsing, using the module-scoped cached-fixture system (conftest.py + caching_parser.py), the GCS replay auto-download, the correct pytest markers, and the right subset commands. Use whenever the user wants to write or fix a test for the parser, add a fixture, debug a test that can't find a replay, speed up slow/re-parsing tests, add a unit vs integration test, deal with the coverage gate, or configure DOTA_REPLAY_CACHE. Use this even when the user just says "test the wards collector" or "the tests are re-parsing".

Authors and updates the python-manta mkdocs documentation site (guides, API reference, reference pages) consistent with the mkdocs.yml nav, mike versioning, llms.txt generation, and the project's time-formatting and data-extraction-only content rules. Use whenever the user wants to write or update docs, add a guide, document a new feature/collector in the docs site, update the API reference, add a reference page, edit mkdocs, or work on the GitHub Pages / llms.txt site. Use this even when the user just says "document this" or "add it to the docs".