feat(pivot): port pyspy off internal selftel + lifecycle (PR-F unblock)

[trilamsr]

Summary

Ports components/receivers/pyspy off internal/selftelemetry + internal/runtime/lifecycle using the sibling co-location pattern established by PR #184 (nccl_fr reference impl). selftel.go + lifecycle.go now live next to the receiver source.

Unblocks RFC-0013 PR-F deletion of those internal moats.

What changed

• selftel.go (new) — receiver-scoped selfTelemetry interface + selfTelemetryImpl (OTel-backed) + noopSelfTelemetry + recordInitError. Metric names + label shape preserved 1:1 with internal/selftelemetry:
  • tracecore.receiver.errors_total{kind,component_id}
  • tracecore.receiver.emissions_total{component_id}
  • tracecore.receiver.collection_latency_seconds{component_id} (12-bucket boundaries, matches v0.1.x)
  • tracecore.receiver.degraded_seconds_total{component_id} (observable counter)
  • tracecore.receiver.last_activity_unix_seconds{component_id} (observable gauge)
  • tracecore.selftelemetry.init_errors_total{kind,component_id,reason} (factory-fallback signal)
• lifecycle.go (new) — slim single-source variant (no Add()). pyspy fans its three goroutines (scan loop, trigger cadence driver, trigger run loop) via its own sync.WaitGroup inside runAll, so lifecycle only needs Start + Shutdown.
• kinds.go — kind is now a receiver-local type. kindPanic is declared locally (replaces selftelemetry.KindPanic).
• factory.go — uses local newSelfTelemetry / recordInitError / reasonInstrumentRegister.
• pyspy.go — fields/types switched to local sibling.
• pyspy_test.go — uses sibling-local fakeTelemetry captor (replaces selftelemetry.CapturingReceiver).
• selftel_test.go (new, RED-first TDD) — 7 tests covering noop safety, nil-MP, errors_total kind+component_id, scope-name pin, init_errors_total, nil-MP safety on recordInitError, factory fallback path.
• fake_telemetry_test.go (new) — test-only captor implementing the selfTelemetry interface; mirrors the kernelevents export_test.go pattern.

Scope-name standard

Instrumentation scope pinned to the receiver's Go import path:

github.com/tracecoreai/tracecore/components/receivers/pyspy

When the receiver moves to module/receiver/pyspyreceiver/ in PR-I.1, the scope name moves with it (matches OTel convention).

Lifecycle pattern decision

pyspy uses single-source lifecycle (like nccl_fr), NOT multi-source (like kernelevents). The receiver's runAll callback owns a local sync.WaitGroup and fans into three goroutines from within the single lifecycle.Start(ctx, r.runAll) call. No Add() needed → dropped from the slim sibling.

Tests

$ go test ./components/receivers/pyspy/ -count=1
ok  	github.com/tracecoreai/tracecore/components/receivers/pyspy	0.735s

$ go test -race ./components/receivers/pyspy/ -count=1
ok  	github.com/tracecoreai/tracecore/components/receivers/pyspy	1.745s

$ make check
0 issues.

13 targeted tests pass (7 new selftel + 6 existing receiver lifecycle tests).

Wave context

pyspy is 1 of 4 remaining unported consumers of internal/selftelemetry + internal/runtime/lifecycle. Sibling agents (otlphttp / containerstdout / k8sevents) are landing in parallel; this PR's scope is the pyspy receiver only — zero file overlap with the parallel work.

Test plan

• go test ./components/receivers/pyspy/ -count=1 — green
• go test -race ./components/receivers/pyspy/ -count=1 — green
• make check — 0 lint issues, vet clean, modules verified
• Scope name asserted at github.com/tracecoreai/tracecore/components/receivers/pyspy
• Factory fallback ticks tracecore.selftelemetry.init_errors_total on instrument-register failure
• Noop hot-path methods never panic; nil-MP rejected with sentinel error
• Existing receiver tests (Start_EmptyUDSDir, Start_NonExistent, Start_TopLevelDisabled, Shutdown_HonorsContextBudget, Shutdown_Idempotent) still pass against the sibling

NONE