Found in the VM test: adopt refused events@2.2.0 because the AI tokens migration made it into the release, and adopt only moved installs with no migrations. Now the migrations the release has and the old install doesn't run after the backup, while neither version runs; a failure starts the old install again. They're recorded (EVENTS_ADOPT_MIGRATIONS) so adopt --undo can still go back past them (they only add columns). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>