Skip to content

fix(insights): device-coverage advisory follows enabled+configured devices - #4

Merged
8tp merged 1 commit into
mainfrom
fix/device-coverage-advisory
Jun 23, 2026
Merged

fix(insights): device-coverage advisory follows enabled+configured devices#4
8tp merged 1 commit into
mainfrom
fix/device-coverage-advisory

Conversation

@8tp

@8tp 8tp commented Jun 23, 2026

Copy link
Copy Markdown
Owner

Bug: Dashboard showed "Running on 2/3 devices · Missing: whoop, oura" even though those devices are no longer used.

Cause: buildInsightsForDate hardcoded a 3-device expectation (['whoop','oura','apple']) from before the Fitbit pivot.

Fix: Compute the expected set from the wearables actually in use — kind==='wearable' && enabled && configured (configured = has credentials) — and only surface the advisory when you run 2+ devices and one of yours is missing today. Labels come from DEVICE_LABEL. Dormant WHOOP/Oura (no creds) are excluded.

Verified: typecheck + lint + 20 tests green.

🤖 Generated with Claude Code

The "Running on 2/3 devices · Missing: whoop, oura" card hardcoded a 3-device
expectation (whoop/oura/apple) from before the Fitbit pivot, so it always
flagged dormant WHOOP/Oura as missing.

Base the advisory on the wearables actually in use — enabled AND configured
(has credentials) — and only show it when you run 2+ devices and one of yours
is absent today. A device you don't use no longer reads as "missing".

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@8tp
8tp merged commit 30087df into main Jun 23, 2026
2 checks passed
@8tp
8tp deleted the fix/device-coverage-advisory branch June 23, 2026 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant