What problem does it solve? It answers whether the local ptp telemetry receiver is running, where its store lives, and how many runs are closed or unclosed per epic, without ever creating files or mutating state. ## Core Features & Use Cases - Read-only status report: Resolves telemetry mode and root from configuration independently of whether a store exists, and never creates directories or files. - Per-epic run accounting: Reports total, closed, and unclosed run counts per epic directory, plus the _unattributed/ bucket as its own health signal. - Three unambiguous states: Distinguishes mode off, mode on with no store, and mode on with unclosed runs, so an absent store is never misread as telemetry being off. - Use Case: After a pipeline run, ask for the telemetry status to confirm the receiver is up and check whether any run was left unclosed before starting the next change. ## Quick Start Ask the assistant to run the ptp telemetry status report and show the resolved mode, store root, and per-epic run counts.