Improving recipe quality with multi-model routing

Different Friji tasks need different response shapes, so a single-model approach was no longer the right tradeoff for both latency and answer quality.

We reclassified the main paths such as inventory analysis, substitution suggestions, and recipe generation, then routed each class to the strongest model for that job.

The result was more consistent output quality and faster first responses on the user side without changing the overall product flow.