{"version":"2.1.257","anchor":"some-legacy-artifact-actions-explicitly-disabled-with-tailor","canonical_anchor":"some-legacy-artifact-actions-explicitly-disabled-with-tailor","heading":"Some legacy artifact actions explicitly disabled with tailored error messages","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/some-legacy-artifact-actions-explicitly-disabled-with-tailor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Some legacy artifact actions explicitly disabled with tailored error messages\n\nLegacy artifact actions with no new equivalent now return a tailored explanation instead of quietly failing.\n\nWhen a legacy-shaped artifact call names an action that no longer maps 1:1 onto the new schema, such as whole-artifact delete, `read_asset`, `delete_asset`, `read_file`, or `describe_type`, the tool now returns a specific explanatory error instead of silently failing. For example, it explains that `delete` now only removes one uploaded asset by id, and that `describe_type` only creates a new Artifact from a type rather than reading its details.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}