@deepseek-ai/dsh-app-boot

Previewing the effective configuration

Before you boot, you can print the exact configuration the app will mount: the dump shows the composed entry list with !!js expressions verbatim, grouped under comments naming each source file and the patch layers that changed it, as one loadable YAML document. Patches that match no row are reported with their layer label; a missing, unparsable, or invalid config fails the dump.

Inspecting plugin configuration schemas

generateConfigSchema takes a diagnostic bin name, a prepared on-disk profile, ordered patch lists, and an installation anchor, and returns ConfigSchemaDump. App-boot owns composition, runtime resolution, and collection diagnostics. The caller owns profile preparation, home/argv layer selection, process streams, and exit policy. createConfigProjector, isNativeConfigSchema, and LOADER_EXPRESSION_SCHEMA are exported for callers that project one live plugin Config without profile collection; projected value positions reference #/$defs/loaderExpression, so the enclosing document must define it.

The generated JSON Schema 2020-12 describes the composed entry list, with $defs.patchList for root-tree overlays and shared definitions projected from plugin Config graphs. It includes disabled entries, native groups, and literal YAML/JSON includes; builtin and canonical native package exports are matched using each tree's module-resolution base, including profile-local copies. Custom carriers are not inferred from their config fields. A missing include with literal initial entries is expanded in memory without writes. Discovery and projection diagnostics remain in x-cordis, including unknown Configs and partial constraints. The CLI schema-dump reference owns the output fields and editing semantics.

The projector preserves native omission behavior by checking literal defaults against generated schemas with Ajv, without executing native validators or transform callbacks. Regex compatibility checks and unsupported or recursive-default cases produce explicit limitations. Opaque input adaptations and lazy metadata effects widen validation rather than replaying native mutation. Non-JSON default/presentation annotations are omitted with limitations without losing the structural schema; an unrepresentable default leaves omission acceptance unknown unless the field is required. These dependencies load only when collection runs. Imports, Config getters, and lazy builders still execute trusted code; collection is not a sandbox. Do not overlap profile-resolution interceptions. The collector releases its interception before returning, while Node retains imported modules; runtime-created plugins and Agent preset instances remain outside discovery.