{"version":"2.1.280","anchor":"legacy-skills-manifest-repair-path-removed","canonical_anchor":"legacy-skills-manifest-repair-path-removed","heading":"Legacy skills manifest repair path removed","tier":"internal","area":"Skills","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/legacy-skills-manifest-repair-path-removed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Legacy skills manifest repair path removed\n\nSkills sync no longer repairs a malformed manifest with a legacy schema fallback; it now just fails\n\n**What**\n\nWhen syncing skills, if a manifest file failed to parse against the current schema, the code used to fall back to a legacy schema parser and repair the manifest, logging `skills_sync_legacy_manifest_repaired`. That repair path has been removed: a manifest that fails the current schema now simply returns `null` instead of being salvaged.\n\n**Why**\n\nA manifest that would previously have been silently patched up under the old format will now be treated as unreadable instead. This means older or malformed skills manifests may stop working where they used to be auto-repaired.\n\n- Area: Skills\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}