Repository navigation
Define Setup in the glossary - #133
Merged
Merged
Conversation
Setup writes the User config from a few questions, offered by the first Run on a machine with no User config. Spec in #126. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merged
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.
Summary
Adds Setup to
CONTEXT.md, right after User config, so the tickets for #126 (#127–#132) have a term to build on.Refs #126. Glossary only: no code, and it doesn't close the issue.
Evidence
CONTEXT.mdhas no term for writing the User config; the spec in thirdshift setup #126 and its tickets say "Setup" with nothing to point to.After: the term is defined, in the words the spec uses.
Merge Danger
Door: two-way
A revert removes four lines.
Blast Radius: none
Docs only. Nothing reads
CONTEXT.mdat build or run time.🤖 Generated with Claude Code