backend-configurationlisted

# The Backend Configuration The user configures their observability CLI themselves; agents never run interactive auth (OAuth device codes and SSO browser logins stall subagents — observed). This skill resolves the configured stack, shows which instance the runs will hit, proves the CLI is connected, and guides the user when it is not (`## Check`); and it owns the write — the switch to another backend and the targeting values persisted for it (`## Switch`). A switch is a write, and a write deserves a preflight: a stack persisted for a CLI that is not on the machine turns every later mission into the same discovery, so the switch checks the binary first, writes second, and ends in `## Check`'s proof. Three lines this skill never crosses: it never installs anything silently (it offers, the user runs or approves), it never authenticates on the user's behalf, and it never stores or echoes a secret — credentials stay in the CLI's own auth store and are referred to by name only. This skill knows no stack by name. Everything about a stack — its CLI, what to display, how to prove the connection, what to say when it fails, what to persist — lives in that stack's reference file: in the `observability-cli-guides` skill, `references/<stack>.md`, for a stack the package ships (the list of those, their aliases and their CLIs is that skill's `references/builtin-stacks.md`), or in the observed repository, `.odd/observability-stacks/<stack>.md`, for a **custom stack** the team wrote itself