Merge main into addJSKernel

Author: MUFFANUJ

README.md

@@ -7,9 +7,11 @@
 
 | Try in your browser   | Lab                                                                                                                                                       | Notebook v7                                                                                                                                                            |
 | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Binder (Powerful)     | [![Binder](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/jupyterlab/plugin-playground/main?urlpath=lab)                                | [![Binder Notebook v7](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/jupyterlab/plugin-playground/main?urlpath=tree)                                |
+| Binder (Powerful)     | [![Binder](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/jupyterlab/plugin-playground/binder-stable?urlpath=lab)                       | [![Binder Notebook v7](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/jupyterlab/plugin-playground/binder-stable?urlpath=tree)                       |
 | JupyterLite (Instant) | [![JupyterLite](https://jupyterlite.rtfd.io/en/latest/_static/badge-launch.svg)](https://jupyterlab-plugin-playground.readthedocs.io/en/latest/lite/lab/) | [![JupyterLite Notebook v7](https://jupyterlite.rtfd.io/en/latest/_static/badge-launch.svg)](https://jupyterlab-plugin-playground.readthedocs.io/en/latest/lite/tree/) |
 
+<!-- Binder links above are intentionally pointed at the `binder-stable` branch with pinned Binder dependencies; update that branch only after validating Binder builds. -->
+
 A JupyterLab extension to write and load simple JupyterLab plugins inside JupyterLab.
 
 ## Install
@@ -30,7 +32,7 @@ Plugin Playground is built to keep the full plugin prototyping workflow inside J
 ![Export format dropdown in editor toolbar](docs/images/readme/editor-toolbar-export-dropdown.png)
 ![Share target dropdown in editor toolbar](docs/images/readme/editor-toolbar-share-dropdown.png)
 
-The right sidebar includes a single Plugin Playground panel with two collapsible sections. In **Extension Points**, the `Tokens` tab helps you discover available token strings and insert import/dependency updates, the `Commands` tab lets you search command IDs, inspect argument docs, and insert execution snippets (either directly or through AI-assisted prompt mode), and the `Packages` tab surfaces package docs plus npm and repository links for known modules.
+The right sidebar includes a single Plugin Playground panel with three collapsible sections. In **Extension Points**, the `Tokens` tab helps you discover available token strings and insert import/dependency updates, the `Commands` tab lets you search command IDs, inspect argument docs, and insert execution snippets (either directly or through AI-assisted prompt mode), and the `Packages` tab surfaces package docs plus npm and repository links for known modules.
 
 ![Extension Points token discovery and insertion actions](docs/images/readme/extension-points-tokens.png)
 ![Extension Points command discovery and insertion actions](docs/images/readme/extension-points-commands.png)
@@ -40,6 +42,8 @@ The **Extension Examples** section lists discovered examples from `extension-exa
 
 ![Extension Examples section with code and README actions](docs/images/readme/extension-examples.png)
 
+The **Currently Loaded Plugins** section lists plugins loaded by Plugin Playground in the current session, shows each plugin's source path, and lets you deactivate a selected plugin without clearing the rest of the session.
+
 Command completion is also included for `app.commands.execute(...)` / `commands.execute(...)` in JavaScript and TypeScript editors, and Notebook v7 integrates `Start from File`, `Build with AI`, and `Take the Tour` into New-file flows so you can create starter plugin files from the tree interface.
 
 The Launcher `Plugin Playground` section includes `Start from File`, `Build with AI`, and `Take the Tour` so first-time users can pick a guided flow quickly.
@@ -59,7 +63,7 @@ jlpm docs:screenshots
 3. Paste plugin code into the active editor.
 4. Run `Load Current File As Extension` from the editor toolbar or Command Palette.
 5. Use the `Run on save` icon button for fast iteration on one file.
-6. Use the sidebar to discover tokens, commands, packages, and extension examples.
+6. Use the sidebar to discover tokens, commands, packages, extension examples, and currently loaded playground plugins.
 
 For extension examples availability:
 
@@ -136,6 +140,8 @@ There are a few differences in how to write plugins in Plugin Playground compare
 - To load code from an external package, RequireJS is used (hidden behind ES module-compatible import syntax), so import statements may need explicit version or file paths.
   - In addition to JupyterLab and Lumino packages, only AMD modules can be imported; ES modules and modules compiled for Webpack/Node are not supported directly and can fail with `Uncaught SyntaxError: Unexpected token 'export'`.
 - The playground can import relative files (`.ts`, `.tsx`, `.js`, and `.css`), load SVG as strings, and load settings schema from `package.json` (`jupyterlab.schemaDir`) with `plugin.json` fallback for single-plugin prototyping.
+- For multi-file prototypes, create a package root with `package.json` before adding files under `src/`, `schema/`, or `style/`. This lets `Share Package` and extension export find the whole plugin folder reliably.
+- Playground prototypes cannot replace existing JupyterLab commands by reusing their command IDs. Register your own command ID and add it to the relevant menu, toolbar, launcher, palette, or cell toolbar instead.
 
 ### Migrating from version 0.3.0
 
@@ -172,6 +178,10 @@ Plugin Playground supports AI-assisted extension prototyping in both JupyterLite
 - [JupyterLite AI documentation](https://jupyterlite-ai.readthedocs.io/en/latest/)
 - [Plugin authoring skill for agents](_agents/skills/plugin-authoring/SKILL.md)
 
+### JS Logs Ask AI
+
+Plugin Playground adds an `Ask AI` button to JS Logs entries so you can send error text to JupyterLite AI chat for debugging context. The button appears only on `error`/`critical` entries that include text content, and only when JupyterLite AI is available and a provider is configured.
+
 ### Command Insert Modes (Default + AI Prompt)
 
 In the `Commands` tab, each command row includes a split `+` action and a mode dropdown:

_agents/skills/plugin-authoring/SKILL.md

@@ -37,8 +37,23 @@ Produce working plugin code that can be loaded with `plugin-playground:load-as-e
 - If the user does not already have a plugin file open or specified, run `plugin-playground:create-new-plugin` with a meaningful `path` argument (for example `app.commands.execute('plugin-playground:create-new-plugin', { path: 'status-indicator.ts' })`) instead of relying on untitled defaults.
 - Start from the generated TypeScript scaffold and adapt it.
 - Plugin Playground supports schema-backed settings during prototyping (`package.json` with `jupyterlab.schemaDir`, with `plugin.json` fallback for single-plugin cases).
+- For any plugin with multiple files, settings schema, CSS, SVG, or other local assets, create a package root up front (for example `my-extension/src/index.ts`) and include a minimal `package.json` in `my-extension/` so `Share Package` and extension export operate on the full folder.
+- When creating nested files through AI file commands, create the parent directories first and verify the files appear in the file browser before continuing.
 - Focus on TypeScript/TSX plugin code. Do not scaffold Python projects (`pyproject.toml`, Python package layout) unless explicitly requested.
 
+Minimal package metadata for Playground prototypes:
+
+```json
+{
+  "name": "my-extension",
+  "version": "0.1.0",
+  "jupyterlab": {
+    "extension": true,
+    "schemaDir": "schema"
+  }
+}
+```
+
 2. Discover available extension points
 
 - Run `plugin-playground:list-tokens` to get available tokens.
@@ -57,7 +72,8 @@ Produce working plugin code that can be loaded with `plugin-playground:load-as-e
 
 - Start from a minimal plugin shape (`id`, `autoStart`, `activate`).
 - Add `requires` tokens only after confirming availability from step 2.
-- Add commands with stable IDs (`<namespace>:<action>`).
+- Add commands with stable, unique IDs (`<namespace>:<action>`).
+- Do not overwrite or reuse built-in JupyterLab command IDs. Plugin Playground skips duplicate command registrations; register a separate command and add it to the relevant palette, menu, toolbar, launcher, or cell toolbar instead.
 - Use one or more `.ts`/`.tsx` files as needed as complexity grows.
 
 5. Load and iterate

binder/environment.yml

@@ -21,7 +21,7 @@ dependencies:
   # additional packages for demos
   # - ipywidgets
   - jupyterlab-lsp
-  - jupyterlab-js-logs>=1.2,<2
+  - jupyterlab-js-logs>=1.3.1,<2
   - jupyterlab-tour>=4,<5
   # use the same AI package in Binder and JupyterLite deployments
   - jupyterlite-ai>=0.15,<1

docs/environment.yml

@@ -11,7 +11,7 @@ dependencies:
   - ipywidgets>=8.0,<9
   - jupyterlab>=4.0.0,<5
   - jupyterlab-lsp>=5.2.0,<6
-  - jupyterlab-js-logs>=1.2,<2
+  - jupyterlab-js-logs>=1.3.1,<2
   - jupyterlab-tour>=4,<5
   - jupyterlab-language-pack-fr-FR
   - jupyterlab-language-pack-zh-CN

package.json

@@ -70,7 +70,7 @@
         "@jupyterlab/lsp": "^4.5.5",
         "@jupyterlab/settingregistry": "^4.5.5",
         "@typescript/vfs": "^1.6.4",
-        "jupyterlab-js-logs": "^1.2.0",
+        "jupyterlab-js-logs": "^1.3.1",
         "raw-loader": "^4.0.2",
         "requirejs": "^2.3.6",
         "semver": "^7.7.4",
@@ -138,15 +138,18 @@
         "extension": true,
         "outputDir": "jupyterlab_plugin_playground/labextension",
         "schemaDir": "schema",
-        "disabledExtensions": [
-            "jupyterlab-tour:default-tours"
-        ],
         "sharedPackages": {
             "@jupyterlab/lsp": {
                 "bundled": false,
                 "singleton": true,
                 "strictVersion": false
+            },
+            "jupyterlab-js-logs": {
+                "singleton": true
             }
-        }
+        },
+        "disabledExtensions": [
+            "jupyterlab-tour:default-tours"
+        ]
     }
 }

src/contents.ts

@@ -62,7 +62,7 @@ export namespace ContentUtils {
   };
 
   export type IFileModel = Contents.IModel & {
-    type: 'file';
+    type: 'file' | 'notebook';
     content: unknown;
     format?: string | null;
   };
@@ -194,23 +194,27 @@ export namespace ContentUtils {
       const model = await getContentsModel(serviceManager, candidatePath, {
         content: true
       });
-      if (!model || model.type !== 'file') {
+      if (!model || (model.type !== 'file' && model.type !== 'notebook')) {
         continue;
       }
       if (model.content !== null) {
         return model as IFileModel;
       }
 
-      const textModel = await getContentsModel(serviceManager, candidatePath, {
-        content: true,
-        format: 'text'
-      });
+      const fallbackModel = await getContentsModel(
+        serviceManager,
+        candidatePath,
+        {
+          content: true,
+          format: model.type === 'notebook' ? 'json' : 'text'
+        }
+      );
       if (
-        textModel &&
-        textModel.type === 'file' &&
-        textModel.content !== null
+        fallbackModel &&
+        (fallbackModel.type === 'file' || fallbackModel.type === 'notebook') &&
+        fallbackModel.content !== null
       ) {
-        return textModel as IFileModel;
+        return fallbackModel as IFileModel;
       }
     }
     return null;