{"version":"2.1.265","anchor":"designsync-tool-telemetry-now-validates-dsmethod-against-a","canonical_anchor":"designsync-tool-telemetry-now-validates-dsmethod-against-a","heading":"DesignSync tool telemetry now validates dsMethod against a known method list","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/designsync-tool-telemetry-now-validates-dsmethod-against-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### DesignSync tool telemetry now validates `dsMethod` against a known method list\n\nDesignSync tool telemetry now checks the method name against a fixed list instead of logging it raw\n\n**What**\n\nWhen Claude Code records telemetry about which DesignSync tool method was used (things like `list_projects`, `get_project`, `list_files`, `get_file`, `finalize_plan`, `write_files`, `delete_files`, `register_assets`, `unregister_assets`), it now looks the reported method name up against a fixed list of known method names and records the match, instead of logging whatever string was passed in directly. This also applies to the error telemetry recorded when a DesignSync tool call fails.\n\n**Why**\n\nThis keeps telemetry data consistent and prevents unexpected or malformed method names from being recorded as-is; it has no effect on what the DesignSync tool actually does.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}