Description
Base Command Manager is the cluster manager under Mission Control. Its CMDaemon Prometheus exporter on each head node (disabled by default, TLS-only, client-certificate authenticated) exposes node state, service state, health check results, measurables, triggers and alert state; on liquid-cooled racks the leak-detection measurables also reach Prometheus through BCM. BCM service logs and platform events go through the logging path. A collector scraping it with an expired client certificate silently loses the whole management plane.
Acceptance Criteria
- #1 The construct emits the CMDaemon exporter metric and label shapes from the BCM documentation at a pinned version, documented in a new signals/ area file
- #2 Node state, health check results, a representative measurables subset and alert or trigger state are emitted for nodes in the GPU fixture, with leak-detection measurables on liquid-cooled racks only
- #3 BCM service logs are emitted with real message formats
- #4 Failure modes cover a node going down, a failing health check, a leak detection and an exporter certificate expiry that turns into scrape failure and a telemetry gap
- #5 Every metric, label, attribute and log field is sourced from vendor documentation or a capture at a pinned version and recorded with provenance in the named signals/ area file; anything unconfirmed is a PENDING in cantfind.md, never an invented name
- #6 Rates, counts and cardinality in any shipped blueprint are plausible for a real deployment, with the real-world basis stated in a comment; nothing is raised to force emission
Definition of Done
- #1 just check (fmt-check, lint, gen-check, env-check, docs-check, test, race, hygiene, ui-check, compose-check, helm-test, lab-check, signal-fidelity)
- #2 just gen (only if a blueprint field, construct/workload config struct, or a skill under plugins/synthkit/skills/ changed)
- #3 just dump — inventory diffed against signals/
Implementation Notes
loop47: admitted R10 vendor-contract research; implementation waits for fixture landing
loop47: public BCM v11 manual documents exporter endpoint/TLS configuration but no core metric or service-log output contract. Resume with a version-pinned CMDaemon exporter metric reference or capture and real service log examples; manual patch correspondence must be pinned. Implementation attempts 0; review-repairs 0; infra retries 0; no rejection.