Problem
When a model is deprecated or approaching sunset, users get no warning from Hermes. They discover it only when the API starts returning errors. The models.dev integration already has a status field that can be "deprecated" but nothing reads it for warnings.
Proposed Solution
In the model capability pre-flight (if merged) or during AIAgent init, check the models.dev status field. If the model is marked deprecated, emit a warning via _vprint. Low effort — the data source already exists.
Problem
When a model is deprecated or approaching sunset, users get no warning from Hermes. They discover it only when the API starts returning errors. The models.dev integration already has a
statusfield that can be "deprecated" but nothing reads it for warnings.Proposed Solution
In the model capability pre-flight (if merged) or during AIAgent init, check the models.dev status field. If the model is marked deprecated, emit a warning via
_vprint. Low effort — the data source already exists.