{"version":"2.1.234","anchor":"plugin-manifest-errors-carry-a-machine-readable-class","canonical_anchor":"plugin-manifest-errors-carry-a-machine-readable-class","heading":"Plugin manifest errors carry a machine-readable class","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/plugin-manifest-errors-carry-a-machine-readable-class","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Plugin manifest errors carry a machine-readable class\n\nPlugin manifest errors now carry a code, so an invalid manifest is no longer reported as unverified identity.\n\n**What**\n\nManifest failures now attach one of `manifest_read_failed`, `manifest_json_invalid` or `manifest_schema_invalid`, and the plugin eval advisory pass reads that back to report `manifest_invalid` instead of lumping the case in with `identity_unverified`.\n\n**Evidence**\n\n`manifest_schema_invalid`\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}