fix: warn when previously installed plugin disappears from discovery

jincheng-xydt · claude · jincheng-xydt · commit 35ae489b04f3 · 2026-06-19T22:26:57.000+08:00
When a plugin like Slack is externalized from bundled to npm, the upgrade path can silently drop it from the installed plugin index with no diagnostic output. Users only discover the issue when the channel stops working. Add a console.warn when a previously-installed plugin is no longer found in the current discovery results, including the previous path and a hint about plugins.allow. Fixes #91873 Co-Authored-By: Claude <noreply@anthropic.com>
diff --git a/src/plugins/installed-plugin-index-invalidation.ts b/src/plugins/installed-plugin-index-invalidation.ts
@@ -35,6 +35,16 @@ export function diffInstalledPluginIndexInvalidationReasons(
   for (const [pluginId, previousPlugin] of previousByPluginId) {
     const currentPlugin = currentByPluginId.get(pluginId);
     if (!currentPlugin) {
+      // A previously installed plugin is no longer in the discovery results.
+      // This can happen when a bundled plugin is externalized (e.g. Slack)
+      // or the plugin was uninstalled. Log a warning so users can diagnose
+      // the issue rather than discovering the plugin silently disappeared.
+      console.warn(
+        `plugin ${pluginId}: previously installed plugin not found in discovery ` +
+          `(previous path: ${previousPlugin.rootDir ?? "unknown"}). ` +
+          `If this was unexpected, check that the plugin is still installed and ` +
+          `configured in plugins.allow.`,
+      );
       reasons.add("source-changed");
       continue;
     }
