@punica/editor 1.10.4 → 1.10.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@punica/editor",
-  "version": "1.10.4",
+  "version": "1.10.6",
   "description": "Punica Editor",
   "private": false,
   "type": "module",

package/types/punica.module.kernel.ai.d.ts

@@ -277,9 +277,26 @@ declare module 'punica' {
         deferToolLoading?: boolean;
         /**
          * Size of the fully-loaded hot set when deferred loading is
-         * active (meta-tools not counted). Default ~16.
+         * active (meta-tools not counted). Default 40.
          */
         hotSetSize?: number;
+        /**
+         * Capability ids guaranteed a place in the hot set, whatever the
+         * intent ranking says. Exact ids only — no globs, so the substrate
+         * needs no matcher and the field stays a plain set union.
+         *
+         * This is where a product declares its staples: the handful of tools
+         * an assistant is expected to reach for in almost any request (open a
+         * file, search, read, write). Ranking is a guess about THIS request;
+         * pinning is knowledge about the product, and the substrate has none
+         * of the latter — it hardcodes no ids and ships no default list.
+         *
+         * Pinned ids are seated first and COUNT against `hotSetSize`, so
+         * pinning cannot silently widen the request's tool budget. Ids that
+         * are not in the catalog (extension not installed, filtered by the
+         * profile budget) are ignored rather than faked.
+         */
+        pinnedTools?: string[];
         /**
          * Prepend a one-shot workspace orientation (the
          * `workspace.projectContext` snapshot: stack, dependencies, run

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

@@ -101,6 +101,43 @@ declare module 'punica' {
         allowedOrigins?: CapabilityOrigin[];
       }
 
+      /**
+       * Tool selection budget — how many capabilities the agent SEES.
+       *
+       * Not a permission surface. What may be called stays with
+       * `ProfileCapabilityBudget` and the gateway's policy stages; this only
+       * decides how many tools travel with full schemas versus as one-line
+       * index entries. Widening it cannot grant a profile anything its
+       * capability budget denies.
+       *
+       * Every field is optional: the substrate boots headless with no profile
+       * at all, so the kernel owns working defaults and a profile only states
+       * where it wants to differ.
+       */
+      interface ProfileToolSelectionSpec {
+        /** Above this many capabilities the catalog is narrowed by intent. */
+        narrowThreshold?: number;
+        /** Ceiling on the narrowed catalog. */
+        catalogTopN?: number;
+        /** How many id-namespace categories survive narrowing, kept whole. */
+        topCategories?: number;
+        /** Tools shipped with full schemas (meta-tools not counted). */
+        hotSetSize?: number;
+        /**
+         * Slots one category may take in the hot set before the fill moves on.
+         * Omitted ⇒ derived from `hotSetSize`. Stops one large namespace from
+         * consuming the whole hot set.
+         */
+        perCategoryCap?: number;
+        /** How many ranked ids to request from the recommender. */
+        rankLimit?: number;
+      }
+
+      /** Agent-facing profile dimension. */
+      interface ProfileAgentSpec {
+        toolSelection?: ProfileToolSelectionSpec;
+      }
+
       /** Layout sub-spec embedded in the profile's shell spec. */
       interface ProfileLayoutSpec {
         /**
@@ -254,6 +291,7 @@ declare module 'punica' {
 
         // ── v1 optional dimensions (shape declared, not enforced at runtime) ─
         extensions?: ProfileExtensionsSpec;
+        agent?: ProfileAgentSpec;
         commandPalette?: ProfileCommandPaletteSpec;
         authoring?: ProfileAuthoringSpec;
         telemetry?: ProfileTelemetrySpec;

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

@@ -169,7 +169,18 @@ declare module 'punica' {
             | 'caption'
             | 'overline';
           color?: 'primary' | 'secondary' | 'error';
-          fontWeight?: 'normal' | 'bold';
+          /**
+           * The six weights `punica-typography` ships a rule for. `normal` was
+           * never one of them, so it resolved to no rule at all; `regular` is
+           * the component's spelling for the same intent.
+           */
+          fontWeight?:
+            | 'thin'
+            | 'regular'
+            | 'medium'
+            | 'semi-bold'
+            | 'bold'
+            | 'extra-bold';
           style?: Record<string, string> | string;
           className?: string;
           attrs?: Record<string, string>;