Repository navigation
Clarify private key delivery and Muse entry syntax - #26
Merged
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.
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.Review notes