Problem
components/receivers/pyspy/README.md line 3 carries a stale banner:
⚠️ Status (2026-05-22): Scheduled for deletion at v0.3.0 per RFC-0013 §7. Replaced by parca-agent (eBPF) per RFC-0013 §2. Security posture changes: CAP_SYS_PTRACE → CAP_SYS_ADMIN/CAP_BPF - operator review window in v0.3.0. Operators: see the migration guide for old→new chart values mapping (one-version compat). Contributors: do not invest further in this receiver - file improvements upstream instead.
This banner pre-dates the PR-M deferral memo in #222, which keeps pyspy in v0.3.0 with unchanged zero-capability posture until OTel Profiles reaches Beta + parca-agent gains OTLP export (re-evaluation conditions in #222).
PR #254 reconciled docs/migration/v0.2-to-v0.3.md against #222 but explicitly left this README out-of-scope per a reconcile-only contract.
Where
components/receivers/pyspy/README.md:3
Fix prescription
Re-frame the banner so it tells operators the truth: pyspy ships as-is in v0.3.0, deletion is deferred to v0.4.0+ pending the #222 trigger conditions, and the security-posture migration content lives in docs/migration/v0.2-to-v0.3.md as forward-looking material. Suggested wording:
⚠️ Status (deferred per #222): This receiver ships in v0.3.0 with the same zero-capability posture as v0.2.x. PR-M (delete this receiver + ship parca-agent recipe) has been deferred to v0.4.0+ pending two upstream triggers: (1) OTel Profiles reaches Beta and the service.profilesSupport feature-gate is removed, and (2) parca-agent gains OTLP export (or PR-M is re-scoped to an "otelcol-ebpf-profiler sibling distro" pattern). See docs/migration/v0.2-to-v0.3.md for forward-looking operator preparation material on the eventual CAP_SYS_PTRACE → CAP_SYS_ADMIN/CAP_BPF migration.
Also sweep components/receivers/pyspy/RUNBOOK.md for the same staleness pattern while you are in the file.
Acceptance
Related: #222, #254.
Problem
components/receivers/pyspy/README.mdline 3 carries a stale banner:This banner pre-dates the PR-M deferral memo in #222, which keeps pyspy in v0.3.0 with unchanged zero-capability posture until OTel Profiles reaches Beta + parca-agent gains OTLP export (re-evaluation conditions in #222).
PR #254 reconciled
docs/migration/v0.2-to-v0.3.mdagainst #222 but explicitly left this README out-of-scope per a reconcile-only contract.Where
components/receivers/pyspy/README.md:3Fix prescription
Re-frame the banner so it tells operators the truth: pyspy ships as-is in v0.3.0, deletion is deferred to v0.4.0+ pending the #222 trigger conditions, and the security-posture migration content lives in
docs/migration/v0.2-to-v0.3.mdas forward-looking material. Suggested wording:Also sweep
components/receivers/pyspy/RUNBOOK.mdfor the same staleness pattern while you are in the file.Acceptance
make doc-checkstays greenRelated: #222, #254.