docs: from-scratch setup playbook + token identity explainer - #43
Merged
Conversation
SKILL.md assumed a config already existed; add a 'Setup from scratch' section that walks an agent through zero-to-working (and secured) setup: write .cfg.toml, pick an identity mode, generate a token hash without leaking the secret (cfg identity-hash --stdin -> tokens[] -> CFGIT_IDENTITY_TOKEN), set permissions, init/doctor/import. Also add an 'How it works, and what it does (and doesn't) protect' subsection to IDENTITY_AND_ATTRIBUTION.md explaining the common confusion: the hash lives in the shared config, the raw token stays local, cfgit re-verifies per command (no server/ session), so it is attribution not a hard boundary — prefer db_principal for a real security boundary. All flags/keys verified against the code.
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
2 participants
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.
Follow-up to the setup-docs audit. Two gaps:
.cfg.toml, pick an identity mode, generate a token hash without leaking the secret (cfg identity-hash --stdin→tokens[]→CFGIT_IDENTITY_TOKEN), set permissions, then init/doctor/import.IDENTITY_AND_ATTRIBUTION.md: the hash lives in the shared config, the raw token stays local, cfgit re-verifies per command (no server/session) — so it's attribution, not a hard boundary; preferdb_principalfor a real security boundary.Every flag/key referenced (
cfg doctor --status,cfg identity-hash --stdin,token_env/sources/admin_actions/CFGIT_IDENTITY_TOKEN) verified against the code.