{"version":"2.1.221","anchor":"dead-probe-telemetry-pruned-to-two-events","canonical_anchor":"dead-probe-telemetry-pruned-to-two-events","heading":"Dead-probe telemetry pruned to two events","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/dead-probe-telemetry-pruned-to-two-events","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Dead-probe telemetry pruned to two events\n\nMost of the one-shot probes checking whether old code paths still run were removed.\n\n**What**\n\nThe one-shot `tengu_dead_probe_*` instrumentation that checked whether legacy code paths were still reached has been almost entirely removed, along with the call sites and the dedupe flags that guarded them.\n\n**Details**\n\n- 2.1.220 emitted 32 such events; 2.1.221 has two, `tengu_dead_probe_tool_alias_exec` and `tengu_dead_probe_hook_updated_mcp_tool_output`.\n- Removed probes include the plugins v2 dual-file rename and plugins v1 file probe, top-level `experimental.themes` and `experimental.monitors`, global-config env, attachment rename, daemon `origin: auto`, the Chrome legacy-socket scan, the remote-flag alias probe, `tengu_dead_probe_plugin_toplevel_experimental`, `tengu_dead_probe_pinned_sidecar` and both `tengu_dead_probe_mcp_subsec_timeout` call sites in MCP tool timeout and idle timeout resolution.\n- The associated dedupe sets and flush helpers were deleted with them.\n\n**Evidence**\n\n`tengu_dead_probe_`, `tengu_dead_probe_tool_alias_exec`, `tengu_dead_probe_mcp_subsec_timeout`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}