[Feature] Telemetry, FinOps & Budget Governance

[djm81]

Summary

• Track active opt-in telemetry and FinOps governance contracts for the five-pillar wave.
• Keep PII-safe telemetry, outcome evidence, and budget-approval behavior aligned before enterprise chargeback extends them.
• Revisit default-on telemetry only after the opt-in release proves transparency, auditability, enterprise controls, and community acceptance.

Scope

• active opt-in telemetry with enterprise-safe default-off rules
• clear telemetry disclosure of what is tracked and what is never tracked
• FinOps telemetry and outcome evidence contracts
• budget approval and enforcement gates for expensive flows

Child changes

• telemetry-01-opentelemetry-default-on (nold-ai/specfact-cli) — revised scope: active opt-in first, default-on deferred
• finops-01-telemetry-and-outcomes (nold-ai/specfact-cli)
• finops-02-budget-approval-gates (nold-ai/specfact-cli)