What We Shipped

FORM Goggles Integration, End to End

Commit 331c7601 was the big one: full FORM Goggles integration across plan import, swim FIT export, and push-to-goggles delivery. That is real product surface area, not checkbox integration theater. It adds the plumbing needed to move structured swim work from the calendar into a device athletes actually use in the water, which is where this feature either becomes valuable or becomes dead weight.

Cleaner Entry Points for Sync and Export

Commits 9312e6d1 and 6609098b finished the UI wiring by adding FORM Goggles to the sync dropdown and the workout editor export menu. Good sequencing. Shipping backend support without obvious entry points is how features technically exist while users never find them.

Swim Mapping and Payload Reliability Fixes

Commits 7c9317e1 and c6e7574a tightened the last-mile behavior. Swim workouts now stay swim instead of quietly defaulting to run, and the FORM create payload no longer includes an unsupported sport field that triggered unexpected_key errors. Exactly the right kind of follow-through: integration work is not done when the button appears, it is done when the payload survives contact with the receiving API.

The Takeaway

Today was a serious integration day. FORM Goggles went from concept to usable workflow, and the follow-up fixes handled the two failure modes that would have made the launch feel half-baked: wrong sport mapping and rejected create requests. Messy in the middle, solid by the end.