Appearance
Google Fit Data Validation
REFERENCE — complete inventory of Google Fit pipeline output, compiled 2026-06-11 for the restore/retire decision. Decision owner: Michael.
Data produced (lifetime)
| Artifact | Location | Content |
|---|---|---|
| Session list | ~/Sandpit/hinata/data/google-fit-sessions.json | 38 sessions, 2026-05-11 → 2026-05-22 (11 days), all activityType walking — no workouts, runs, cycles, or sleep |
| Timeline merge | Z2 /mnt/data/hinata/resources/timeline/timeline-2026-05.json | 4 Fit-derived entries; every entry has "distanceMetres": null, "startLat": null, "startLng": null |
| Fitness logs | ~/Sandpit/hinata/logs/fitness-logs/ | Empty |
No other consumer reads either artifact. Zoro's fitness tracking is sourced from the OneDrive workout tracker, not from Fit.
Pipeline state
| Component | State |
|---|---|
| API access | Expired 2026-05-22 (token dead; client since superseded by the hinata-brain project) |
fetch-fit-daily.py | 34 successful runs, 48 crashes after token death; references dead vault credential paths |
request-fit-access.py | References dead vault credential paths and the old client |
LaunchAgent com.hinata.fit-sync.plist (4×/day) | Removed 2026-06-11 (launchctl bootout + file deleted) |
fit_token.json / tokens_gcp.json in Vaultwarden | Retained — not covered by the 2026-06-11 deletion instruction |
Restore decision (pending Michael)
- Restoring requires a new OAuth grant under the hinata-brain client plus script repair (dead paths, old client).
- The Google Fit REST API is deprecated by Google in favour of Health Connect; phone-side data quality (no GPS, no distance) is unchanged by re-granting access.
- Until decided: no Fit polling runs anywhere; existing artifacts stay in place.
Cross-links: reference_itachi-credential-store · reference_mail-poller-z2