Problem
PR #781 adds query-tracker accuracy and latency fields, but the LocalPlannerClient calls the legacy Controller generate path. That path uses the legacy generator and does not read controller_options, so the new fields do not affect generated plans. Requiring a positive tracker accuracy SLA would also break existing drop-in configurations without changing behavior.
Desired outcome
Either wire the query tracker to the optimizer pipeline that enforces SLAs, or retain the legacy tracker behavior without SLA settings. Decide and implement the architectural integration separately from #781.
Context
Raised during review of #781.
Problem
PR #781 adds query-tracker accuracy and latency fields, but the LocalPlannerClient calls the legacy Controller generate path. That path uses the legacy generator and does not read controller_options, so the new fields do not affect generated plans. Requiring a positive tracker accuracy SLA would also break existing drop-in configurations without changing behavior.
Desired outcome
Either wire the query tracker to the optimizer pipeline that enforces SLAs, or retain the legacy tracker behavior without SLA settings. Decide and implement the architectural integration separately from #781.
Context
Raised during review of #781.