@north-light/crouter 0.3.186 → 0.3.187

package/dist/types.d.ts

@@ -33,7 +33,18 @@ export interface PluginManifest {
     description?: string;
     source?: string;
     owner?: OwnerRef;
-    kinds?: string[];
+    /** Kind-registry contributions, keyed by full kind string (top-level e.g.
+     *  `applet-builder`, or sub-kind e.g. `plan/reviewers/security`). Each entry
+     *  is either a FULL `KindConfig` (has `whenToUse`: defines or wholly shadows
+     *  the kind) or a sparse PATCH over a kind a lower layer already defines —
+     *  the same two shapes a scope `config.json` `kinds` block accepts.
+     *  `readMergedLaunchConfig` layers an enabled plugin's entries directly
+     *  above the builtin registry and below its host scope's own `config.json`,
+     *  so a plugin can ship a persona kind (registry entry here + gated persona
+     *  memory docs in its `memory/` tree) and the user still overrides it.
+     *  Archive plugins declare this in `bundle.json`; the installer copies the
+     *  validated block into this synthesized manifest. */
+    kinds?: Record<string, Partial<KindConfig>>;
     /** Plugin-root-relative path to one declarative command manifest
      *  (`commands.json`). When present on an installed, enabled plugin, that
      *  manifest contributes top-level command branches to the `crtr` tree —

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@north-light/crouter",
-  "version": "0.3.186",
+  "version": "0.3.187",
   "description": "crtr — agent runtime with memory, plugins, and marketplaces",
   "type": "module",
   "main": "dist/index.js",

package/runtime.lock.json

@@ -1,12 +1,12 @@
 {
   "name": "@north-light/crouter",
-  "version": "0.3.186",
+  "version": "0.3.187",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@north-light/crouter",
-      "version": "0.3.186",
+      "version": "0.3.187",
       "hasInstallScript": true,
       "license": "MIT",
       "dependencies": {