doctor (runtime diagnosis)

Shared front door: load ../olares-shared/SKILL.md for suite routing, active-profile selection, platform entry points, and the auth proceed/stop gate. Load its auth reference only when login, profile switching, token storage, or auth recovery is actually needed.

This skill is a thin diagnostic router over Market, Cluster, and Dashboard. Load the shared application-state model when interpreting lifecycle states, TTLs, serialized downloads, or running. Use olares-cli doctor <verb> --help for syntax.

When to use

• An install/upgrade is stuck or never reaches running; an app won't start.
• An app crashes / restarts repeatedly (CrashLoopBackOff, exit codes, config errors).
• An image won't pull (ImagePullBackOff / ErrImagePull / wrong arch), or you want to find unused local images.
• An app is running but its entrance is unreachable / errors / times out.
• The system or an app is slow, or a GPU/resource binding is rejected (node-pressure).

Both catalog apps (installed via market) and your own dev apps (deployed via chart) route runtime failures here. Once the root cause is found, the fix for a dev app you authored is usually a chart edit — hand back to ../olares-chart/SKILL.md.

Mental model: doctor answers "why is this broken and what do I do next?" Diagnosis is read-only by default; the only mutation is the explicitly approved thirdleveldomain --force-dedupe repair. The four-skill develop->deploy->debug combo is chart + market + olares-shared + doctor.

Symptom routing