OpenTelemetry is too complex to set up in local dev and CI with silent failures and heavy overhead

Setting up OpenTelemetry in local dev and CI means wiring collectors, configuring exporters, guessing at span correctness, and spinning up a cloud backend before you see a single trace. No tool auto-instruments a project from the command line, validates that spans are semantically correct, and runs a local trace viewer in the same step. This CLI fills that gap: one command detects language and framework, injects OTel instrumentation, watches the span stream in real time, and opens a lightweight local UI for trace exploration, with a headless CI mode that fails the build when spans are malformed or missing.