@punica/editor 1.39.0 → 1.40.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@punica/editor",
-  "version": "1.39.0",
+  "version": "1.40.0",
   "description": "Punica Editor",
   "private": false,
   "type": "module",
@@ -25,6 +25,7 @@
     "check:copy": "node scripts/check-marketplace-copy.mjs",
     "check:permissions": "node scripts/check-permissions.mjs",
     "check:empty-states": "node scripts/check-empty-states.mjs",
+    "check:card-shape": "node scripts/check-card-shape.mjs",
     "check:capability-handlers": "node scripts/check-capability-handlers.mjs",
     "check:duplicate-capabilities": "node scripts/check-duplicate-capabilities.mjs",
     "check:instruction-classes": "node scripts/check-instruction-classes.mjs",

package/types/punica.module.shell.profile.d.ts

@@ -163,10 +163,20 @@ declare module 'punica' {
          * during bootstrap. Kernel and runtime modules are always registered
          * unconditionally.
          *
-         * Structural DOM slots are derived from this list:
-         * - `shell.activityBar` → creates `activityBar` slot
-         * - `shell.view` → creates `primarySidebar` + `contentSidebar` slots
-         * - `shell.statusbar` → creates `statusbar` slot
+         * Structural DOM slots are derived from this list
+         * (`presentedSlots()` in `@punica/editor` is the one definition):
+         * - `shell.activityBar` → `activityBar`, `primarySidebar` and
+         *   `contentSidebar` — the strip is the only gesture that opens a
+         *   primary sidebar, and the content drawer is anchored beside it
+         *   (until 2026-09-26 the two sidebars followed `shell.view`, which
+         *   every profile activates for its helpers, so a window with no
+         *   strip got a sidebar nothing could open)
+         * - `shell.statusbar` → `statusbar`
+         *
+         * A view whose declared home slot the profile does not present is
+         * placed as a tab in the `content` slot, on demand — the extension
+         * analysis decorator applies that rule, so an extension never reads
+         * the profile.
          */
         activeModules: ShellModuleId[];
         /**

package/types/punica.module.shell.views.d.ts

@@ -12,6 +12,13 @@ declare module 'punica' {
      * agents and MCP clients all converge on them).
      */
     export namespace Views {
+      /**
+       * Where a view can be placed. `content` is never a manifest home: it is
+       * where a view lands when the active profile presents none of the slot
+       * its manifest names (`homeSlot` keeps the declared one), and a view
+       * placed there is a content tab, opened by a reveal and closed like a
+       * document.
+       */
       export type ViewSlotId =
         | 'primarySidebar'
         | 'secondarySidebar'