ConfigValidationReport
Defined in: core/dist/config/loader.d.ts:181
The outcome of gth config validate: whether any config was found, and the per-layer verdict
for EVERY layer a run would validate. Pure/read-side — it neither builds an LLM nor mutates
process globals, so it can report a verdict without the run-path’s side effects. The command
layer turns this into console output + an exit code.
GS2-29 — validateConfig mirrors the layer set initConfig validates: the discovered PROJECT
layer (if any) AND the GLOBAL layer (if any). A run validates both and exits(1) if EITHER
carries a problem, so a removed shape in the global config (with a clean project config) shows
up here exactly as the run would reject it. Both layers are kept in layers (in run
order) so the offending file is always identifiable.
Properties
Section titled “Properties”found:
boolean
Defined in: core/dist/config/loader.d.ts:183
False when neither a project nor a global config exists within the discovery boundary.
layers
Section titled “layers”layers:
ConfigLayerValidationReport[]
Defined in: core/dist/config/loader.d.ts:190
Each config layer a run would load + validate, in run order: the discovered PROJECT layer
(if any) first, then the GLOBAL layer (if any). Empty when found is false.
ok:
boolean
Defined in: core/dist/config/loader.d.ts:185
True only when a config was found AND every present layer validates OK.