pi-harness-runtime 1.1.390 → 1.1.391

package/AGENTS.md

@@ -502,21 +502,27 @@ bun run build && bun run start   # Server deployment
 
 **This info is shown in UI and delivered to agent context:**
 ```
-Workspace: DEVELOPMENT | dev server: running | build: not running (script available) | RAM: 10/16
+Workspace: ~/pi-harness-runtime | OS: Linux | mode: DEVELOPMENT | dev server: running | dev script: available | build 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.
+A dev/build script is a CAPABILITY, not a state: `dev script: available` means
+the script exists, not that a server runs. The server state is separate and
+never claims more than it knows: `running`, `not detected` (a check ran and
+found nothing) or `not checked` (no check was possible, e.g. no `pgrep`).
+
+The OS is part of the line because it decides which command prints the
+working directory: `pwd` on Linux/macOS, `cd` or `echo %cd%` on Windows.
+The agent context names the command to use.
 
 **IMPORTANT Rules:**
 
 | State | Action |
 |-------|--------|
-| `Workspace: UNKNOWN (…)` | Explicitly ask user before build |
-| `Workspace: DEVELOPMENT` | Use `dev` mode, don't auto-build |
-| `Workspace: PRODUCTION` | Build allowed, but confirm with user |
+| `mode: UNKNOWN (…)` | Explicitly ask user before build |
+| `mode: DEVELOPMENT` | Use `dev` mode, don't auto-build |
+| `mode: PRODUCTION` | Build allowed, but confirm with user |
 | `Low RAM` | Never run parallel build + dev |
 | `Dev server running` | Reuse it, don't restart |
 

package/harness/startup-report.ts

@@ -59,7 +59,10 @@ export function oneLineError(error: unknown, maxLength = 160): string {
 			"$1<redacted>",
 		)
 		// A url path: "/bot123456:ABC-DEF/", "/token/abc12345".
-		.replace(/\bbot\d{4,}:[A-Za-z0-9_\-]{4,}/g, "<redacted>")
+		// The boundary is "not a digit" and not a word boundary, so a
+		// token that is glued to a word ("xbot123:ABC-DEF") is redacted
+		// as well.
+		.replace(/(^|[^0-9])\d{6,}:[A-Za-z0-9_\-]{4,}/g, "$1<redacted>")
 		.replace(
 			/(\/((?:access_token|api[-_]?key|token|secret)[=/]))[A-Za-z0-9_\-:]{4,}/gi,
 			"$1<redacted>",
@@ -177,6 +180,21 @@ export function lineConfigurationReport(options: {
 	telegramConfigured?: boolean;
 	/** The fix commands for the missing LINE credentials. */
 	fixes: string[];
+	/**
+	 * The fix commands for the channel access token only.
+	 *
+	 * The startup check validates the ACCESS TOKEN. The user id is only the
+	 * recipient of the messages, so a failed check must not point at
+	 * line-user-id.txt.
+	 */
+	accessTokenFixes?: string[];
+	/**
+	 * Why the channel did not start (from the adapter).
+	 *
+	 * It says WHICH problem it is - an invalid or revoked token, a LINE API
+	 * failure or a network failure - and it never contains a credential.
+	 */
+	channelDiagnostic?: string | null;
 }): StartupReport | null {
 	if (!options.clientKeyFilePresent) return null;
 	const channelState = options.channelState ?? "not-started";
@@ -204,15 +222,27 @@ export function lineConfigurationReport(options: {
 		}
 		if (channelState === "failed") {
 			// The credentials are there but the channel did not start - the
-			// credentials themselves are the likely cause.
+			// channel access token is what the startup check validates, so
+			// the user id must not be named as the cause.
+			const details = [
+				...(options.accessTokenFixes && options.accessTokenFixes.length > 0
+					? options.accessTokenFixes
+					: options.fixes),
+			];
+			if (options.channelDiagnostic) {
+				details.push(options.channelDiagnostic);
+			}
+			details.push(
+				"The startup check validates the channel access token - the user id is only the recipient of the messages.",
+			);
+			details.push(
+				"Fix the file, then reload Pi so the channel is checked again.",
+			);
 			return {
 				label: "LINE",
 				text: "configured but the LINE channel did not start",
 				status: "warn",
-				details: [
-					...options.fixes,
-					"Check the LINE credentials in ~/.pi-harness-runtime/keys/, then reload Pi.",
-				],
+				details,
 			};
 		}
 		// The credentials are there but the channel was never started in this

package/index.ts

@@ -163,6 +163,15 @@ let keyFileAuditDone = false;
  * startup line must not claim a green "configured".
  */
 let lineChannelState: "started" | "failed" | "not-started" = "not-started";
+/**
+ * Why the LINE channel did not start (from the adapter).
+ *
+ * The adapter knows the difference between an invalid or revoked token
+ * (401/403), a LINE API failure and a network failure - the startup
+ * summary shows it so the user knows what to fix. It never contains a
+ * credential.
+ */
+let lineChannelDiagnostic: string | null = null;
 let telegramChannelState: "started" | "failed" | "not-started" = "not-started";
 /** Did the relay client connect at least once in this extension load? */
 let relayStreamConnected = false;
@@ -1398,9 +1407,13 @@ async function initTelegram(pi: ExtensionAPI): Promise<void> {
 		if (lineChannelConfigured) {
 			if (center.isChannelHealthy("line")) {
 				lineChannelState = "started";
+				lineChannelDiagnostic = null;
 				addHarnessMessage("LINE", "configured and enabled (tap Toggle LINE to disable)", "ok");
 			} else {
 				lineChannelState = "failed";
+				// Keep the reason: "the token is wrong" and "LINE is down"
+				// need different actions.
+				lineChannelDiagnostic = center.getChannelDiagnostic("line");
 			}
 		}
 		if (telegramChannelState !== "started") {
@@ -1795,8 +1808,15 @@ function reportLineConfiguration(): void {
 		channelState: lineChannelState,
 		telegramConfigured: telegramIsConfigured(),
 		// The fallback makes sure that a warning always carries a command,
-		// even when the audit could not answer.
-		fixes: keyFileFixesOrFallback("LINE", ["channel access token", "user id"]),
+		// even when the audit could not answer. It names the ACCESS TOKEN
+		// only - the user id is the recipient of the messages, not the cause
+		// of a failed startup check.
+		fixes: keyFileFixesOrFallback("LINE", ["channel access token"]),
+		// The startup check validates the access token - the user id is only
+		// the recipient, so it must not be named as the cause.
+		accessTokenFixes: keyFileFixesOrFallback("LINE", ["channel access token"]),
+		// The reason the channel did not start (invalid token, LINE down, ...).
+		channelDiagnostic: lineChannelDiagnostic,
 		// Without Telegram the LINE channel cannot start - the user needs
 		// the Telegram commands, not only an explanation.
 		telegramFixes: keyFileFixesOrFallback("Telegram", ["bot token", "chat id"]),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-harness-runtime",
-  "version": "1.1.390",
+  "version": "1.1.391",
   "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.390",
+  "version": "1.1.391",
   "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.390",
+  "version": "1.1.391",
   "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.390",
+  "version": "1.1.391",
   "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.390",
+  "version": "1.1.391",
   "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.390",
+  "version": "1.1.391",
   "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.390",
+  "version": "1.1.391",
   "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.390",
+  "version": "1.1.391",
   "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.390",
+  "version": "1.1.391",
   "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.390",
+  "version": "1.1.391",
   "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.390",
+  "version": "1.1.391",
   "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.390",
+  "version": "1.1.391",
   "type": "module",
   "main": "src/index.ts",
   "exports": {

package/packages/clipboard-plugin/package.json

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

package/packages/code-generation/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi/code-generation",
-  "version": "1.1.390",
+  "version": "1.1.391",
   "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.390",
+  "version": "1.1.391",
   "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.390",
+  "version": "1.1.391",
   "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.390",
+  "version": "1.1.391",
   "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.390",
+  "version": "1.1.391",
   "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.390",
+  "version": "1.1.391",
   "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.390",
+  "version": "1.1.391",
   "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.390",
+  "version": "1.1.391",
   "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.390",
+  "version": "1.1.391",
   "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

@@ -37,6 +37,16 @@ export interface WorkspaceEnvResult {
     packageManager: string | null;
     devServerRunning: boolean;
     buildServerRunning: boolean;
+    /**
+     * The tri-state state of the dev server.
+     *
+     * "not detected" means a check ran and found nothing; "not checked"
+     * means no check was possible (an unsupported platform or a failed
+     * check). Neither of them is evidence that a server is not running.
+     */
+    devServerState?: ServerState;
+    /** The tri-state state of the build server. */
+    buildServerState?: ServerState;
     ramTotalGb: number | null;
     ramAvailableGb: number | null;
     ramEffectiveLimitGb: number | null;
@@ -44,6 +54,47 @@ export interface WorkspaceEnvResult {
     buildAllowed: boolean;
     detectedAt: number;
 }
+/**
+ * The state of a dev/build server.
+ */
+/**
+ * Is this command line a package-manager launcher?
+ *
+ * A launcher ("npm run dev", "bun run start") only STARTS a server - the
+ * server is its child. Counting the launcher would report a running
+ * server for a script that does not start one at all ("sleep 300").
+ *
+ * The rule is pure, so it lives in the pure module and can be tested
+ * without the SQLite cache.
+ */
+export declare function isLauncherCommand(cmdline: string): boolean;
+export type ServerState = "running" | "not-detected" | "not-checked";
+/**
+ * The name of the operating system the harness runs on.
+ *
+ * The OS decides which command shows the working directory (pwd on
+ * POSIX, cd / echo %cd% on Windows), so the summary names it.
+ */
+export declare function describeOs(platformName?: string): string;
+/**
+ * The command that prints the working directory on this OS.
+ */
+export declare function describeCwdCommand(platformName?: string): string;
+/**
+ * Remove the pids of our own processes from a pgrep result.
+ *
+ * The shell that runs pgrep carries the search pattern in its own command
+ * line, so pgrep always reports it - a server would be claimed where none
+ * runs. The pids of our own processes are therefore dropped.
+ */
+export declare function filterOwnPids(pids: string[], ownPids: string[]): string[];
+/**
+ * Shorten the home directory to "~".
+ *
+ * The check is on a path boundary: "/home/frappe" is the home of
+ * "/home/frappe/app", but not of "/home/frappeX".
+ */
+export declare function formatWorkspacePath(workspacePath: string, home?: string): string;
 /**
  * Human readable mode label.
  *
@@ -56,10 +107,12 @@ 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.
+ * "not detected" is what a check that found nothing says - it is NOT the
+ * same as "not running": on a platform where no check is possible the
+ * state is "not checked". Neither of them says anything about the
+ * workspace mode.
  */
+export declare function describeServerState(state: ServerState): string;
 export declare function describeServerState(running: boolean, hasScript: boolean): string;
 /**
  * One line status for the footer / status bar.

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

@@ -12,6 +12,88 @@
  *   "not running (script available)" so it cannot be mistaken for a running
  *   server or for evidence about the workspace mode.
  */
+/**
+ * The state of a dev/build server.
+ */
+/**
+ * Is this command line a package-manager launcher?
+ *
+ * A launcher ("npm run dev", "bun run start") only STARTS a server - the
+ * server is its child. Counting the launcher would report a running
+ * server for a script that does not start one at all ("sleep 300").
+ *
+ * The rule is pure, so it lives in the pure module and can be tested
+ * without the SQLite cache.
+ */
+export function isLauncherCommand(cmdline) {
+    return /^(npm|bun|yarn|pnpm)\b.*\b(run\s+)?(dev|start)\b/.test(cmdline.trim());
+}
+/**
+ * The name of the operating system the harness runs on.
+ *
+ * The OS decides which command shows the working directory (pwd on
+ * POSIX, cd / echo %cd% on Windows), so the summary names it.
+ */
+export function describeOs(platformName) {
+    const name = platformName ?? process.platform;
+    switch (name) {
+        case "linux":
+            return "Linux";
+        case "darwin":
+            return "macOS";
+        case "win32":
+            return "Windows";
+        default:
+            return name;
+    }
+}
+/**
+ * The command that prints the working directory on this OS.
+ */
+export function describeCwdCommand(platformName) {
+    switch (platformName ?? process.platform) {
+        case "win32":
+            return "cd or echo %cd% (CMD), or (Get-Location).Path (PowerShell)";
+        case "linux":
+        case "darwin":
+            return "pwd";
+        default:
+            return "pwd (POSIX shells)";
+    }
+}
+/**
+ * Remove the pids of our own processes from a pgrep result.
+ *
+ * The shell that runs pgrep carries the search pattern in its own command
+ * line, so pgrep always reports it - a server would be claimed where none
+ * runs. The pids of our own processes are therefore dropped.
+ */
+export function filterOwnPids(pids, ownPids) {
+    const own = new Set(ownPids.map((pid) => pid.trim()));
+    return pids.map((pid) => pid.trim()).filter((pid) => pid.length > 0 && !own.has(pid));
+}
+/**
+ * Shorten the home directory to "~".
+ *
+ * The check is on a path boundary: "/home/frappe" is the home of
+ * "/home/frappe/app", but not of "/home/frappeX".
+ */
+export function formatWorkspacePath(workspacePath, home) {
+    if (!workspacePath)
+        return "";
+    // A trailing separator is not part of the path.
+    const path = workspacePath.replace(/[\\/]+$/, "") || workspacePath;
+    const homeDir = (home ?? process.env["HOME"] ?? process.env["USERPROFILE"] ?? "").replace(/[\\/]+$/, "");
+    // A root home ("/") shortens nothing - every path would look like "~".
+    if (homeDir && homeDir !== "/" && path.startsWith(homeDir)) {
+        const rest = path.slice(homeDir.length);
+        if (rest === "")
+            return "~";
+        if (rest.startsWith("/") || rest.startsWith("\\"))
+            return `~${rest}`;
+    }
+    return path;
+}
 /**
  * Human readable mode label.
  *
@@ -30,28 +112,42 @@ export function describeWorkspaceMode(env) {
     }
     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";
+export function describeServerState(stateOrRunning, hasScript) {
+    // The legacy signature (a boolean plus the script flag) is kept so that
+    // published consumers keep working.
+    if (typeof stateOrRunning === "boolean") {
+        if (stateOrRunning)
+            return "running";
+        return hasScript ? "not running (script available)" : "no script";
+    }
+    switch (stateOrRunning) {
+        case "running":
+            return "running";
+        case "not-detected":
+            return "not detected";
+        case "not-checked":
+            return "not checked";
+        default:
+            // An unknown state is never reported as "not running".
+            return "not checked";
+    }
 }
 /**
  * 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}`;
