cfba3146e2
Reshape the sync-providers seam before Komoot (web-login) and Apple Health (device) adapters land. Captures the decisions in three ADRs, seeds CONTEXT.md with Connected Services vocabulary, and proposes the OpenSpec change covering schema rename + ConnectedServiceManager + capability seams (Importer / RoutePusher / WebhookReceiver). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
18 lines
1 KiB
Markdown
18 lines
1 KiB
Markdown
# RoutePusher seam takes (service, route); workarounds stay inside adapters
|
|
|
|
`RoutePusher` has one adapter today (Wahoo), but Coros, Garmin, and Strava
|
|
push are all foreseeable. The current Wahoo push code exposes its
|
|
workarounds — FIT Course conversion, the deterministic `external_id =
|
|
route:<id>` convention, the PUT→POST-on-404 fallback when a user has
|
|
deleted the route on the remote side — at the call site, which would force
|
|
every future pusher to either inherit those Wahoo-isms or reshape the
|
|
seam.
|
|
|
|
We commit to the seam shape now, with one adapter: `pushRoute(service,
|
|
route) → {remoteId, version}`. Format conversion, idempotency tricks, and
|
|
provider-specific HTTP recovery live entirely inside the adapter. The
|
|
`sync_pushes` table (`(user_id, route_id, provider) → remote_id,
|
|
last_pushed_version`) is the cross-provider contract for idempotency; the
|
|
adapter is responsible for honouring it but not for exposing how. When the
|
|
second pusher lands, it implements the same shape without changing
|
|
callers.
|