Tags

v0.6.0

v0.5.2

v0.5.1

v0.5.1 — patch release: the v0.5.0 gate goes green in CI (no product change)

v0.5.0's tag stays on its commit. This patch corrects the two defects its
pipeline exposed, both in the hermetic test tier that shipped with the release:

- .gitlab-ci.yml fetches full history (GIT_DEPTH: 0): check.sh tier 7 rebuilds
  the pre-cloud seed from commit 5cc753c (~100 commits back), which the runner's
  default depth of 20 never reached → "fatal: Not a valid object name 5cc753c".
- tests/e2e_update.sh no longer depends on ambient git config: the pre-cloud
  fixture writes its own scratch core.excludesFile, pinning the historical
  condition (a global ignore rule hides AGENTS.md) that the migrator's
  `git add -f` repairs, and the tier neutralizes GIT_CONFIG_GLOBAL/SYSTEM.
- the tier now fails with the actionable message ("full history is required")
  when the seed commit is absent, instead of git's bare error.

No tool, engine, skill or state-schema change: v0.5.1 differs from v0.5.0 in the
CI config, the tier-7 test and the pinned refs (README/INSTALL/package.json) only.
Install refs pin v0.5.1.

v0.5.0

v0.5.0 — goal-race gate context, weekly volume target, elevation model, schema v5

- coach_gate reads goals.md (target / race_distance_km / race_elevation_gain_m)
  and plan/macrocycle.md (race_date) into the AthleteContext and derives the
  goal pace once; validators gains a RACE-only branch warning
  RACE_FAST_VS_GOAL / RACE_SLOW_VS_GOAL (PACE_RACE_OFF yields to it), and
  plan/macrocycle.md's legacy goal is read alongside.
- volume: new pure src/volume.py + JSON CLI (week_km_target vs planned+done km,
  RAMP_MAX x km4wk ceiling, statuses ahead/on-track/behind/unreachable-by-policy);
  plan_file.spec_km's anchored parser is promoted and shared with the logbook;
  coach_week_review appends the engine volume line after the diff (byte-identical
  without a target).
- elevation: VERT_JUMP per-run gate (vert_max_4wk + 150 m ceiling, REST excluded),
  fatigue.md vert_max_4wk (largest single-activity gain in the window), public
  elevation_gain_m_from_activity, elev_m appended as the log month-row's last
  column (pre-v5 rows still parse, blank), optional elevation_gain_m through the
  workout library offer/push path. Vert ships as a description annotation only:
  the C0 live probe (2026-09-11) shows Garmin accepts TargetType.GRADE but its
  value encoding did not round-trip, so workout_spec stays frozen.
- schema v5: goals.md target + race_distance_km/race_elevation_gain_m,
  plan/current.md week_km_target, fatigue.md vert_max_4wk ship as seed-only keys;
  the migration is a deliberate no-op (no narrative file or plan header rewritten,
  a missing key reads as absent and every gate skips).
- tests: tests/e2e_update.sh is re-pinned to the shipped schema and joins check.sh
  as hermetic tier 7; a pre-0.5.0 verdict fixture pins the byte-identical contract.

Additive tools + state schema; registration-affecting release.

v0.4.1

v0.4.1 — engine header-grammar corruption fixes (BUG-1/3), plan-row import matching (BUG-4), upload-log digest on push/delete (BUG-5)

v0.4.0

v0.4.0 — Garmin readback round (2026-09-08)

- garmin_activity: per-activity summary + lap splits (--last/--date/--id)
- HRV fix: nested hrvSummary payload parsed (was always no-data)
- refresh_fatigue persists recovery signals (HRV/RHR+7d/body battery/readiness)
  into fatigue.md keys + engine-owned computed section (schema v4)
- History: one row per refresh day (same-day refresh replaces; dupes collapse)
- coach_log_run + coach_week_review: plan-vs-execution (explicit import)
- Migration v4 chains 0/1/2/3 -> 4 on scripts/update.sh
Additive tools + state schema; registration-affecting release.

v0.3.1

v0.3.0

v0.2.0