{"version":"2.1.273","anchor":"file-path-content-type-check-refactored-to-share-the-new-uns","canonical_anchor":"file-path-content-type-check-refactored-to-share-the-new-uns","heading":"file_path content-type check refactored to share the new unservable-file messaging","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/file-path-content-type-check-refactored-to-share-the-new-uns","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### file_path content-type check refactored to share the new unservable-file messaging\n\nThe error message shown when a file_path points to an unservable file type now shares common wording\n\n**Unclear.** The finding doesn't say whether the actual wording shown to users changed, only that it now routes through a shared builder.\n\n**What**\n\nWhen you give an artifact tool a `file_path` whose content type isn't recognized or servable, the error message is now built from a shared message helper instead of its own separate text.\n\n**Why**\n\nThis is an internal cleanup so the unservable-file error stays consistent wherever `file_path` is used, rather than drifting between separately maintained copies.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}