v0.5.9

Documentation and release-pipeline changes. No behaviour change in the server itself.

README — the console script grew --help and --version in 0.5.8 and the README never said so. The install section now states that the MCP client spawns the server (which is the real answer to "how do I run this"), names the two flags that work outside a client, and adds a troubleshooting row pointing at --version for the case that sends people to a terminal: the client listing the server as failed, with no way to tell a PATH problem from a bad configuration.

Release workflow — the build job now checks the files it is about to hand over, not just the version that asked for them. The tag check reads pyproject.toml before uv build, and if-no-files-found: error only proves dist/ was non-empty; neither constrains what reaches PyPI. uv build does not empty dist/ first either, so a stale or mis-versioned distribution could ride along to an upload that cannot be withdrawn. The new step names the two files it expects and refuses anything else.

Two comments in that workflow also claimed more than the configuration does, and now say which is which: the pypi environment scopes identity but gates nothing, and id-token: write is job-scoped, which puts setup-uv and download-artifact inside the credential boundary alongside uv publish.

Full changelog: v0.5.8...v0.5.9