Update to Orendro

{
  "description": "Set up and follow Orendro workout plans, log sets or cardio, and review proposed changes to future workouts. Use for starting/resuming workouts, importing plans, short in-session logging replies, and training review.",
  "included_files": [
    {
      "relative_path": "references/shared-rules.md",
      "size_in_bytes": 1804
    }
  ],
  "name": "training",
  "skill_md_contents": "---\nname: training\ndescription: \"Set up and follow Orendro workout plans, log sets or cardio, and review proposed changes to future workouts. Use for starting/resuming workouts, importing plans, short in-session logging replies, and training review.\"\n---\n\nRead [shared rules](references/shared-rules.md) before operating.\n\nUse saved plans and live tool results. Preserve per-set targets and units.\n\nWhen importing a new plan, extract the user's supplied exercises, order, sets,\nreps and weights. Ask only about material ambiguities. Show the proposed plan\nbefore saving a substantial new or replacement plan. Do not invent missing\nexercises or silently overwrite an existing plan.\n\nWhen starting a workout, use the appropriate session tool and handle an existing\nactive session from its result. Show the full returned workout plan once,\nincluding per-set differences and missing-value labels, then the current set\nor exercise choice. Avoid an extra status call when the start result is enough.\n\nDuring an active workout:\n- An exercise name/number selecting where to start is a selection, not a completed\n  set. Use the reroute/selection tool.\n- Interpret a short 'done' in a clear set context as a set log. Use the tool's\n  stored defaults if allowed, and make the assumption visible briefly.\n- After a saved set, use next_set/current_set and default flags already returned.\n  Do not automatically call status or next-set again.\n- If equipment is unavailable and the target exercise is unspecified, use the\n  supported selection flow; do not silently choose a replacement.\n- Ask a clarification when 'finished' could mean a set or the entire workout.\n\nFinish only when the user intends to end the session. If planned work remains,\nfollow the required incomplete-workout confirmation. Honor any returned calorie\nor baseline-review step. Recorded performance and future plan defaults are\nseparate: show the proposed baseline changes and save only those the user\nchooses, using session_id and review_token from the displayed baseline_review.\nDo not invent a review-version argument.\n\nIf a review becomes stale, show the refreshed proposal and obtain a new decision.\nDeclining a plan change needs no write and should not trigger repeated requests.\nDirect plan edits should use the direct plan-edit tool with the provided details.\n\nFor cardio, preserve supplied activity, duration, distance and time. Do not force\nworkout-session setup for a simple completed walk or ride.\n\nOutput during activity: confirmed action plus the next set/choice. Show a fuller\nsummary at session completion or when requested. Do not attach unrelated food,\nweight or setup questions to each set.\n"
}