{"version":"2.1.223","anchor":"code-review-telemetry-records-where-the-effort-level-came-fr","canonical_anchor":"code-review-telemetry-records-where-the-effort-level-came-fr","heading":"Code-review telemetry records where the effort level came from","tier":"internal","area":"Code Review","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/code-review-telemetry-records-where-the-effort-level-came-fr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Code-review telemetry records where the effort level came from\n\nCode review logging now records why a given effort level was picked for your run.\n\n**What**\n\nRouting telemetry for code review now distinguishes how the effort level was chosen.\n\n**Details**\n\n- `tengu_code_review_routed` gained an `effort_source` field with values \"explicit\", \"last_used\", \"ultra_fallback\" and \"session\"\n- the routing debug payload gained `lastUsed` and `willRunAsFork`\n\n**Evidence**\n\n`tengu_code_review_routed`\n\n- Area: Code Review\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}