fix(curator): respect curator.auxiliary config for review model

[apcjoaofilho]

Problem

The _run_llm_review function in agent/curator.py was always resolving the model/provider from cfg['model'], ignoring any curator.auxiliary settings in config.yaml.

This caused the curator to always run on the user's main (often expensive) model even when curator.auxiliary was explicitly configured to use a cheaper auxiliary model.

Root Cause

Introduced by commit fa9383d ("feat(curator): umbrella-first prompt, inherit parent config"). The fix for an OpenRouter empty-credentials path replaced the curator.auxiliary read entirely instead of falling back to it.

Changes

• Read curator.auxiliary.provider and curator.auxiliary.model first
• Fall back to cfg['model'] only when curator.auxiliary is unset
• Preserves backward compatibility — existing configs without curator.auxiliary continue to work exactly as before

Verification

• Syntax check passes (python3 -m py_compile agent/curator.py)
• Tested locally with curator.auxiliary configured → curator now uses the configured auxiliary model
• Tested locally without curator.auxiliary → curator falls back to main model (previous behavior)

Fixes #17572

[alt-glitch]

Likely duplicate of #17868 (merged) — curator.auxiliary config resolution was already fixed and unified under the auxiliary.curator slot with CLI picker and deprecation-compatible fallback.

[alt-glitch]

Likely duplicate of #17868 (merged) — curator.auxiliary config resolution was already fixed and unified under the auxiliary.curator slot with CLI picker and deprecation-compatible fallback.

[alt-glitch]

Likely duplicate of #17868 (merged).

[alt-glitch]

Likely duplicate of #17868 (merged).

[teknium1]

Thanks for the fix @apcjoaofilho — unfortunately this was already resolved by PR #17868 ("fix(curator): unify under auxiliary.curator"), which landed a few weeks before your submission.

Current agent/curator.py has _resolve_review_model() (called by _run_llm_review()) reading in this precedence:

1. auxiliary.curator.{provider,model} (new unified location)
2. Legacy curator.auxiliary.{provider,model} (with a deprecation warning)
3. Fall back to cfg['model']

So the behavior you wanted — curator.auxiliary being honored over the main model — already works on main via the legacy-fallback path, plus there's a newer canonical location at auxiliary.curator now. Closing as redundant. Thanks for taking the time to write it up and include a clear root-cause note.