pi-harness-runtime 1.1.387 → 1.1.388

package/AGENTS.md

@@ -502,16 +502,21 @@ bun run build && bun run start   # Server deployment
 
 **This info is shown in UI and delivered to agent context:**
 ```
-Workspace: DEV | dev server: running | build: explicit request only | RAM: 10/16
+Workspace: DEVELOPMENT | dev server: running | build: not running (script available) | RAM: 10/16
 ```
 
+The mode words are exactly what the detector emits: `DEVELOPMENT`, `PRODUCTION`,
+`TEST` or `UNKNOWN` (with its reason, e.g. `UNKNOWN (no explicit NODE_ENV)`).
+A dev/build script is a CAPABILITY, not a state: `not running (script available)`
+means the script exists, not that a server runs.
+
 **IMPORTANT Rules:**
 
 | State | Action |
 |-------|--------|
-| `Workspace: UNKNOWN` | Explicitly ask user before build |
-| `Workspace: DEV` | Use `dev` mode, don't auto-build |
-| `Workspace: PROD` | Build allowed, but confirm with user |
+| `Workspace: UNKNOWN (…)` | Explicitly ask user before build |
+| `Workspace: DEVELOPMENT` | Use `dev` mode, don't auto-build |
+| `Workspace: PRODUCTION` | Build allowed, but confirm with user |
 | `Low RAM` | Never run parallel build + dev |
 | `Dev server running` | Reuse it, don't restart |
 

package/index.ts

@@ -58,6 +58,7 @@ import { aggregateWindows } from "./windows.ts";
 // Relay client for streaming callbacks (t3code-style two-way communication)
 import { RelayClient } from "./packages/relay/src/client.js";
 import type { CallbackPayload } from "./packages/relay/src/types.js";
