What problem does it solve? Telemetry contracts drift silently when event names change, JSONL envelope shapes evolve, or /api/health and /api/status payloads are modified without updating downstream consumers like z-server ingestion and UI dashboards. This Skill provides a structured procedure to detect, update, and validate telemetry contract changes so emitters and consumers stay in lockstep. ## Core Features & Use Cases - Contract Surface Identification: Locates the stable surfaces that must not drift, including telemetry JSONL envelope shape, event names with required fields, and /api/health and /api/status payload shapes. - Lockstep Updates: Guides updating emitter and consumer code together, along with the smallest tests that enforce the contract. - Anti-Pattern Guardrails: Flags risky changes such as blindly renaming events without checking downstream consumers or bloating /api/status with deeply nested payloads. - Use Case: When adding a new field to a telemetry event consumed by z-server, use this Skill to find the relevant session docs, update both sides, add a contract test, and record the migration rationale. ## Quick Start Use the telemetry-contracts skill to check whether renaming this telemetry event will break the /api/status consumers and z-server ingestion.
