{"version":"2.1.274","anchor":"extraction-swap-failure-path-now-distinguishes-a-superseded","canonical_anchor":"extraction-swap-failure-path-now-distinguishes-a-superseded","heading":"Extraction-swap failure path now distinguishes a superseded extraction from a genuine restore failure","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/extraction-swap-failure-path-now-distinguishes-a-superseded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Extraction-swap failure path now distinguishes a superseded extraction from a genuine restore failure\n\nFailed extraction restores now tell you if the backup was superseded rather than truly broken\n\n**What**\n\nClaude Code installs plugins and tools by swapping in a new \"extraction\" (an unpacked copy of the files) and moving the old one aside as a backup. If that swap fails and the code tries to restore the old backup, it now first checks whether a newer extraction has already been put in place. If so, it reports that a newer extraction is live and the backup was simply moved aside, instead of reporting a generic restore failure.\n\n**Why**\n\nThis prevents a confusing false alarm: previously any error thrown while restoring the backup was treated as \"could not restore,\" even when the real story was that a newer version had already taken over and restoring the old one wasn't needed or possible. The new message tells you what actually happened.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}