fix: reset version to 0.1.0 baseline; let cz bump own versioning

The manual 0.1.0->0.2.0 bump conflicted with the automated release
workflow, which would have double-bumped to 0.3.0. Version is now driven
solely by `cz bump` from conventional commits (last tag v0.1.0 is the
baseline); CHANGELOG entries are generated at release time.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NGzHtDvJur9U7ysgRKRUTN

CHANGELOG.md

@@ -8,23 +8,10 @@ project is pre-1.0, new features bump the **minor** version and fixes bump the *
 version. Versions are cut with Commitizen (`uvx --from commitizen cz bump`), which updates
 this file and tags `vX.Y.Z`.
 
-## [0.2.0] — unreleased
-
-### Added
-- Nutrition & wellness intelligence tooling (in progress on this branch): training-readiness
-  signal (HRV/RHR/sleep/subjective synthesis), pre-activity fueling planner (carbs/fluid/
-  sodium), energy-availability / underfueling screen, and a wellness/nutrition write path
-  (`PUT /athlete/{id}/wellness/{date}`).
-- Computed **Form (TSB = CTL − ATL)** surfaced in wellness output.
-
-### Fixed
-- Wellness output mislabeled the record `id` as the date.
-
 ## [0.1.0] — 2026-07-20
 
 Baseline: multi-tenant fork of `intervals-mcp-server`. Per-user OAuth credentials with
 AES-256-GCM-encrypted Intervals.icu API keys (Better Auth), streamable-HTTP transport with
 CORS, and the full activity / event / wellness / power-curve / gear / custom-item toolset.
 
-[0.2.0]: https://git.farh.net/farhoodlabs/intervalsicu-mcp/compare/v0.1.0...HEAD
 [0.1.0]: https://git.farh.net/farhoodlabs/intervalsicu-mcp/releases/tag/v0.1.0

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "intervalsicu-mcp"
-version = "0.2.0"
+version = "0.1.0"
 description = "A Model Context Protocol server for Intervals.icu (FastMCP, native OAuth)"
 readme = { file = "README.md", content-type = "text/markdown" }
 requires-python = ">=3.12"