Skip to content

v0.2.0 — reviewed adaptation and time-aware scheduling

Choose a tag to compare

@dithiothreitol dithiothreitol released this 21 Oct 20:21
· 130 commits to main since this release

Install: npx trainctl@0.2.0, MCP: npx -y trainctl-mcp@0.2.0. Full history in CHANGELOG.md.

Reviewed adaptation and time-aware scheduling

  • Execution data now distinguishes unknown from explicitly skipped sessions.
    Pull, review and adaptation share running-only classification and the latest
    journal correction. Shorter sync refreshes retain older history.
  • adapt --prepare saves an inspectable, content-addressed plan proposal;
    adapt --apply <id> applies exactly that proposal and rejects changed inputs
    or edited proposal files. Past, logged, pinned and manually edited days stay
    intact. Applicable patches cover volume and calibration; recovery remains an
    individual coaching decision.
  • reschedule --time YYYY-MM-DD=minutes --pin YYYY-MM-DD --preparation minutes
    honors time budgets including preparation, recoveries and strength. Preview
    exposes alternatives (--strategy long|quality) and dropped sessions.
  • Plans retain calibration inputs and generated-day checksums. why explains
    result selection and rule provenance; excluded/exclusionReason let runners
    retain unsuitable race results without using them for zones or predictions.
  • MCP tools return structured domain data with output schemas and annotations.
  • export --what mobile --date YYYY-MM-DD: standalone responsive workout HTML,
    including light/dark mode, session steps, purpose and expandable reasoning.
  • Fixed new-result detection comparing a result collection against itself,
    cycling counting toward a planned run, and the sync test's dependence on the
    current calendar date. pull --date makes historical sync ranges explicit.

See the workflow guide for examples and boundaries.

Added

  • trainctl log --rpe <1–10> (CLI and the trainctl_log MCP tool): session
    effort on the CR-10 scale, stored in the journal and shown by today. The
    engine only stores and quotes it — it never converts feelings into zones,
    paces or volume (ADR-027; collection is grounded in P-6, the refusal in Z-4).
  • The weekly review has a new section, How it felt: journal entries with an
    RPE or a note from the reviewed window, quoted verbatim (the last entry per
    day wins). No aggregation, no thresholds — the trail is material for a
    conversation with the coach-agent, not input to arithmetic.
  • AGENTS.md grew a debrief ritual (after a logged session, ask how it went
    and record it; when the feeling clashes with the session's role, ask one
    question about context), rule 8 — feelings are for conversation, not
    arithmetic — and an opt-in offer of a scheduled Monday debrief.
  • docs/examples/proactive-review.md: the coach speaks first — a weekly
    check-in from the agent's scheduler or cron, with the consent and
    propose-don't-apply rules spelled out.