{"version":"2.1.257","anchor":"model-consent-fallback-event-now-records-original-models-di","canonical_anchor":"model-consent-fallback-event-now-records-original-models-di","heading":"Model consent fallback event now records original model's display name","tier":"internal","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/model-consent-fallback-event-now-records-original-models-di","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Model consent fallback event now records original model's display name\n\nModel-consent fallback telemetry and the usage-credit swap schema now carry the original model's display name.\n\nThe telemetry payload for the model-consent-fallback flow now includes `original_model_name` alongside the existing model id, giving clearer logging of what model a user was switched away from. The usage-credit swap schema also gained `original_model_name`, an optional string a host can show in its own notice instead of the CLI's generic copy (which otherwise names the original model \"Fable 5\", falling back to \"Fable\" when absent).\n\n- Area: Models\n- Names: `original_model_name`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}