What problem does it solve? Before an observability mission runs, someone must confirm which backend stack is configured, prove its CLI is installed and connected, and persist any backend switch or targeting values correctly — doing this ad hoc leads to failed missions and wrong-target queries. ## Core Features & Use Cases - Connection preflight (Check): Resolves the configured stack via odd_config_get, displays the effective backend configuration, runs the reference-defined connection proof, and emits a preflight handoff block for the mission. - Backend switching (Switch): Validates the target stack, checks CLI binary presence with a guided install offer, persists the switch and per-environment stack_config values via odd_config_set, then verifies with a connection proof. - Machine snapshot script: scripts/preflight.py gathers CLI versions, running containers, git state, and .odd/ store contents in one call, printing the handoff's Machine line. - Use Case: Before running an observe mission, ask the agent to confirm the configured Grafana or CloudWatch backend — it shows the target instance, proves the CLI is authenticated, and hands the mission a ready preflight block. ## Quick Start Ask the agent to check the configured observability backend and prove its CLI is connected before starting the mission.
