Skip to content

Clarify private key delivery and Muse entry syntax - #26

Merged
0xBreadguy merged 5 commits into
mainfrom
t3/garmin-key-entry-clarification
Nov 8, 2026
Merged

0xBreadguy merged 5 commits into
mainfrom
t3/garmin-key-entry-clarification

Conversation

@0xBreadguy

Copy link
Copy Markdown
Owner

What changes

Headless setup guidance previously described private file delivery as the only route, causing assistants to overlook secure process-environment injection. Document both supported paths and their persistence, validation and scheduling limits.

Add exact Muse complete-header entry copy: ApiKey (capital A and K), one space, then the key unchanged. Show a fake mixed-case example before the private card and distinguish this format from the raw key required by normal installer, environment and file inputs. Keep repository and installed agent guidance aligned.

Record the bounded Muse dummy probes and the limits of their evidence. This PR changes guidance only: the Muse authentication adapter is not implemented, real-key authentication and sync remain unverified for that route, and card connection status must not be presented as proof of authentication. Grok's process-environment path remains a raw-key path.

Verification

  • uv run --locked python -m unittest discover -s tests -p 'test_onboarding.py' -v — 4 tests passed for the final file content.
  • uv run --locked garmin-archive agent-guide --client muse — inspected emitted syntax, raw-key distinction and adapter limitation.
  • git diff --check origin/main...HEAD — passed; reviewed all six changed files for scope and privacy.
  • The acceptance report separates native UI observations, Muse-reported HTTP results and independent offline source checks. No real key or health data was used in those probes. Android delivery, a working adapter and recurring execution are not claimed.

Review notes

  • The change and its limits are documented.
  • Checks appropriate to the guidance-only change passed; required CI still applies.
  • The diff contains no credentials, real health data, activity originals or GPS routes.

@0xBreadguy
0xBreadguy merged commit f1f242d into main Nov 8, 2026
4 checks passed
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