[intervals-mcp-server] Fix calendar tools and add planning projection to the coach report

[morritter]

Summary

• get_event_by_id: called /athlete/{id}/event/{eventId} (always 404); now uses /events/{eventId} like update/delete.
• get_events / get_event_by_id: show category, sport, planned load and planned time instead of Type: Other (N/A when Intervals.icu has no value); races are detected from RACE_A/B/C.
• Event and note updates send only the fields that are set: no null description, no forced category: WORKOUT, no move to today when no date is given. workout_type is optional (renaming works), new optional category (e.g. RACE_A).
• get_coach_report schema 1.1: projection mode for a future end_date:
  • period.mode, load.actual / load.projected, recovery.as_of
  • plan section: planned load, hours and sessions per ISO week and sport family, rest days, missing_load, projected CTL/ramp/tsb_min, races 12 weeks ahead
  • plan flags ramp_planned_high (> 6), tsb_planned_low (< −20 / < −30), planned_rest_days_low; every flag carries basis: actual|projection
  • load.src = api_incl_planned for values that include planned workouts; recomputed_without_planned only for days up to today

Compatibility

• Reports without a future end_date are unchanged apart from schema_version: "1.1" and period.mode: "actual" (snapshot test against the 1.0 output).
• add_or_update_event: name is now the first parameter and workout_type is optional. MCP clients pass named arguments; there are no positional callers in the repo.
• get_coach_report fetches the athlete first also with an explicit end_date (one extra round trip), because the athlete's "today" decides the mode.

Intervals.icu API assumptions (verified with read-only live calls)

• Events: category, type, icu_training_load (null for workouts without targets), moving_time (s), start_date_local.
• GET /athlete/{id}/events/{eventId} returns the event.
• category=RACE_A,RACE_B,RACE_C filters /events server-side.
• Wellness records for future days contain ctl, atl, rampRate including planned workouts; rampRate = CTL(d) − CTL(d−7).

Testing

• pytest: 202 passed.
• ruff, mypy: no new findings (the two F401 in server.py and power_curves.py already exist on main).
• pylint as in CI: no new findings; the existing ones in power_curves.py, gear.py, server.py and formatting.py are unchanged.
• Manual, read-only against a live account:
  • get_events and get_event_by_id show sport, category, planned load and time.
  • get_coach_report(days=14, end_date="2026-10-04"): mode: projection, plan W40 load 817 with missing_load: 2, projected CTL 105.1 / ramp 2.4 (api_incl_planned), load.actual CTL does not rise with planned-but-not-done load, tsb_planned_low warning at −23.0.
  • get_coach_report(): mode: actual, keys unchanged.
• Not done: a live write test of event updates (covered by unit tests only).

Known limitations

• Once today has an activity, plan starts tomorrow; a second session planned for today is then missing from plan (it is still in the CTL projection).
• Workouts without a computed load are also missing from the Intervals.icu projection, so ramp/TSB are optimistic; reported as missing_load.
• ramp is checked at the end of each week only; planned_rest_days_low only for fully planned weeks.

🤖 Generated with Claude Code