setup-specialists

Validate specialist configuration by running the setup flow to verify Pi model availability, apply three-layer merge overrides, and check probe settings. It confirms package defaults, global config, and repo layers are correctly merged without shadowed or missing values.

The three-layer merge model combines package defaults, global user config, and per-repo overrides. It preserves allowed fields while blocking unsafe global overrides, ensuring local repo settings correctly shadow global behavior without breaking core configurations.

Fix missing provider credentials and unsupported defaults by running the doctor setup flow. It identifies shadowed configurations, validates specialist readiness, and helps remap models or adjust privacy exclusions to restore proper functionality.

Yes, you need to verify Pi models before bootstrapping settings. Checking your Pi model fleet identifies which specialists lack a usable model, allowing you to choose provider auth and apply valid global overrides safely.

Yes, you can use sp init --global and sp edit --global to standardize global behavior. These commands bootstrap shared user overrides and apply uniform specialist settings across all your repositories before validating readiness.

Specialist configuration breaks after model changes when per-repo overrides point to unavailable Pi models. Running the setup flow validates specialist readiness, remaps models, and resolves conflicts between package defaults and global user config.