Issue #31857 is harder because it requires tracing router selector lifecycle, safely cancelling asynchronous tasks during dynamic reconfiguration, preserving callback behavior, and adding regression coverage. Issue #26669 provides no substantive technical scope and is therefore likely lower-effort or impossible to assess beyond a basic clarification.

The left issue requires coordinated provider parameter translation, upstream request handling, response-field compatibility, and regression coverage. The right issue provides no actionable technical scope in the supplied information and is marked stale, so its implementation effort is indeterminate but likely lower.