doca-telemetry

Use this skill when reading **DOCA hardware-counter events** from a `doca_dev` via the per-domain DOCA Telemetry reader libraries — `doca_telemetry_pcc`, `_dpa`, `_diag`, `_adp_retx`, `_phy`, `_pci`. This is the **counter-READER** surface — there is no NetFlow / IPFIX / local-socket collector framework here; the bundle previously framed it that way and that framing is wrong. Each domain ships its own `doca_telemetry_{domain}_*` API: cap-query `_cap_is_supported(devinfo)`, `_create()` on a `doca_dev`, `_start()`, then per-domain read / sample. Trigger even when the user does not say "DOCA Telemetry" — typical implicit phrasings: "read PCC counters from my BlueField app", "sample DPA counter exports", "expose PHY / PCI / DIAG counters from this `doca_dev`". Refuse and route elsewhere for the publishing / export side (`doca-telemetry-exporter`), DOCA Telemetry Service (DTS) as deployed (out of scope), NetFlow / IPFIX collectors, and plain stdout logging.