🔧 Replacing Model Routes Behind One API Key Without Corrupting Node.js Classification Data

Treat every model change as a data migration: keep one application credential and one chat-completions-shaped boundary if that simplifies the Node.js service, but never let a routing decision overwrite a previously accepted classification without a versioned schema, provenance, and an explicit promotion rule.

That is the short answer. Replacing...