Release v0.10.0 — Garmin/Strava connection & recovery analyst#35
Merged
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version bump to 0.10.0 (+ regenerated uv.lock) and the changelog for what is already on main:
performance-agent connect garmin|strava(interactive Garmin login with MFA, Claude Code registration or paste-ready JSON snippet; Strava authorizes in the browser from the conversation).connected_serviceson the athlete profile; check-ins pull activities and wellness from a connected Garmin/Strava MCP server through the existing propose → confirm → log flow, and the skills walk the athlete through setup when the server is missing.analyze_wellness_trend(103 tools): rolling ln(rMSSD) vs 28-day baseline ± SWC, resting-HR bands, sleep debt — honesty-gated,delta_pctfeedscompute_readiness.recovery-analyst(16 skills): device-data trend reads against training load, descriptive never diagnostic.1425 tests. After merge: tag
v0.10.0to trigger the release workflow.🤖 Generated with Claude Code