What
The 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.
Details
- 2.1.220 emitted 32 such events; 2.1.221 has two,
tengu_dead_probe_tool_alias_execandtengu_dead_probe_hook_updated_mcp_tool_output. - Removed probes include the plugins v2 dual-file rename and plugins v1 file probe, top-level
experimental.themesandexperimental.monitors, global-config env, attachment rename, daemonorigin: auto, the Chrome legacy-socket scan, the remote-flag alias probe,tengu_dead_probe_plugin_toplevel_experimental,tengu_dead_probe_pinned_sidecarand bothtengu_dead_probe_mcp_subsec_timeoutcall sites in MCP tool timeout and idle timeout resolution. - The associated dedupe sets and flush helpers were deleted with them.
Evidence
tengu_dead_probe_, tengu_dead_probe_tool_alias_exec, tengu_dead_probe_mcp_subsec_timeout
Strings lifted out of the shipped bundle, so the claim above can be checked against them.