feat: Open Wearables integration proof-of-concept

[travis-sauer-oltech]

Summary

Adds a complete proof-of-concept integration between JupyterHealth Exchange (JHE) and Open Wearables (OW), enabling patients to connect wearable devices (Oura, Garmin, etc.) through JHE's existing invite-link flow.

What Changed

Backend - Proxy API (core/views/ow.py)

Endpoint	Method	Purpose
/api/v1/ow/users	POST	Creates/finds OW user for authenticated JHE user; stores ow:<user_id> in JHE identifier field
/api/v1/ow/providers	GET	Proxies OW provider list (enabled, cloud-API providers with icons)
/api/v1/ow/oauth/<provider>/authorize	GET	Generates OAuth authorization URL for any OW provider
/api/v1/oauth/<provider>/callback	GET	Proxies OAuth callback from provider back to OW for token exchange

Config is read from JheSetting DB records (ow_api_base_url, ow_api_key).

Frontend - Client Flow (core/static/js/)

• common.js - New shared utilities: parseInvitationCode(), exchangeCodeForToken(), base64UrlEncode()
• ow-client.js - Full client-side orchestration:
  1. Parse invite link and exchange auth code for JHE token
  2. Fetch user profile + study consents from JHE
  3. Create OW user via proxy (seamless, no separate login)
  4. Fetch and display available wearable providers
  5. Cross-reference JHE study data sources with OW providers
  6. Render provider picker grid with provider icons
  7. Handle OAuth redirect to provider and completion

Templates

• base_ow_client.html - Base template with Bootstrap 4, Bootstrap Icons, common scripts
• launch.html - Landing page with status spinner, provider picker grid, integration log panel
• complete.html - Success page after OAuth completion

URL Routes

• /ow/ - Launch page (invite link entry point)
• /ow/complete - Post-OAuth completion page

Integration Log Panel

Terminal-style debug panel rendered during the flow showing:

• Token exchange status
• Study enrollment and consent details
• Data source/device cross-reference with OW providers
• Provider availability

End-to-End Flow

1. Patient visits /ow/?code=<invitation_code>
2. JS parses invite code, exchanges for JHE access token
3. Fetches profile + study consents, creates OW user
4. Displays provider picker grid
5. Patient selects provider -> redirected to provider OAuth
6. Provider redirects back -> JHE proxies callback to OW
7. Success page confirms device is connected
8. OW handles ongoing data sync in background

Test Coverage

• tests/test_ow_integration.py - 257 lines covering:
  • User creation (auth, conflicts, error handling)
  • Provider authorization (missing account, custom redirect_uri)
  • Config validation (missing/partial settings)
  • All endpoints return proper error codes for edge cases

Files Changed

File	Change
core/views/ow.py	New - proxy endpoints
core/static/js/ow-client.js	New - client orchestration
core/static/js/common.js	New - shared utilities
core/templates/ow_client/launch.html	New - launch page
core/templates/ow_client/complete.html	New - completion page
core/templates/partials/base_ow_client.html	New - base template
core/templates/partials/base.html	Modified - minor updates
core/urls.py	Modified - added OW routes
core/views/common.py	Modified - added view functions
tests/test_ow_integration.py	New - integration tests