Single source of truth for user-configurable state.json config keys.
Keys fall into two CLI surfaces:
oss-autopilot setup --set key=value — direct scalar / list-replace sets
oss-autopilot config <key> <value> — list mutators (add-/remove-) and aliases
A key may be settable via one, the other, or both. auto means the field is
populated by internal code (e.g. starredRepos is fetched from GitHub), never
by a user command — it's listed here so scout-bridge.ts reads are auditable.
When adding a new user-configurable state.json field:
Add the field to AgentConfigSchema (state-schema.ts).
Add an entry here.
Wire the handler in commands/setup.ts and/or commands/config.ts.
The registry test (config-registry.test.ts) asserts both commands
handle every non-auto key.
Single source of truth for user-configurable state.json config keys.
Keys fall into two CLI surfaces:
oss-autopilot setup --set key=value— direct scalar / list-replace setsoss-autopilot config <key> <value>— list mutators (add-/remove-) and aliasesA key may be settable via one, the other, or both.
automeans the field is populated by internal code (e.g. starredRepos is fetched from GitHub), never by a user command — it's listed here soscout-bridge.tsreads are auditable.When adding a new user-configurable state.json field:
AgentConfigSchema(state-schema.ts).commands/setup.tsand/orcommands/config.ts.config-registry.test.ts) asserts both commands handle every non-autokey.