Coach command centre

Build my Coach Command Centre from Athuno: one HTML page, generated each morning, that reads every athlete I coach and tells me who to look at first. Run it now for today, then keep it as a command I can run any morning. Read everything through the Athuno connector. Start with get_me: the athletes I coach are the ones with role `coach`, each with a timezone and today's date there. Every window below is in the athlete's own dates. Today is the day I run it. 1. Data to pull, per athlete - get_calendar from 7 days before today to 3 days after: planned workouts with their status, activities with the plan they fulfilled. - get_fitness for the last 56 days: CTL, ATL, TSB and TSS per day. - get_training_summary for the last 2 weeks, for the previous week's totals. - get_activity for each activity in the 7-day window that has feedback or comments: `feedbackAnswers` (RPE is the `exertion` answer, feeling the `feeling` answer, the note `notes`, or the athlete's own questions by label), and whose word is last in the thread. - list_flags: the open attention flags. - get_thresholds: the thresholds in effect today. 2. Windows and definitions - The 7-day window is the last 7 days including today. The previous week is the 7 days before it. - Time 7d is the sum of moving time (elapsed time when moving time is missing). Distance 7d and elevation 7d are sums. TSS 7d is the sum of TSS. - CTL, ATL and TSB are the app's own numbers from get_fitness. Read them at the end of yesterday, never part way through today: ATL moves six times faster than CTL, so a morning read shows the whole roster freshening. Show CTL's change over 7 days (yesterday against 8 days ago) as the ramp. - Compliance is the planned workouts in the window dated before today, plus today's done ones, that are completed or partial, out of all of those. A session done without a plan does not count against it. - Feel 7d is the mean RPE and the lowest feeling in the window, from the sessions where the athlete logged them. - Blank cells mean the app has no value. A heart rate of 0 or null means no heart rate: leave it out, never average it. 3. Flags, in this order of severity - Red: any open app flag of severity 70 or more not marked seen; a feeling of 1 on any session in the last 3 days; a day note in the window about illness, injury or pain. - Amber: an open app flag of severity 40 to 69 not marked seen; a planned session in the last 3 days marked missed or skipped; a thread whose last word is the athlete's; no session in the 7-day window. - The app flag's own label is the reason text. For the rest: "missed Tue 5 × 4 min", "feeling 1 after Sunday's long run", "waiting for a reply since Mon", "no session in the last 7 days". - TSB is shown, never flagged: a deep TSB is normal in a build week and a high one in a taper. Watch the CTL ramp instead. - An athlete's dot is red if any red flag, amber if any amber flag, green otherwise. 4. The page, top to bottom - Title: "Coach Command Centre · Friday 11 September 2026", with a sub-line stating the windows exactly: "Training from Sat 05 Sep to Fri 11 Sep. Plan to Mon 14 Sep. Load read at the end of Thu 10 Sep. Generated 07:40." - Five KPI cards: Athletes; Need attention (athletes with any flag); Sessions, 7 days; Hours, 7 days (one decimal); Planned, next 3 days. - "Look at these first": every flagged athlete, red before amber, then alphabetical, each with the dot, the name and one chip per flag (the flag name in bold, then the reason). - "Every athlete": one table, same order, the unflagged after them. Columns: Athlete · Time 7d with the change against the previous week as a percentage · Distance 7d · TSS 7d · Sessions with "4/5 planned" under it · CTL with the ramp · ATL · TSB · Feel 7d · Next 3d as the number of planned sessions and their total time. Numbers right-aligned and tabular. - "Athlete by athlete": one card per athlete in the same order. Header: dot, name, flag chips, or a plain chip "Nothing flagged". Eight stat tiles: Time 7d (sessions) · Distance 7d (elevation) · TSS 7d (change vs previous week) · CTL (ramp) · TSB · Compliance · Mean RPE · Lowest feeling. Then two columns. Left, "Last 7 days": one row per day, today marked, each session as its sport and title, then time, distance, pace per km for runs or average power for rides, average heart rate, TSS, RPE and feeling, leaving out anything the app has no value for; "rest" on days with none. A planned session with no activity is marked missed in red on its day. Right, "Today and the next 3 days": each day either "Nothing planned" or its planned sessions with title, sport, planned time and distance, and a collapsible "Workout detail" with the description as written. - Footer: the definitions above in plain words. 5. Design and delivery - Self-contained HTML, no external files, system font, 1180px wide, cards with hairline borders and 10px radius, KPI values at 24px, uppercase 11px labels, red, amber and green chips with tinted backgrounds. Follow the system light or dark theme with prefers-color-scheme, and print cleanly with cards kept whole. On a phone the table scrolls sideways and the cards stack. - In a terminal agent, save it as latest.html in a folder named command-centre, keep a dated copy beside it, and open it. In a chat app, show it as an artifact. - The page carries athlete names and how they feel, so treat it as private. You aggregate and flag. The coaching decisions are mine. Read only.