Marc-André Bombeck c8e8499472 fix(whoop): degrade a per-resource 403 gracefully instead of parking the connection ...

A 403 on a single WHOOP collection endpoint was classified reauth_required,
which parked the whole connection at error_reauth and short-circuited every
future sync. A lower-tier user missing one gated data class would brick the
entire integration.

Treat a per-resource collection 403 as a soft skip of that data class: log,
return 0, and continue so sibling resources still sync. Reserve connection-wide
reauth for a 401 (token rejected) and for a 403 on the token-refresh / profile
path, which run outside the per-resource catch blocks and remain unchanged.

Add isCollectionForbidden as the shared gate and cover both branches in tests.

2026-06-04 15:36:06 +02:00

..

client.test.ts

feat(whoop): WHOOP v2 API client, response classifier, credential resolution

2026-06-04 01:05:06 +02:00

credentials.test.ts

feat(whoop): WHOOP v2 API client, response classifier, credential resolution

2026-06-04 01:05:06 +02:00

oauth-state.test.ts

feat(whoop): WHOOP v2 API client, response classifier, credential resolution

2026-06-04 01:05:06 +02:00

response-classifier.test.ts

feat(whoop): WHOOP v2 API client, response classifier, credential resolution

2026-06-04 01:05:06 +02:00

sync.test.ts

fix(whoop): degrade a per-resource 403 gracefully instead of parking the connection

2026-06-04 15:36:06 +02:00

webhook-signature.test.ts

feat(whoop): OAuth connect/callback + HMAC-signed webhook + CSP gating

2026-06-04 01:40:27 +02:00