cluster (per-user K8s view)

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.

Load the shared platform model when the task depends on app namespaces, application spaces, cross-namespace DNS, or system middleware. Use olares-cli cluster <noun> <verb> --help for syntax.

When to use

• Inspect K8s runtime objects, YAML, events, logs, or identity context.
• Execute a one-shot command in a container.
• Scale, restart, stop, start, or delete a workload; suspend/resume cronjobs; rerun jobs.
• Watch pod, workload, application, or log state.

Diagnosing why an app is broken (stuck install, crash loop, running but unreachable, image won't pull, resource pressure) is ../olares-doctor/SKILL.md — it orchestrates these cluster commands into symptom→root-cause routing. cluster stays the raw runtime view and the place that mutates K8s objects.

workload stop/start changes controller replicas; it does not update the Market lifecycle row. Use market stop/resume for app-level lifecycle.

The identity-vs-server-decides principle (cross-cutting)