Auto Router v6: what model: "auto" does behind AICraft's endpoint

Once a team contracts several AI APIs, the decision of which model to call spreads across the codebase, model-name changes break tests, and failover logic goes unwritten. Auto Router v6 is presented as an answer to that sprawl, and the piece is careful to say it is organizing what the documentation states and what response headers reveal rather than pitching the service.

The routing table is copied directly from that documentation, with the caveat that model lineups change and the Model Catalog's IDs should be checked before use. The v6 additions address a subtler issue — that a routing decision made once goes stale — through Lock Decay and Drift Detection, while Fault Self-Healing covers bypassing a failing model for 1 hour. The suggested adoption order is to start with auto, read the headers to see the classification and the model actually used, and pin model IDs only where output must be fixed.