+    // Without a stored state the honest answer is "not checked" - a legacy
+    // row that says "false" cannot tell a missing server from a platform
+    // where no check was possible.
+    const devState = env.devServerState ?? (env.devServerRunning ? "running" : "not-checked");
+    const buildState = env.buildServerState ?? (env.buildServerRunning ? "running" : "not-checked");
+    const path = formatWorkspacePath(env.workspacePath);
+    let status = `Workspace: ${path} | OS: ${describeOs()} | mode: ${mode}` +
+        ` | dev server: ${describeServerState(devState)}` +
+        ` | dev script: ${env.hasDevScript ? "available" : "unavailable"}` +
+        ` | build server: ${describeServerState(buildState)}` +
+        ` | build script: ${env.hasBuildScript ? "available" : "unavailable"}`;
     const ramStr = formatRam(env);
     if (ramStr) {
         status += ` | RAM: ${ramStr}`;
@@ -93,18 +189,19 @@ function formatRamForAgent(env) {
 export function formatEnvForAgentResult(env) {
     let message = `[Workspace Environment]\n`;
     message += `Mode: ${describeWorkspaceMode(env)}\n`;
+    message += `OS: ${describeOs()}\n`;
+    message += `Workspace path: ${formatWorkspacePath(env.workspacePath)}\n`;
+    message += `The workspace path was captured from the process working directory - to verify it in a shell: ${describeCwdCommand()}\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`;
-    }
+    const devState = env.devServerState ?? (env.devServerRunning ? "running" : "not-checked");
+    const buildState = env.buildServerState ?? (env.buildServerRunning ? "running" : "not-checked");
+    message += `Dev server: ${describeServerState(devState)}\n`;
+    message += `Build server: ${describeServerState(buildState)}\n`;
     if (env.ramTotalGb !== null || env.ramAvailableGb !== null) {
         message += `RAM: ${formatRamForAgent(env)}\n`;
         if (env.lowRamWarning) {

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

@@ -9,15 +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";
+import { describeCwdCommand, describeOs, describeServerState, describeWorkspaceMode, formatEnvForAgentResult, formatWorkspacePath } from "./workspace-env-format.js";
+import type { EnvEvidence, ServerState, WorkspaceEnvResult, WorkspaceMode } from "./workspace-env-format.js";
 /**
  * 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, };
-export type { EnvEvidence, WorkspaceEnvResult, WorkspaceMode };
+export { describeCwdCommand, describeOs, describeServerState, describeWorkspaceMode, formatEnvForAgentResult, formatWorkspacePath, };
+export type { EnvEvidence, ServerState, WorkspaceEnvResult, WorkspaceMode };
 /**
  * Detect and store workspace environment
  */