check-backend-configurationlisted

# Check 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). What this skill does instead: resolve the configured stack, show which instance the runs will hit, prove the CLI is connected, and guide the user when it is not. 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 — lives in that stack's reference file in the `observability-cli-guides` skill, `references/<stack>.md`; the list of stacks is that skill's `references/builtin-stacks.md`. This file is the method; the reference is the content. ## 1. Resolve the stack `odd_config_get` names the configured stack — one of the values `builtin-stacks.md` lists. When the mission or the instructions name a different one, they win — whether the switch persists is the **caller's call**: `odd-observe` persists it with `odd_config_set` so the next run starts from it; `odd-verify` states the divergence and does not persist (the stored report is the contract it replays). Open the stack's row in `builtin-stacks.md` and, from it, the stack's reference file: the rest of this skill is that file's `## Configuration display` section, applied in order. **Read by section, never the whole file.** A reference runs a few hundred lines, and this skill needs two sections of it: `## CLI binary` (step 2's Detect and Install