{"version":"2.1.227","anchor":"probes-report-whether-old-code-paths-are-still-reached","canonical_anchor":"probes-report-whether-old-code-paths-are-still-reached","heading":"Probes report whether old code paths are still reached","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/probes-report-whether-old-code-paths-are-still-reached","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Probes report whether old code paths are still reached\n\nOne-off counters now show which old code paths are still being used, so they can be removed.\n\n**What**\n\nFour one-shot telemetry probes now fire the first time a legacy path is hit, to work out what can be deleted. They cover the Co-Authored-By attribution setting, legacy local settings, the legacy progress bridge, an older token-adoption path and legacy plugin tip counts. No user-visible effect.\n\n**Details**\n\n- Each probe is deduplicated per call site and can be reset; the token-adoption probe reports the site it fired from, and the plugin tip probe fires once per distinct outcome pair.\n\n**Evidence**\n\n`tengu_dead_probe_include_coauthored_by`, `tengu_dead_probe_adopt_ticks_token`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}