Bootstrap binary StepSettings from defaults, config, registries, and profile

Applications now bootstrap StepSettings from defaults/config/env/flags only; profiles no longer patch them.

Sections

Terminology & Glossary
📖 Documentation
Navigation
58 sectionsv0.1
📄 Bootstrap binary StepSettings from defaults, config, registries, and profile — glaze help bootstrap-binary-step-settings-defaults-config-registries-profile
bootstrap-binary-step-settings-defaults-config-registries-profile

Bootstrap binary StepSettings from defaults, config, registries, and profile

Applications now bootstrap StepSettings from defaults/config/env/flags only; profiles no longer patch them.

Tutorialconfigurationprofilesstep-settingsglazedgeppettopinocchioconfig-fileprofileprofile-registries

Bootstrap binary StepSettings from defaults, config, registries, and profile

This playbook changed with the StepSettingsPatch hard cut.

Current rule:

  1. Build StepSettings from schema defaults, config files, env, and flags.
  2. Resolve profile registries separately for runtime metadata (system_prompt, tools, middlewares).
  3. Build engines from the app-owned final StepSettings.

Profiles no longer produce final StepSettings, and ResolveEffectiveProfile no longer returns effectiveStepSettings.