/setup

Interactive onboarding. The deterministic parts (detection, pin verification, marker) run in the Go binary (evolve setup detect|complete); the judgment parts (recommend models, explain the pipeline) run HERE, in your session — zero extra API cost. You PROPOSE per-phase pins; the kernel CLAMP (envelope + allowed_clis) is enforced two ways: evolve setup detect reports any pin that breaches the floor as pin_violation, and dispatch hard-fails an out-of-bounds pin at cycle time. Step 9 removed the old llm_config.json layer — the durable per-phase override is now .evolve/policy.json pins. See docs/architecture/setup-onboarding.md and the deterministic core in go/internal/setup/setup.go.

When to use

The loop printed [setup] First run …, or the user typed /setup, or asked to configure models / learn the pipeline.
Re-running is always safe — it re-detects and rewrites .evolve/policy.json pins.

Binary

Call evolve if on PATH; otherwise ./go/bin/evolve (or $EVOLVE_GO_BIN). All commands below are read-only except complete (stamps the marker) and your Write of .evolve/policy.json.

Procedure

Detect. Run evolve setup detect --json and parse it. The digest has clis[] (per family: binary_present, auth_mode, subscription_type, capability_tier, verdict, and tier_models {fast,balanced,deep} → that CLI's NATIVE model) and phases[] (per role: current_cli, current_tier, source — profile or policy-pin, envelope {min,default,max}, cross_family_with, allowed_clis, and pin_violation when a pin breaches the floor). A malformed .evolve/policy.json shows up as a top-level policy_error.
Present the detection as a compact table — one row per CLI family with binary/auth/tier/verdict.
- Caveat (state, don't hide): on macOS, claude may report MISCONFIGURED/blocked even when authed, because detection only checks ~/.claude/.credentials.json and misses Keychain-stored OAuth. If the user is clearly running in a Claude session, treat claude as available and say so.