Read what is already scheduled on the athlete's calendar in a date range (so you don't double-book and can balance weekly load). Returns days — only days that hold a session or a note — each with its planned workouts (iid, title, sport, zone, duration + TSS; a gym session carries its content instead, a swim its metres; goal — the one line under its name saying why it exists; any note; fuel — the carbohydrate the athlete sees on the session's card, computed by the app; target — what a ride or run is held to on the device, power/pace/hr/rpe, targetDefault when that is their profile's and not the session's own; judge_by where the signal it is judged in differs, none = nothing readable: no number) and the day's own notes, plus monthlyTss (planned TSS per calendar month). Both dates are optional and inclusive; an omitted one is unbounded, so a call with neither returns the whole calendar, past and future. key:true marks a KEY session — the one the week is built around, declared in advance (see plan_workouts). Pass structure:true to also get each workout's full interval structure (compact, e.g. "6' @55% + 3×(12' @90% / 4' @55%)"); for raw blocks of ONE entry use get_plan_workout.