Code review logging now records why a given effort level was picked for your run.
What's wrong with this entry?
Routing telemetry for code review now distinguishes how the effort level was chosen.
tengu_code_review_routedgained aneffort_sourcefield with values "explicit", "last_used", "ultra_fallback" and "session"- the routing debug payload gained
lastUsedandwillRunAsFork
tengu_code_review_routed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.219
PR-review anchor repo names reject "." and ".."
Both mention code review
-
v2.1.219
Composed PR-review publish refusal explains whether it is a live switch
Both mention code review
-
v2.1.239
Code review findings now carry a short summary and a category
Both mention code review