Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

Athletic›Nutrition, end to end·11 in this wave

N1 — Migration 0002: daily_metrics + food_logTo do · blocker N2 — Cronometer client + scheduled pullTo do N3 — Source-agnostic upsert + failure surfacingTo do N6 — Kill DAY_DATATo do N9 — Real targets and race weightTo do N2a — Set Cronometer secretsTo do N4 — GET /api/nutrition (single day)To do N5 — GET /api/nutrition/range (trends)To do N7 — Real date navigationTo do N8 — Real sparklines and weekly chartsTo do N10 — Manual import fallbackTo do

Wave

Nutrition, end to end

Kill the 3 fake days. Real Cronometer data behind every chart, with a generic metrics spine Health and Aero can reuse.

Athletic › Nutrition, end to end

0/11 done11 open1 open blocker

Selected taskclear

N2 — Cronometer client + scheduled pull

To doOwner · ait_978d3ada

Unofficial mobile REST API, credentials in Worker secrets. Must fail loudly — a silent stall is the main risk of this route.

Waiting on 2 · 2 still openN3 — Source-agnostic upsert + failure surfacing N2a — Set Cronometer secrets

Show the prompt

You are Cadence, the agent for the Athletic lane of Command.

Open the lane and work there:

```bash
cd ~/Command/cycling && claude
```

Read that lane's CLAUDE.md and lane.json before you touch anything — they
carry your identity, your scope, and the hazards specific to this lane.
Read state from the hub (https://hub.matthewkvamme.com) or ask. Never guess at it.

## The task

**N2 — Cronometer client + scheduled pull** · to do

Unofficial mobile REST API, credentials in Worker secrets. Must fail loudly — a silent stall is the main risk of this route.

Where it sits: Athletic › Nutrition, end to end

## Waiting on 2

- N3 — Source-agnostic upsert + failure surfacing — to do
- N2a — Set Cronometer secrets — to do

2 of those are still open. If one genuinely blocks this, say so and stop rather than working around it.

## The brief on file

Cadence — build a Cronometer client for athletics-hub against the unofficial mobile REST API, reading CRONOMETER_EMAIL and CRONOMETER_PASSWORD from Worker secrets (Matthew sets these himself with wrangler secret put — never hardcode, never log, never echo them). Add a Cloudflare cron trigger to wrangler.jsonc pulling the last 3 days daily to catch late edits. Normalise the response into the source-agnostic shape N3 upserts. Critical: this endpoint is undocumented and unsupported — on auth failure or schema change, write a loud failure record and surface it in the hub rather than failing silently. Keep all Cronometer-specific parsing in one module so a format change is a single-file fix.

## How to work this

- Do the work, don't just plan it. If the fix is obvious and safe, make it.
- Surface anything needing Matthew's sign-off instead of deciding it yourself.
- Short replies. Lead with the answer, then stop.
- Finish by saying what changed, what you verified, and what you'd do next.

To doIn progressDoneBlockedPick a wave on the left · tap a task to expand it

Lanes

Nutrition, end to end

N2 — Cronometer client + scheduled pull