show-otel-instrumentation-reportlisted

# Show an OTel Instrumentation Report The stored report is the input the spec-driven instrumentation plan is built from — the right artifact for the next wave, the wrong one for the human closing the mission: several screens of tables, env blocks, and doc links bury the takeaways. This skill renders the closing synthesis. The report file stays the deliverable; only what the human sees at the end of the mission changes. ## Input The persisted report to render: the file the `create-otel-instrumentation-report` skill just stored, or any stored report the caller names. Read it from disk — the synthesis renders the stored file, not the conversation's memory of it. ## The synthesis, in order 1. **Headline** — one bold line answering "what will happen": services covered, dominant approach, package count, open decisions (`2 services, zero-code approach, 7 pinned packages, 3 decisions open`). 2. **Where it lives** — one line: the stored path and the commit that carries it. 3. **Plan at a glance** — the report's own summary table (its section 2), reused as-is: it already carries one row per service with approach, pinned key packages, effort, and risk flags — the pinned packages ARE what the implementation wave will add. Follow it with the recommended implementation order, one line. 4. **Decisions the spec must settle** — the count, then one line per open question (the report's section 4). 5. **Next action** — one line naming the loop's next step: build t