docs(rfc-0013): amend §migration — PR-I/K sub-slicing + PR-B2 gate

[trilamsr]

Summary

Four amendments to docs/rfcs/0013-distro-first-pivot.md (plus a one-line sweep across 6 companion docs) per the scope-review findings staged before PR-I.1 / PR-K / PR-M code work begins. Pre-stages each decision in the RFC so the autonomous code PRs don't escalate mid-flight.

Root cause

#181 (RFC-0013 PR-I in-repo submodule rescope) was incomplete:

1. Sweep missed 6 companion docs still pointing at the original-design external tracecoreai/tracecore-components repo.
2. §7 listed 3 GitHub workflows for deletion that were already removed pre-RFC and 1 issue template (component-bug-dcgm.yml) that was already removed pre-RFC.
3. PR-K was a single 4-receiver-delete-plus-chart-migration mega-PR with no decoupling of the internal/synthesis/patterns/ k8sevents dep break, which is on PR-I.2's critical path.
4. PR-I.1 conflated the module/go.mod scaffolding with the git mv + package rename, blocking PR-I.1a from landing without PR-B2 even though the scaffolding step has no nccl_fr dep.

Mid-flight discovery during merge cycle: merged commit #188 (feat(pivot): PR-B2 — port dcgm off internal selftel + lifecycle) reused the PR-B2 slug for a PR-B1-shape dcgm port (which is moot since dcgm is deleted entirely in PR-F), creating a naming collision against the canonical PR-B2 defined in the RFC — the nccl_fr internal/{pipeline,consumer,runtime/lifecycle} → upstream port that hard-gates the PR-I.1b git mv.

Amendments

1. §6/§7 sweep miss (Amendment 1): Remove surviving tracecoreai/tracecore-components external-repo references across docs/getting-started.md, docs/followups/M11.md, docs/followups/M19.md, docs/FOLLOWUPS.md, docs/rfcs/0003-pipeline-runtime-and-component-contract.md, AGENTS.md. All re-pointed at github.com/tracecoreai/tracecore/module per RFC-0013 §6. Verified zero surviving stale refs.
2. §7 nonexistent workflow entries (Amendment 2): Collapse pyspy-integration.yml, python-publish.yml, kernelevents-integration.yml deletion rows into one row marked "already removed pre-RFC". component-bug-dcgm.yml also already removed. Only component-bug-kernelevents.yml survives for PR-K. §4 v0.3.0 row + PR-M slug cleaned for consistency.
3. §migration PR-K sub-slice (Amendment 3):
   • PR-K.1 — sever internal/synthesis/patterns/ from components/receivers/k8sevents via local model types in internal/synthesis/patterns/model.go. No deletions. Unblocks PR-I.2.
   • PR-K.2 — delete components/receivers/{clockreceiver,kernelevents,k8sevents,containerstdout} + migrate ~86 test fixtures + delete tools/failure-inject/xidgen/ + keep tools/failure-inject/ncclhang/.
   • PR-K.3 — chart cleanup: flip containerstdout-on-values.yaml to filelog+container-stanza, delete containerstdout-rbac.yaml, delete .github/ISSUE_TEMPLATE/component-bug-kernelevents.yml, ship NOTES.txt deprecation + values-key removal.
4. §migration PR-I sub-slice + PR-B2 promotion (Amendment 4):
   • PR-B2 reframed as hard gate for PR-I.1b: port components/receivers/nccl_fr off internal/{pipeline,consumer,runtime/lifecycle} to upstream go.opentelemetry.io/collector/{component,receiver,consumer,pipeline}. Slug-collision note added re: merged feat(pivot): PR-B2 — port dcgm off internal selftel + lifecycle #188.
   • PR-I.1a — module/go.mod + root go.work + builder-config.yaml replaces: skeleton. No file movement. Tag module/v0.0.1 (genesis tag, validates the tagging contract).
   • PR-I.1b — git mv components/receivers/nccl_fr → module/receiver/ncclfrreceiver + git mv pkg/nccl/fr_parser → module/pkg/nccl/fr_parser + rename Go package nccl_fr → ncclfrreceiver + update all importers. Hard-gated on PR-B2. No new tag; next bump is module/v0.1.0 at PR-I.2.
   • PR-I.2 — rankjoinprocessor + patterndetectorprocessor net-new. Hard-gated on PR-K.1. Tag module/v0.1.0 (first version pinned in builder-config.yaml for v0.2.0).

Also: PR-J marked (landed, #195) with note that recipe docs landed but chart-values compat map follows in PR-K.3.

Adversarial review (5 lenses, inline)

• (a) PR slug internal consistency: PR-I.1b ↔ PR-B2 ↔ PR-I.2 ↔ PR-K.1 bidirectional gates all match. PR-J landed marker consistent with docs(integration): PR-J — filelog/journald/k8sobjects/prometheus recipes #195. §4 v0.2.0 row has pre-existing drift (mentions dcgm+kueue in v0.2.0 when PR-F+chore(pivot): delete kueue + kineto receivers per RFC-0013 #168 already deleted them in v0.1.0) — out of these 4 amendments' scope; flag for follow-up.
• (b) PR-B2 hard-gate naming: tightened from "Hard gate for PR-I.1" to "Hard gate for PR-I.1b" — accurate because PR-I.1a is scaffolding-only with no file movement.
• (c) Sub-PR numbering collision: feat(pivot): PR-B2 — port dcgm off internal selftel + lifecycle #188 explicitly addressed in slug-collision note. feat(pivot): port clockreceiver off internal selftel + lifecycle #185/feat(pivot): port stdoutexporter off internal/selftelemetry #186/feat(pivot): port kernelevents off internal selftel + lifecycle #187/feat(pivot): port otlphttp off internal/selftelemetry (PR-F unblock) #193/feat(pivot): port pyspy off internal selftel + lifecycle (PR-F unblock) #194/feat(pivot): port k8sevents off internal selftel + lifecycle (PR-F unblock) #196 are PR-B1-shape ports for non-nccl receivers (no PR-slug label in their commits), no collision.
• (d) Stale external-repo refs: grep -rn "tracecoreai/tracecore-components" docs/ AGENTS.md README.md returns zero hits post-amendment.
• (e) Cross-reference link integrity: docs/migration/v0.1-to-v0.2.md references #migration--rollout and #3-customer-stable-telemetry-contracts; both anchors preserved (§ headers unchanged). make doc-check confirms 526 markdown links resolve.

Test plan

• make doc-check — 526 markdown links resolve, 0 stale refs, banned-phrase lint clean, alert-check + chart-appversion gates green.
• Pre-push hooks: golangci-lint clean, go vet clean, go mod verify clean.
• CI doc-check + actionlint + zizmor gates pass on PR.

NONE