{"version":"2.1.222","anchor":"telemetry-model-name-sanitizer-accepts-a-bracketed-context-s","canonical_anchor":"telemetry-model-name-sanitizer-accepts-a-bracketed-context-s","heading":"Telemetry model-name sanitizer accepts a bracketed context suffix","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/telemetry-model-name-sanitizer-accepts-a-bracketed-context-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Telemetry model-name sanitizer accepts a bracketed context suffix\n\nTelemetry now records long-context model names properly instead of labelling them nonconforming.\n\n**What**\n\nDated model ids that carry a 1m-context suffix are now reported verbatim in telemetry instead of being replaced with \"nonconforming\".\n\n**Details**\n\n- The gate regex widened from `^[A-Za-z0-9._:[\\]-]{1,91}@\\d{8}$` to allow an optional trailing `[<digits>m]` group\n- Model identifiers that still fail the pattern continue to report as \"nonconforming\"\n\n**Evidence**\n\n`nonconforming`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}