STAS Running Coach for Claude

Previous value: -"End boundary date in YYYY-MM-DD, exclusive. To load one date, set newest to the next calendar date, for example oldest=2026-06-21 and newest=2026-06-22."New value: +"End boundary date in YYYY-MM-DD, exclusive. Never use the last wanted date here; use the next calendar date. For one day D, set oldest=D and newest=D+1, for example oldest=2026-06-21 and newest=2026-06-22."

Added value: +{
+  "description": "Pagination offset for completed trainings. Use the next offset to continue the same bounded date window; calendar context is returned only on the first page.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

Previous value: -"Compact STAS preparation map: a saved result of long-horizon planning, not a calendar, weekly plan, workout prescription, or full coaching analysis. Target length is about 1800-4000 characters; hard maximum is 5000 characters. Required sections: Goal direction, Current phase, Preparation map, Durable boundaries, Review triggers / unknowns. Build from current goals, rules, profile, lastMetrics, wellness, reports, training history, evidence, and calendar first; do not copy or paraphrase previous_strategy unless current facts independently support the same durable decision. For strategy-level work, use at least 8 weeks of weekly/load history when available and 12-26 weeks for season direction; combine it with exact bounded-list windows and selected detailed workout passports instead of using only 2-4 weeks. Treat every dated goal as a real planning input by default; do not infer a single main goal from distance, later date, target result, profile order, or old strategy wording. Use priority only when it is explicit in the current profile, goal comment, athlete message, or current coaching decision. B/C/training-race/no-full-taper wording changes peak depth and risk; it does not mean the race should be ignored unless the athlete explicitly says the result does not matter. Store the agreed goal relationships, current phase purpose, a 3-6 phase seasonal route, what each phase develops/preserves/defers, broad transition conditions, durable boundaries, and causal review triggers. A phase may name the capacity it develops, but it must not prescribe exact weekly stimuli, workout formats, dose, load, support work, cuts, or taper. Do not store session frequency, easy/hard balance, weekly load targets, number of key workouts, default weekly stimulus, exact progression, workout protocols, fixed taper depth, ready 2-4 week sequences, or current Fitness/Fatigue/Form/TL. Old detailed strategies remain historical context. Do not proactively ask the athlete to convert one merely because it is legacy; create or update the map only when the athlete asks for strategy/season work or explicitly agrees to a long-term route change. Before save_strategy, show the user the exact full markdown and save only after explicit confirmation. Never show one version and save another."New value: +"Compact STAS preparation map: a saved result of long-horizon planning, not a calendar, weekly plan, workout prescription, or full coaching analysis. Target length is about 1800-4000 characters; hard maximum is 5000 characters. Required sections: Goal direction, Current phase, Preparation map, Durable boundaries, Review triggers / unknowns. Build from current goals, rules, profile, lastMetrics, wellness, reports, training history, evidence, and calendar first; do not copy or paraphrase previous_strategy unless current facts independently support the same durable decision. For strategy-level work, use at least 8 weeks of weekly/load history when available and 12-26 weeks for season direction; combine it with exact bounded-list windows and selected detailed workout passports instead of using only 2-4 weeks. Treat every dated goal as a real planning input by default; do not infer a single main goal from distance, later date, target result, profile order, or old strategy wording. Use priority only when it is explicit in the current profile, goal comment, athlete message, or current coaching decision. B/C/training-race/no-full-taper wording changes peak depth and risk; it does not mean the race should be ignored unless the athlete explicitly says the result does not matter. Store the agreed goal relationships, current phase purpose, a 3-6 phase seasonal route, what each phase develops/preserves/defers, broad transition conditions, durable boundaries, and causal review triggers. A phase may name the capacity it develops, but it must not prescribe exact weekly stimuli, workout formats, dose, load, support work, cuts, or taper. Do not store session frequency, easy/hard balance, weekly load targets, number of key workouts, default weekly stimulus, exact progression, workout protocols, fixed taper depth, ready 2-4 week sequences, or current Fitness/Fatigue/Form/TL. Every Durable boundaries line must preserve a route-specific decision that would be lost after reloading goals, athlete rules, and canonical planning rules; delete universal coaching, measurement, device, or load-cost rules from the map. Local pain, sleep, recovery, illness, or execution signals change the near-term plan first. Store them as map review triggers only when persistence or consequence would change phase feasibility, timing, sequence, or the goal route. Treat phase dates as approximate anchors and Transition when as review evidence, not hard gates. If a condition is unmet, consider adaptation, delayed or compressed transition, and remaining runway to the next goal instead of freezing the route. Old detailed strategies remain historical context. Do not proactively ask the athlete to convert one merely because it is legacy; create or update the map only when the athlete asks for strategy/season work or explicitly agrees to a long-term route change. Before save_strategy, show the user the exact full markdown and save only after explicit confirmation. Never show one version and save another."

Previous value: -"Compact direction-only STAS strategy markdown, not a calendar, weekly plan, block contract, or full coaching analysis. Target length is about 2500-4000 characters; hard maximum is 5000 characters. Required sections: Goal chain, Current point, Weekly decision contract, Roadmap, Resources / risks, Review triggers / unknowns. Build from current goals, rules, profile, lastMetrics, wellness, reports, training history, evidence, and calendar first; do not copy or paraphrase previous_strategy unless current facts independently support the same durable decision. For strategy-level work, use at least 8 weeks of weekly/load history when available and 12-26 weeks for season direction; combine it with exact bounded-list windows and selected detailed workout passports instead of using only 2-4 weeks. Treat every dated goal as a real planning input by default; do not infer a single main goal from distance, later date, target result, profile order, or old strategy wording. Use priority only when it is explicit in the current profile, goal comment, athlete message, or current coaching decision. B/C/training-race/no-full-taper wording changes peak depth and risk; it does not mean the race should be ignored unless the athlete explicitly says the result does not matter. Store only explicit priority/tradeoffs not recoverable from goals, broad phase direction, deliberate deferrals, durable direction-changing risks/constraints, and causal review triggers. Weekly decision contract must state durable boundaries and delegate current capacity, stimuli, format, dose, load, support work, cuts, and taper to the private Planning Gate using fresh data. Do not store session frequency, easy/hard balance, weekly load targets, number of key workouts, default weekly stimulus, support-work dose, exact progression, workout formats/protocols, taper depth, ready 2-4 week sequences, or current Fitness/Fatigue/Form/TL. Roadmap phases are broad direction, priority/tradeoff, deliberate deferral, and review points—not Driver/Support/Switch-gate block contracts. Before save_strategy, show the user the exact full markdown and save only after explicit confirmation. Never show one version and save another."New value: +"Compact STAS preparation map: a saved result of long-horizon planning, not a calendar, weekly plan, workout prescription, or full coaching analysis. Target length is about 1800-4000 characters; hard maximum is 5000 characters. Required sections: Goal direction, Current phase, Preparation map, Durable boundaries, Review triggers / unknowns. Build from current goals, rules, profile, lastMetrics, wellness, reports, training history, evidence, and calendar first; do not copy or paraphrase previous_strategy unless current facts independently support the same durable decision. For strategy-level work, use at least 8 weeks of weekly/load history when available and 12-26 weeks for season direction; combine it with exact bounded-list windows and selected detailed workout passports instead of using only 2-4 weeks. Treat every dated goal as a real planning input by default; do not infer a single main goal from distance, later date, target result, profile order, or old strategy wording. Use priority only when it is explicit in the current profile, goal comment, athlete message, or current coaching decision. B/C/training-race/no-full-taper wording changes peak depth and risk; it does not mean the race should be ignored unless the athlete explicitly says the result does not matter. Store the agreed goal relationships, current phase purpose, a 3-6 phase seasonal route, what each phase develops/preserves/defers, broad transition conditions, durable boundaries, and causal review triggers. A phase may name the capacity it develops, but it must not prescribe exact weekly stimuli, workout formats, dose, load, support work, cuts, or taper. Do not store session frequency, easy/hard balance, weekly load targets, number of key workouts, default weekly stimulus, exact progression, workout protocols, fixed taper depth, ready 2-4 week sequences, or current Fitness/Fatigue/Form/TL. Old detailed strategies remain historical context. Do not proactively ask the athlete to convert one merely because it is legacy; create or update the map only when the athlete asks for strategy/season work or explicitly agrees to a long-term route change. Before save_strategy, show the user the exact full markdown and save only after explicit confirmation. Never show one version and save another."