docs(configuration): name the setup-vs-day-2 split explicitly - #957
Merged
Conversation
The setup wizards (CLI and dashboard) only ask a shortlist of fields; everything else in config.reference.json was left undocumented as day-2-only, so operators had no way to tell "not asked" from "missing". Add a short section naming the split with examples. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Mode-coverage audit finding: several supported modes are deliberately config.json-only — inexpressible in either setup wizard — and nothing told operators these are day-2 features rather than missing ones. The new "Setup vs. day-2" section states the split plainly, with the field set verified by diffing config.reference.json's surface against the union of both wizards' asked fields (stratum TLS/auth details, onion client-auth, XvB, energy pricing, notification webhooks among the named examples). Verifier: pass (one ambiguous phrase, fixed). Lint green, house voice. Ponytail: doc section.
🤖 Generated with Claude Code