I measured fifty implementation runs across my two engines. One engine’s context window is about 258,000 tokens. The median run on the other engine peaked above that, and half of all runs peaked above the entire smaller window. A build routed into a window it does not fit is not a cheaper job, it is a failed one. It compacts, reorients, and a two hour build becomes a four day one. So the router now pins build sized runs to the larger window, and leaves quick and single stream work on ordinary routing. When I name a provider myself, that still wins. The pin is about window fit, not about which model is smarter.