{"version":"2.1.225","anchor":"classifier-unavailable-denial-message-shortened-via-shared-f","canonical_anchor":"classifier-unavailable-denial-message-shortened-via-shared-f","heading":"Classifier-unavailable denial message shortened via shared fragments","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/classifier-unavailable-denial-message-shortened-via-shared-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Classifier-unavailable denial message shortened via shared fragments\n\nThe \"temporarily unavailable\" denial message is shorter and no longer shows HTTP status details.\n\n**What**\n\nThe \"temporarily unavailable\" denial text in auto mode now ends with two shared constants rather than inline prose, and the same fragments are reused by the new safeguard-refusal message.\n\n**Details**\n\n- The fragments are \"If it keeps failing, continue with other tasks that don't require this action and come back to it later.\" and \"Note: reading files, searching code, and other read-only operations do not require the classifier and can still be used.\"\n- The helper that produced HTTP status and error-kind detail now returns the empty string, so status details no longer appear in either message.\n\n**Evidence**\n\n`Note: reading files, searching code, and other read-only operations do not require the classifier and can still be used.`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}