gateway-doctorlisted

# Agent Gateway — doctor Diagnose and explain gateway issues without ever revealing secrets. ## What to do 1. **Run diagnostics:** ```bash agw doctor ``` It reports prerequisite versions, runtime paths and permissions, native Claude resolution, configured models, provider authentication state, an inspectable Claude `availableModels` conflict (if any), and managed-proxy state. It exits non-zero if it finds a blocking problem. Secrets are always redacted. 2. **Map each failing check to an action:** - *provider not authenticated / expired* → `agw auth chatgpt`. - *native claude not found* → install Claude Code, then `agw setup`. - *port in use by an unrelated process* → free the port or change `port` in `~/.config/agent-gateway/config.yaml`, then `agw proxy restart`. - *proxy running with a different config/version* → `agw proxy restart` (the only path that applies a changed fingerprint). - *availableModels excludes a configured model* → this is managed Claude policy the gateway cannot override; per-task routing to that model is unavailable until the policy allows it. Do not claim success via a fallback model. - *bad file permissions* → re-run `agw setup`, which restores 0700/0600. 3. **Inspect sanitized logs if needed:** ```bash agw status # proxy identity + model→provider mapping agw logs --lines 100 ``` `agw logs` shows only sanitized operational lines (lifecycle, public model, prov