@punica/editor 1.6.21 → 1.7.0

package/package.json

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

package/types/punica.module.runtime.api.d.ts

@@ -87,9 +87,11 @@ declare module 'punica' {
       resources: ResourcesApi;
 
       /**
-       * Minimal in-memory secrets API.
+       * Secrets store (host-injected) plus `resolve()`, which asks the Secret
+       * Manager for a managed entry by name — the provider-routed read that
+       * substrate and host code must use for a real credential.
        */
-      secrets: SecretsApi;
+      secrets: SecretsFacade;
 
       /**
        * LLM provider interface. Hosts decide whether this is backed by local

package/types/punica.module.runtime.secrets.d.ts

@@ -9,10 +9,14 @@ declare module 'punica' {
     }
 
     /**
-     * Minimal secrets API (v1 MVP).
+     * The raw key→value store a host injects via
+     * `punica.runtime.setSecretsProvider(...)`.
      *
      * Notes:
-     * - In-memory only (no vault/persistence).
+     * - Synchronous, and keyed by whatever string the caller passes — it knows
+     *   nothing about the Secret Manager's names, providers or index.
+     * - A host that registers no provider gets an in-memory default, so the API
+     *   being present says nothing about persistence.
      * - Intended primarily for preventing secrets from leaking in trace exports
      *   and enabling simple { secretRef } resolution for capabilities.
      */
@@ -22,5 +26,25 @@ declare module 'punica' {
       delete(name: SecretName): boolean;
       list(): SecretRecord[];
     }
+
+    /**
+     * What `punica.runtime.secrets` actually is: the store above, plus the
+     * substrate-level resolution the store cannot do on its own.
+     *
+     * `resolve()` is not a second `get()`. `get()` takes a raw store key;
+     * `resolve()` takes a **Secret Manager entry name** and asks the Secret
+     * Manager for it, so a secret the user keeps in HashiCorp Vault resolves
+     * exactly like a local one. That round trip is async and goes through an
+     * extension, which is why it cannot live on the synchronous host-injected
+     * `SecretsApi`.
+     *
+     * Substrate and host code that needs a managed credential — MCP
+     * `${secret.NAME}` placeholders, the Electron renderer's remote-LLM token —
+     * must use this rather than reading the local provider's private value key.
+     * See `punica-editor/docs/secrets-contract.md`.
+     */
+    export interface SecretsFacade extends SecretsApi {
+      resolve(name: SecretName): Promise<string | null>;
+    }
   }
 }