Description
41 extra_metric gaps in signals/k8s.md and 2 in signals/k8s-addons.md: families the EKS readback and the k3d lab publish that synthkit does not emit. Small enough to verdict individually, and worth doing separately from the CloudWatch block because the sourcing question is different — these come from named upstream exporters whose metric sets are documented, rather than from a cloud vendor’s metric catalogue.
Also covers the 19 host.md gaps, which are label and instrument findings rather than missing families.
Same discipline as the CloudWatch block: a verdict per family, sourced names only, and a cantfind.md PENDING rather than a guess where the shape is unconfirmed.
Acceptance Criteria
- #1 Every k8s and k8s-addons extra_metric gap carries a verdict: emit, out of scope with a reason, or a cantfind PENDING
- #2 The 19 host.md findings are triaged as label or instrument issues, distinct from missing families
- #3 No family is emitted whose names and labels are not sourced from signals/ or current upstream docs
Definition of Done
- #1 make gate (build vet test race rw-proto-check spdx-check forbidden-words)
- #2 make blueprint-schema (only if a blueprint field or construct/workload config struct changed)
- #3 DRY_RUN=true go run ./cmd/synthkit -once -dump — inventory diffed against signals/
Implementation Plan
Verdict all 41 k8s and 2 k8s-addon missing families individually; triage 19 host findings as label or instrument issues; emit only sourced subsets; report counts by class, area, and substrate plus PENDING rows.
Implementation Notes
2026-09-02 current-corpus correction: the durable record covers 43 k8s rows plus 2 k8s-addon rows, not the stale 41 plus 2 wording. Fifteen kube-proxy component rows are already emitted, 28 exporter self-metrics and 2 CoreDNS hosts-plugin rows are deliberately out of scope, and no new family was emitted. All 19 host findings are native-OTLP label or instrument dispositions; five type rows remain capture-blocked by existing SK-103. Focused tests, docs tests, integrated just check, and just dump passed; generation was not applicable.
Final Summary
2026-09-02: Verdicted all current k8s, add-on, and host findings by cause: 15 rows already emitted, 30 deliberately out of scope, and 19 host rows classified separately with five type rows retaining the existing capture boundary.