v0.3.0 — UCI through esca

The bridge now speaks UCI through the in-house esca library, which also answers every chess question along the way. Nothing changes for MCP clients: the same six tools, the same arguments, scores still from White's point of view, moves still spelled the way engines write them.

• Python 3.12 or newer is required.
• -o NAME VALUE on the command line now actually reaches the engine; before, startup options were silently dropped.
• Dependencies refreshed: mcp 1.28.1 or newer, and the lockfile is clear of every advisory GitHub had open against it.

v0.2.0 — discoverable in the MCP registry

The bridge itself behaves exactly as in 0.1.2: the same six tools, the same engine handling. What changed is everything around it.

Listed in the official MCP registry as io.github.AnglerfishChess/chess-uci-mcp, so registry-aware clients can discover and install it instead of being handed a PyPI name by hand.

Releases are published by CI through a PyPI trusted publisher over OIDC. No API token exists on any laptop or as a repository secret, and publishing a GitHub release is the only thing that triggers a release.

Tests now run on Linux against a real Stockfish on every push, which they previously did not do anywhere but a maintainer's machine.

The README documents all six tools. get_engine_options and set_engine_options shipped in 0.1.2 but went unlisted.