0.9.108

bootstrap.ts runs the calling script again in a new Bun process after it installs commander, as upstream's does. The port had dropped that step in 0.9.23, so the first run after each plugin update imported commander in the process that had just installed it. Bun did not find the new node_modules, and the run failed with Cannot find package 'commander' unless Bun's auto-install fetched the package from the registry. The failure reproduced on macOS and Windows 11 with Bun 1.4.4 under bun --no-install. watch-pr/fresh-install.test.ts runs each entry point that way from a copy of the scripts with no node_modules. #326, filed by @Thanaen, found the cause.