v0.29.1 — --version tells the truth again

Patch release. 0.29.0 is on PyPI reporting itself as 0.28.3; upgrade to this one.

Fixed

--version was wrong on every install since 0.28.0. __init__.py read package metadata under the pre-rename distribution name turbo-memory-mcp, which stopped resolving when 0.28.0 renamed the distribution to turbo-quant-memory. Every installed copy fell through to the hardcoded source fallback. 0.28.1–0.28.3 were right by accident, because the release ritual bumped that literal; 0.29.0 did not, so turbo-memory-mcp --version answered 0.28.3.

The same stale string reached server_info/health (version), the daemon handshake (server_version), the migration log (package_version) and the @v{version} git ref in the documented install command.

Also in the same family:

• server_info/health advertised package_name: turbo-memory-mcp, a distribution that has not existed since 0.28.0. Now turbo-quant-memory. runtime_command is unchanged — the console script really is still turbo-memory-mcp serve, so no client config needs touching.
• The packaged SKILL.md was stamped 0.28.3, so skill install wrote 0.29.0 copies claiming the previous version.
• tests/test_version_metadata.py now pins the source fallback, server.json (both version fields), contracts.PACKAGE_NAME and SKILL.md's pinned install example to pyproject.toml, so this class of drift fails in pytest rather than in a user's terminal.

Upgrading

Coming from 0.27.x or earlier, uv tool upgrade turbo-memory-mcp no longer resolves — the distribution was renamed. Once:

uv tool install --force turbo-quant-memory

then uv tool upgrade turbo-quant-memory afterwards. Reported in #4.