fix(workouts): recognize trail running and repair code 7 history - #71
Merged
Conversation
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
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.
Fixes #24.
Zepp cloud-history code
7was mapped using the Zepp OS device-protocol meaning,open_water_swimming. It now normalizes totrail_running, so the activity label and JSON, GPX and FIT exports reflect trail running automatically.The evidence is visualcurrent's September 9 comment: the ZeppBridge screenshot shows raw code 7 and no correction; the matching Zepp screenshot identifies an Amazfit Balance trail run. The supplied JSON confirms
numeric_mapped, and the official Zepp GPX identifies the same activity as Trail running. Both screenshots and the export snippets were checked. Tests reconstruct minimal cloud-shaped inputs from that evidence; the comment did not include a complete raw cloud response. No personal identifiers or GPS coordinates from the report are committed.numeric_mappedcode-7 swimming rows, including libraries whose raw payloads have expired. Only the stored interpretation changes; user overrides, metrics, routes and sync timestamps remain intact. Existing migration locking, transaction and pre-upgrade backup apply.Validation: workspace Rust tests (389 passed, 1 pre-existing ignored), Clippy with warnings denied, rustfmt, frontend build/tests (110 passed), Functions tests (33 passed), version/docs/i18n checks and bundle budget. Also ran the compiled Windows CLI against an isolated on-disk v21 library with no raw payloads: verified migration, exact preservation of all other workout columns, routes, the original v21 backup, JSON/GPX/FIT exports and idempotent replay.
Reporter-device retesting remains for the eventual release. Existing export files must be exported again. This PR is ready for the maintainer to review and merge; no release is published here.