docs(sdk): plugin minimal en dossier + hot reload documentés — manifest (arborescence minimale idea-plugin.json/package.json/tsconfig/src/dist, install depuis dossier), packaging-distribution (procédure hot reload directory install + idea_plugin_reload + limites UI React), README (lien packaging hot reload)

docs/manifest.md

@@ -2,6 +2,103 @@
 
 Every plugin package has an `idea-plugin.json` file at the archive root.
 
+For development installs, the same file must exist at the root of the plugin
+source directory selected in IdeA with `Paramètres > Plugins > Installer depuis
+un dossier…`.
+
+## Minimal Plugin Directory
+
+A plugin directory must contain the manifest at its root and a built ESM
+entrypoint matching the manifest `main` field.
+
+```text
+my-plugin/
+├── idea-plugin.json
+├── package.json
+├── tsconfig.json
+├── src/
+│   └── index.ts
+└── dist/
+    └── index.js
+```
+
+Create the directory:
+
+```sh
+mkdir -p my-plugin/src
+cd my-plugin
+npm init -y
+npm install --save-dev typescript @idea/plugin-sdk
+```
+
+Use a package script that emits JavaScript into `dist/`:
+
+```json
+{
+  "type": "module",
+  "scripts": {
+    "build": "tsc -p tsconfig.json"
+  },
+  "devDependencies": {
+    "@idea/plugin-sdk": "^0.3.0",
+    "typescript": "^5.0.0"
+  }
+}
+```
+
+When developing against a local SDK checkout instead of a published package,
+replace the SDK dependency with a `file:` reference, for example:
+
+```json
+{
+  "devDependencies": {
+    "@idea/plugin-sdk": "file:../IdeaSDK",
+    "typescript": "^5.0.0"
+  }
+}
+```
+
+Minimal `tsconfig.json`:
+
+```json
+{
+  "compilerOptions": {
+    "target": "ES2022",
+    "module": "NodeNext",
+    "moduleResolution": "NodeNext",
+    "outDir": "dist",
+    "rootDir": "src",
+    "strict": true
+  },
+  "include": ["src"]
+}
+```
+
+Minimal `src/index.ts`:
+
+```ts
+import type { IdeAPluginModule } from "@idea/plugin-sdk";
+
+const plugin: IdeAPluginModule = {
+  activate(ctx) {
+    ctx.logger.info("plugin activated", { pluginId: ctx.pluginId });
+  }
+};
+
+export default plugin;
+```
+
+Build before installing or reloading:
+
+```sh
+npm run build
+```
+
+Then install the `my-plugin/` directory in IdeA. For hot reload, keep installing
+from the directory, rebuild after source changes, then run `idea_plugin_reload`
+for the installed plugin id. Do not install from a ZIP archive for a hot-reload
+development loop.
+
 ```json
 {
   "ideaPluginManifestVersion": 1,

docs/packaging-distribution.md

@@ -74,3 +74,55 @@ npm run package:hello-plugin
 
 The resulting archive has no wrapping parent directory and is ready for IdeA's
 plugin installer.
+
+## Hot Reload During Development
+
+Install the plugin from a directory when you want IdeA to hot-reload changes
+without restarting the app.
+
+In IdeA, open `Paramètres > Plugins`, choose `Installer depuis un dossier…`,
+and select the plugin source directory. That directory must contain
+`idea-plugin.json` at its root, and the manifest `main` field must point to the
+built entrypoint that exists inside the same directory, for example
+`dist/index.js`.
+
+```text
+hello-plugin/
+├── idea-plugin.json
+├── package.json
+└── dist/
+    ├── index.js
+    └── core/
+        └── layout.js
+```
+
+After editing plugin source files, rebuild the plugin output first:
+
+```sh
+npm run build
+```
+
+Then ask an IdeA agent that has the plugin administration tool available to run
+`idea_plugin_reload` with the installed plugin id:
+
+```json
+{
+  "pluginId": "com.example.hello-plugin"
+}
+```
+
+The reload uses the recorded directory source from the plugin registry. It
+re-reads and validates the manifest, recalculates the package hash, updates the
+installed package, emits `plugin_reloaded`, and reconciles plugin MCP servers.
+It does not accept an arbitrary path at reload time; install from the intended
+development directory first.
+
+Do not install from the ZIP archive for a development loop that needs hot
+reload. Archive installs are fixed package snapshots. They are appropriate for
+distribution, but the reload command is only defined for plugins installed from
+a directory source.
+
+Current limitation: backend registry state and plugin MCP/tool contributions are
+reloaded without restarting IdeA. Frontend React contributions that are already
+loaded in the current UI session may keep their existing module instance until
+the relevant plugin surface is recreated or the app session is restarted.