Debug export: add a Workouts-by-source breakdown#32
Merged
Conversation
The 'counted but not shown' workout bugs (#28 strap workouts under my-whoop vs the active strap id; #29 activity-file imports the load path skipped) were invisible in a strap log — you couldn't tell WHERE workouts lived vs what the Workouts screen loaded. Add a 'Workouts by source' block to the debug export (both platforms), reusing the existing dynamicLines plumbing: - The RESOLVED active deviceId (whoop-<uuid> vs my-whoop) — the key context for any 'data under the wrong id' report. - A per-source STORED workout count (active strap, my-whoop, their -noop computed twins, activity-file, lifting, apple-health, health-connect). - The most-recent workout (date · sport · source). Best-effort + guarded so it never throws into the export. Makes the whole 'workouts present in Data Sources but missing from the screen' class self-diagnosing.
Extends the source reconciliation to daily data (the same active-strap↔my-whoop id mismatch strands days/steps/sleep/recovery, not just workouts): - Per-source DAY counts (active strap, my-whoop, their -noop twins, apple, health-connect). - Recent-7d metric presence on the imported spine (sleep/recovery/steps/kcal = N/7). - On-device volume one-liner (raw stream rows, imported days, workouts) from the existing dataVolumeSnapshot. Makes the 'no data / no steps / 0% REM' report class self-diagnosing too. Both platforms.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The "counted but not shown" workout bugs (#28 strap workouts under
my-whoopvs the active strap id; #29activity-fileimports the load path skipped) were invisible in a strap log — you couldn't tell WHERE workouts lived vs what the Workouts screen loaded.Adds a "Workouts by source" block to the debug export (both platforms), reusing the existing
dynamicLinesplumbing:whoop-<uuid>vsmy-whoop) — the key context for any "data under the wrong id" report.my-whoop, their-noopcomputed twins,activity-file,lifting,apple-health,health-connect).So a future "workouts present in Data Sources but missing from the screen" report is self-diagnosing (e.g.
activity-file=3with the screen empty → the load skips that source).Best-effort + guarded so it never throws into the export.
Verify