+import { describeRelayEndpoint, resolveRelayEndpoint } from "./packages/relay/src/relay-endpoint.js";
 import { renderStatus } from "./renderer.ts";
 import {
 	JobStateMachine,
@@ -1559,32 +1560,33 @@ function setRelayTelegramAdapter(adapter: any) {
  * to the adapter for proper greeting verification and handling.
  */
 async function initRelayStream(): Promise<void> {
-	const homedir = process.env.HOME || process.env.USERPROFILE || "/home/frappe";
-	const keysDir = join(homedir, ".pi-harness-runtime", "keys");
-
-	// Check for relay WebSocket URL
-	const relayWsUrlPath = join(keysDir, "relay-ws-url.txt");
-	const relayTokenPath = join(keysDir, "relay-auth-token.txt");
+	// Use the OS home directory - the relay server resolves its key files
+	// the same way, so both sides always look in the same place.
+	const keysDir = join(homedir(), ".pi-harness-runtime", "keys");
 
-	if (!existsSync(relayWsUrlPath) || !existsSync(relayTokenPath)) {
-		logToFile("[RelayStream]", "Relay WebSocket URL or token not configured - skipping streaming");
-		return;
-	}
+	// Resolve the relay endpoint from the SAME sources the relay server uses
+	// (env -> dedicated key file -> the telegram webhook url/secret), so the
+	// client and the server always agree on the URL and the token.
+	// The token value is never logged - only the source it came from.
+	const endpoint = resolveRelayEndpoint({ keysDir });
 
-	const relayWsUrl = readFileSync(relayWsUrlPath, "utf-8").trim();
-	const relayToken = readFileSync(relayTokenPath, "utf-8").trim();
-
-	if (!relayWsUrl || !relayToken) {
-		logToFile("[RelayStream]", "Relay URL or token is empty - skipping streaming");
+	if (!endpoint.url || !endpoint.token) {
+		logToFile(
+			"[RelayStream]",
+			`Relay endpoint not configured - skipping streaming (${endpoint.missing.join("; ")})`,
+		);
 		return;
 	}
 
-	logToFile("[RelayStream]", `Connecting to relay at ${relayWsUrl}`);
+	logToFile(
+		"[RelayStream]",
+		`Connecting to relay at ${endpoint.url} (${describeRelayEndpoint(endpoint)})`,
+	);
 
 	_relayClient = new RelayClient(
 		{
-			serverUrl: relayWsUrl,
-			token: relayToken,
+			serverUrl: endpoint.url,
+			token: endpoint.token,
 			// Keep retrying in the background: the relay server may not be up
 			// yet when the harness starts.
 			retryOnConnectFailure: true,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-harness-runtime",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "description": "[BETA] Codex-style /usage status + autonomous coding harness for pi. Not production ready — expect breaking changes.",
   "type": "module",
   "scripts": {

package/packages/a2a-adapter/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi/a2a-adapter",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "type": "module",
   "description": "Google Agent-to-Agent (A2A) protocol adapter for pi-harness",
   "main": "dist/index.js",

package/packages/agent-policy/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi/agent-policy",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "description": "Agent policy runtime for pi-harness - enforces mandatory rule delivery and mutation gating",
   "type": "module",
   "main": "./dist/index.js",

package/packages/architecture-generator/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi-harness/architecture-generator",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "description": "Generate ADR and Mermaid diagrams from project analysis",
   "type": "module",
   "main": "./dist/index.js",

package/packages/auth/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi-harness/auth",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "description": "pi-harness-runtime — auth",
   "type": "module",
   "main": "./dist/index.js",

package/packages/autonomous-refactor/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi/autonomous-refactor",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "type": "module",
   "description": "Autonomous refactoring engine",
   "main": "dist/index.js",

package/packages/autonomous-runtime/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi/autonomous-runtime",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "description": "Autonomous Operations Runtime — task inbox, lease management, and worker lifecycle (RFC-0101)",
   "type": "module",
   "main": "./dist/index.js",

package/packages/cache-strategy/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi/cache-strategy",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "type": "module",
   "description": "Smart caching with TTL and invalidation strategies (RFC-0022)",
   "main": "dist/index.js",

package/packages/capability-registry/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi-harness/capability-registry",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "description": "Capability Registry for pi-harness-runtime — tracks model capabilities and enables capability-based routing",
   "type": "module",
   "main": "./dist/index.js",

package/packages/checkpoint/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi/checkpoint",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "description": "Enhanced checkpoint system with incremental snapshots, diff-based storage, and recovery strategies",
   "type": "module",
   "main": "./dist/index.js",

package/packages/cli-plugin-sdk/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi/cli-plugin-sdk",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "type": "module",
   "description": "CLI Plugin SDK for pi-harness — install, list, remove, update, invoke plugins",
   "main": "dist/index.js",

package/packages/clipboard/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi/clipboard",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "type": "module",
   "main": "src/index.ts",
   "exports": {

package/packages/clipboard-plugin/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi/clipboard-plugin",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "type": "module",
   "main": "src/index.ts",
   "exports": {

package/packages/code-generation/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi/code-generation",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "description": "Code generation pipeline for pi-harness-runtime",
   "type": "module",
   "main": "./dist/index.js",

package/packages/code-review/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi/code-review",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "description": "Automated code review engine for pi-harness-runtime",
   "type": "module",
   "main": "./dist/index.js",

package/packages/codex-adapter/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi/codex-adapter",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "type": "module",
   "description": "OpenAI Codex provider adapter for pi-harness",
   "main": "dist/index.js",

package/packages/codex-watcher/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi-harness/codex-watcher",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "description": "Watches Codex CLI sessions and emits visible messages for PING-PONG monitoring",
   "type": "module",
   "main": "./dist/src/index.js",

package/packages/config-capture/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@moocoding/config-capture",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "description": "Auto-capture API-fetched configuration values to AGENTS.md",
   "type": "module",
   "main": "src/index.ts",

package/packages/connection-runtime/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi-harness/connection-runtime",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "type": "module",
   "description": "Connection management with jittered exponential backoff for pi-harness",
   "main": "./dist/index.js",

package/packages/context-compiler/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi/context-compiler",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "description": "Bounded context selection engine for pi-harness-runtime",
   "type": "module",
   "main": "./dist/index.js",

package/packages/context-discovery/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi/context-discovery",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "type": "module",
   "main": "src/index.ts",
   "exports": {

package/packages/context-manager/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi-harness/context-manager",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "description": "Context Window Manager — prevents model context overflow via compaction and resume prompts (RFC-0010)",
   "type": "module",
   "main": "./dist/index.js",

package/packages/contracts/dist/workspace-env-format.d.ts

@@ -0,0 +1,71 @@
+/**
+ * Workspace environment formatting helpers.
+ *
+ * Split out of workspace-env.ts so the wording can be unit tested without the
+ * node:sqlite dependency (bun 1.3.x has no node:sqlite module).
+ *
+ * Wording rules:
+ * - The mode is only reported when it is EXPLICIT (NODE_ENV). An unknown mode
+ *   is always shown with its reason, never as a bare word next to a dev
+ *   server state that could be read as proof of the mode.
+ * - A dev/build script is a CAPABILITY, not a state. The status line says
+ *   "not running (script available)" so it cannot be mistaken for a running
+ *   server or for evidence about the workspace mode.
+ */
+/**
+ * Workspace mode with explicit states
+ */
+export type WorkspaceMode = "development" | "production" | "test" | "unknown";
+/**
+ * Evidence source for mode detection
+ */
+export interface EnvEvidence {
+    source: "process.env" | ".env file" | "package.json" | "command" | "detection";
+    key: string;
+    value: string;
+    timestamp: number;
+}
+/**
+ * Workspace environment result
+ */
+export interface WorkspaceEnvResult {
+    workspacePath: string;
+    mode: WorkspaceMode;
+    evidence: EnvEvidence[];
+    hasDevScript: boolean;
+    hasBuildScript: boolean;
+    packageManager: string | null;
+    devServerRunning: boolean;
+    buildServerRunning: boolean;
+    ramTotalGb: number | null;
+    ramAvailableGb: number | null;
+    ramEffectiveLimitGb: number | null;
+    lowRamWarning: boolean;
+    buildAllowed: boolean;
+    detectedAt: number;
+}
+/**
+ * Human readable mode label.
+ *
+ * "unknown" always carries the reason: the mode can only be proven by an
+ * explicit NODE_ENV (process env or .env file). When a NODE_ENV IS present
+ * but names a mode this detector does not know ("staging"), the label says
+ * exactly that instead of claiming there is no NODE_ENV at all.
+ */
+export declare function describeWorkspaceMode(env: WorkspaceEnvResult): string;
+/**
+ * Describe a dev/build server as a state.
+ *
+ * "not running (script available)" means the script EXISTS, i.e. a server
+ * could be started. It is not evidence that a server is running and not
+ * evidence about the workspace mode.
+ */
+export declare function describeServerState(running: boolean, hasScript: boolean): string;
+/**
+ * One line status for the footer / status bar.
+ */
+export declare function formatEnvStatusLine(env: WorkspaceEnvResult): string;
+/**
+ * Multi line description for the agent context.
+ */
+export declare function formatEnvForAgentResult(env: WorkspaceEnvResult): string;

package/packages/contracts/dist/workspace-env-format.js

@@ -0,0 +1,120 @@
+/**
+ * Workspace environment formatting helpers.
+ *
+ * Split out of workspace-env.ts so the wording can be unit tested without the
+ * node:sqlite dependency (bun 1.3.x has no node:sqlite module).
+ *
+ * Wording rules:
+ * - The mode is only reported when it is EXPLICIT (NODE_ENV). An unknown mode
+ *   is always shown with its reason, never as a bare word next to a dev
+ *   server state that could be read as proof of the mode.
+ * - A dev/build script is a CAPABILITY, not a state. The status line says
+ *   "not running (script available)" so it cannot be mistaken for a running
+ *   server or for evidence about the workspace mode.
+ */
+/**
+ * Human readable mode label.
+ *
+ * "unknown" always carries the reason: the mode can only be proven by an
+ * explicit NODE_ENV (process env or .env file). When a NODE_ENV IS present
+ * but names a mode this detector does not know ("staging"), the label says
+ * exactly that instead of claiming there is no NODE_ENV at all.
+ */
+export function describeWorkspaceMode(env) {
+    if (env.mode !== "unknown") {
+        return env.mode.toUpperCase();
+    }
+    const nodeEnv = env.evidence.find((e) => e.key === "NODE_ENV" && (e.source === "process.env" || e.source === ".env file"));
+    if (nodeEnv) {
+        return `UNKNOWN (NODE_ENV=${nodeEnv.value} is not a known mode)`;
+    }
+    return "UNKNOWN (no explicit NODE_ENV)";
+}
+/**
+ * Describe a dev/build server as a state.
+ *
+ * "not running (script available)" means the script EXISTS, i.e. a server
+ * could be started. It is not evidence that a server is running and not
+ * evidence about the workspace mode.
+ */
+export function describeServerState(running, hasScript) {
+    if (running)
+        return "running";
+    if (hasScript)
+        return "not running (script available)";
+    return "no script";
+}
+/**
+ * One line status for the footer / status bar.
+ */
+export function formatEnvStatusLine(env) {
+    const mode = describeWorkspaceMode(env);
+    const devStatus = describeServerState(env.devServerRunning, env.hasDevScript);
+    const buildStatus = describeServerState(env.buildServerRunning, env.hasBuildScript);
+    let status = `Workspace: ${mode} | dev server: ${devStatus} | build: ${buildStatus}`;
+    const ramStr = formatRam(env);
+    if (ramStr) {
+        status += ` | RAM: ${ramStr}`;
+    }
+    return status;
+}
+/**
+ * RAM segment of the status line.
+ *
+ * Both values are optional - an unreadable /proc must never produce a
+ * "7.7/null" line.
+ */
+function formatRam(env) {
+    const total = env.ramTotalGb;
+    const available = env.ramAvailableGb;
+    if (total === null && available === null)
+        return "";
+    if (total === null)
+        return `${available}GB available`;
+    if (available === null)
+        return `${total}GB total`;
+    return `${available}/${total}`;
+}
+/**
+ * RAM segment for the agent block.
+ */
+function formatRamForAgent(env) {
+    const total = env.ramTotalGb;
+    const available = env.ramAvailableGb;
+    if (total !== null && available !== null)
+        return `${available}/${total}GB available`;
+    if (total !== null)
+        return `${total}GB total`;
+    return `${available}GB available`;
+}
+/**
+ * Multi line description for the agent context.
+ */
+export function formatEnvForAgentResult(env) {
+    let message = `[Workspace Environment]\n`;
+    message += `Mode: ${describeWorkspaceMode(env)}\n`;
+    if (env.evidence.length > 0) {
+        const sources = env.evidence.map((e) => `${e.source}:${e.value}`).join(", ");
+        message += `Evidence: ${sources}\n`;
+    }
+    message += `Dev script: ${env.hasDevScript ? "yes" : "no"}\n`;
+    message += `Build script: ${env.hasBuildScript ? "yes" : "no"}\n`;
+    if (env.devServerRunning) {
+        message += `Dev server: running\n`;
+    }
+    if (env.buildServerRunning) {
+        message += `Build server: running\n`;
+    }
+    if (env.ramTotalGb !== null || env.ramAvailableGb !== null) {
+        message += `RAM: ${formatRamForAgent(env)}\n`;
+        if (env.lowRamWarning) {
+            message += `WARNING: Low RAM - avoid parallel build + dev\n`;
+        }
+    }
+    message += `\n`;
+    message += `Build allowed: ${env.buildAllowed ? "yes" : "no - requires explicit request"}\n`;
+    if (env.mode === "unknown") {
+        message += `\nNOTE: Environment unknown - a dev/build script only means a server CAN be started, it does not establish the workspace mode. Explicitly ask the user before build.\n`;
+    }
+    return message;
+}

package/packages/contracts/dist/workspace-env.d.ts

@@ -9,38 +9,15 @@
  * Stores detected environment in SQLite for agent reference.
  * Uses synchronous directory creation and exception-safe operations.
  */
+import { describeServerState, describeWorkspaceMode, formatEnvForAgentResult } from "./workspace-env-format.js";
+import type { EnvEvidence, WorkspaceEnvResult, WorkspaceMode } from "./workspace-env-format.js";
 /**
- * Workspace mode with explicit states
+ * The mode/evidence types and every human readable rendering of the workspace
+ * environment live in workspace-env-format.ts. They are re-exported here so
+ * the existing import paths keep working.
  */
-export type WorkspaceMode = "development" | "production" | "test" | "unknown";
-/**
- * Evidence source for mode detection
- */
-export interface EnvEvidence {
-    source: "process.env" | ".env file" | "package.json" | "command" | "detection";
-    key: string;
-    value: string;
-    timestamp: number;
-}
-/**
- * Workspace environment result
- */
-export interface WorkspaceEnvResult {
-    workspacePath: string;
-    mode: WorkspaceMode;
-    evidence: EnvEvidence[];
-    hasDevScript: boolean;
-    hasBuildScript: boolean;
-    packageManager: string | null;
-    devServerRunning: boolean;
-    buildServerRunning: boolean;
-    ramTotalGb: number | null;
-    ramAvailableGb: number | null;
-    ramEffectiveLimitGb: number | null;
-    lowRamWarning: boolean;
-    buildAllowed: boolean;
-    detectedAt: number;
-}
+export { describeServerState, describeWorkspaceMode, formatEnvForAgentResult, };
+export type { EnvEvidence, WorkspaceEnvResult, WorkspaceMode };
 /**
  * Detect and store workspace environment
  */

package/packages/contracts/dist/workspace-env.js

@@ -13,6 +13,7 @@ import { DatabaseSync } from "node:sqlite";
 import { existsSync, readFileSync, mkdirSync } from "fs";
 import { join } from "path";
 import { platform, totalmem, freemem } from "os";
+import { describeServerState, describeWorkspaceMode, formatEnvForAgentResult, formatEnvStatusLine as formatStatusLine, } from "./workspace-env-format.js";
 const STORE_DIR = join(process.env.HOME || "/home/frappe", ".pi-harness-runtime");
 /**
  * Ensure store directory exists synchronously
@@ -56,6 +57,12 @@ function initDatabase() {
 	`);
     return db;
 }
+/**
+ * The mode/evidence types and every human readable rendering of the workspace
+ * environment live in workspace-env-format.ts. They are re-exported here so
+ * the existing import paths keep working.
+ */
+export { describeServerState, describeWorkspaceMode, formatEnvForAgentResult, };
 /**
  * Parse dotenv file without loading secrets
  * Returns only NODE_ENV value, ignoring comments and other vars
@@ -143,31 +150,22 @@ function determineMode(processEnv, dotenvNodeEnv, evidence) {
     // Explicit process.env takes highest priority (for build processes)
     if (processEnv) {
         const env = processEnv.toLowerCase();
+        // The evidence is recorded for EVERY value, including one that names
+        // no known mode ("staging"): the label then says which NODE_ENV could
+        // not be interpreted instead of claiming there is none.
+        evidence.push({
+            source: "process.env",
+            key: "NODE_ENV",
+            value: env,
+            timestamp: Date.now(),
+        });
         if (env === "production") {
-            evidence.push({
-                source: "process.env",
-                key: "NODE_ENV",
-                value: env,
-                timestamp: Date.now(),
-            });
             return "production";
         }
         if (env === "development" || env === "dev") {
-            evidence.push({
-                source: "process.env",
-                key: "NODE_ENV",
-                value: env,
-                timestamp: Date.now(),
-            });
             return "development";
         }
         if (env === "test") {
-            evidence.push({
-                source: "process.env",
-                key: "NODE_ENV",
-                value: env,
-                timestamp: Date.now(),
-            });
             return "test";
         }
     }
@@ -385,48 +383,11 @@ export function revalidateWorkspaceEnv(workspacePath) {
  * Format workspace env as agent-readable message
  */
 export function formatEnvForAgent(workspacePath) {
-    const env = getWorkspaceEnv(workspacePath);
-    let message = `[Workspace Environment]\n`;
-    message += `Mode: ${env.mode.toUpperCase()}\n`;
-    if (env.evidence.length > 0) {
-        const sources = env.evidence.map((e) => `${e.source}:${e.value}`).join(", ");
-        message += `Evidence: ${sources}\n`;
-    }
-    message += `Dev script: ${env.hasDevScript ? "yes" : "no"}\n`;
-    message += `Build script: ${env.hasBuildScript ? "yes" : "no"}\n`;
-    if (env.devServerRunning) {
-        message += `Dev server: running\n`;
-    }
-    if (env.buildServerRunning) {
-        message += `Build server: running\n`;
-    }
-    if (env.ramTotalGb !== null) {
-        const ramStr = env.ramAvailableGb !== null
-            ? `${env.ramAvailableGb}/${env.ramTotalGb}GB available`
-            : `${env.ramTotalGb}GB total`;
-        message += `RAM: ${ramStr}\n`;
-        if (env.lowRamWarning) {
-            message += `WARNING: Low RAM - avoid parallel build + dev\n`;
-        }
-    }
-    message += `\n`;
-    message += `Build allowed: ${env.buildAllowed ? "yes" : "no - requires explicit request"}\n`;
-    if (env.mode === "unknown") {
-        message += `\nNOTE: Environment unknown. Explicitly ask user before build.\n`;
-    }
-    return message;
+    return formatEnvForAgentResult(getWorkspaceEnv(workspacePath));
 }
 /**
  * Format workspace env as compact status line for UI
  */
 export function formatEnvStatusLine(env) {
-    const mode = env.mode.toUpperCase();
-    const devStatus = env.devServerRunning ? "running" : (env.hasDevScript ? "available" : "none");
-    const buildStatus = env.buildServerRunning ? "running" : (env.hasBuildScript ? "explicit request" : "none");
-    const ramStr = env.ramAvailableGb !== null ? `${env.ramAvailableGb}/${env.ramTotalGb}` : "";
-    let status = `Workspace: ${mode} | dev server: ${devStatus} | build: ${buildStatus}`;
-    if (ramStr) {
-        status += ` | RAM: ${ramStr}`;
-    }
-    return status;
+    return formatStatusLine(env);
 }

package/packages/contracts/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi-harness/contracts",
-  "version": "1.1.387",
+  "version": "1.1.388",
   "type": "module",
   "description": "RPC schema definitions for pi-harness runtime",
   "main": "./dist/index.js",