{"version":"2.1.221","anchor":"telemetry-values-are-validated-before-being-sent","canonical_anchor":"telemetry-values-are-validated-before-being-sent","heading":"Telemetry values are validated before being sent","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/telemetry-values-are-validated-before-being-sent","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Telemetry values are validated before being sent\n\nUnexpected telemetry values are replaced with a placeholder instead of being sent raw.\n\n**What**\n\nSeveral event properties now pass through pattern or allowlist validators that substitute `nonconforming` instead of forwarding an unexpected raw value.\n\n**Details**\n\n- Validated: currency in the extra-usage dialogs, evaluator model name in compaction events, fork label in `tengu_forked_agent_default_turns_exceeded`, and the attach `via` value.\n- `tengu_mcp_list_paginated` gained a `source` dimension, defaulting to \"pages\".\n- `tengu_headless_mcp_prewait` gained `waitForDeferrable` and `deadlineMs`.\n\n**Evidence**\n\n`tengu_forked_agent_default_turns_exceeded`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}