Description
AGENTS.md:87 (architecture section, internal/options bullet) says otlp.go configures the “OTLP-tracing” telemetry family. It configures OTLP metrics push (internal/options/otlp.go:307-311); no TracerProvider/sdktrace exists anywhere outside vendor. The binary ships OTLP metrics and logs plus Pyroscope profiles — no traces. Fix the wording (and any other doc echoing it) so agents stop planning against a tracing family that does not exist.
Acceptance Criteria
- #1 AGENTS.md and any echoing docs describe otlp.go as OTLP metrics push
- #2 No remaining doc claims the exporter emits its own traces
Definition of Done
- #1 just check
- #2 just gen (if any generated artifact changed) and the diff committed
Implementation Plan
Wave 1 execution: correct the sole false tracing claim in the repository architecture guide to OTLP metrics push; verify no documentation claims the exporter emits traces; run generated-doc validation and the integrated gate. This is documentation-only, so validate rather than add a test and skip CodeRabbit.
Implementation Notes
Landed as 66192f54a39d765eec356ec97ee05045d85a3624. The sole false trace-emission claim was corrected to OTLP metrics push; targeted telemetry-language search found no remaining documentation claim. just docs-check and integrated just check passed. CodeRabbit was skipped because this is documentation-only. Exact-head CI run 33579700413 completed successfully and ci-success passed.
Final Summary
Corrected the architecture guide to describe internal/options/otlp.go as OTLP metrics push rather than tracing and confirmed no documentation claims the exporter emits OpenTelemetry traces. Verified just docs-check, just check, and exact-head CI run 33579700413. Commit: 66192f54a39d765eec356ec97ee05045d85a3624.