context-mode 1.0.168 → 2.0.0-next.5

package/build/util/jsonc.js

@@ -1,104 +0,0 @@
-/**
- * util/jsonc — string-aware JSONC comment + trailing-comma stripping and a
- * tolerant parse. Several agent CLIs ship config files as JSONC (VS Code
- * `mcp.json`, Zed `settings.json`), so a strict `JSON.parse` false-fails on a
- * perfectly valid commented file. Use `parseJsonc` whenever reading a
- * platform config we did not write ourselves.
- */
-/** Strip `//` line + `/* *​/` block comments and trailing commas, string-aware. */
-export function stripJsonComments(str) {
-    let out = "";
-    let inString = false;
-    let escaped = false;
-    let inBlockComment = false;
-    for (let i = 0; i < str.length; i++) {
-        const c = str[i];
-        const next = str[i + 1];
-        if (inBlockComment) {
-            if (c === "*" && next === "/") {
-                inBlockComment = false;
-                i++;
-            }
-            continue;
-        }
-        if (escaped) {
-            out += c;
-            escaped = false;
-            continue;
-        }
-        if (c === "\\") {
-            out += c;
-            escaped = inString;
-            continue;
-        }
-        if (c === '"') {
-            inString = !inString;
-            out += c;
-            continue;
-        }
-        if (!inString && c === "/" && next === "/") {
-            while (i < str.length && str[i] !== "\n")
-                i++;
-            if (i < str.length)
-                out += "\n";
-            continue;
-        }
-        if (!inString && c === "/" && next === "*") {
-            inBlockComment = true;
-            i++;
-            continue;
-        }
-        out += c;
-    }
-    // Trailing-comma removal, string-aware. The scan above already removed
-    // comments, so this second pass over `out` only needs to track string state:
-    // a comma is "trailing" when the next significant char is `}` or `]`. Doing
-    // it here — instead of a post-hoc trailing-comma regex over the whole string —
-    // preserves commas inside string literals (e.g. "[1, ]"), which that regex
-    // silently corrupted to "[1 ]". See #787 review.
-    let result = "";
-    let inStr = false;
-    let esc = false;
-    for (let i = 0; i < out.length; i++) {
-        const c = out[i];
-        if (esc) {
-            result += c;
-            esc = false;
-            continue;
-        }
-        if (c === "\\") {
-            result += c;
-            esc = inStr;
-            continue;
-        }
-        if (c === '"') {
-            inStr = !inStr;
-            result += c;
-            continue;
-        }
-        if (!inStr && c === ",") {
-            let j = i + 1;
-            while (j < out.length && (out[j] === " " || out[j] === "\t" || out[j] === "\r" || out[j] === "\n"))
-                j++;
-            if (out[j] === "}" || out[j] === "]")
-                continue;
-        }
-        result += c;
-    }
-    return result;
-}
-/**
- * Parse JSON or JSONC. Tries strict `JSON.parse` first (fast, exact), then a
- * comment/trailing-comma-stripped parse. Returns `undefined` when both fail.
- */
-export function parseJsonc(raw) {
-    for (const candidate of [raw, stripJsonComments(raw)]) {
-        try {
-            return JSON.parse(candidate);
-        }
-        catch {
-            /* try next */
-        }
-    }
-    return undefined;
-}

package/build/util/plugin-cache-integrity.d.ts

@@ -1,51 +0,0 @@
-/**
- * TypeScript surface for the start.mjs plugin-cache integrity helper.
- *
- * The actual logic lives in `scripts/plugin-cache-integrity.mjs` (raw
- * `.mjs` so start.mjs can import it without a TS toolchain at boot —
- * #550 fail-fast happens BEFORE any bundle is loaded). This module is
- * the bridge that lets TS consumers (claude-code adapter's
- * getHealthChecks for Algo-D5, the cli doctor surface) call the same
- * function without duplicating the implementation.
- *
- * Single source of truth: scripts/plugin-cache-integrity.mjs. Boot
- * fail-fast (Algo-D4) and doctor diagnostic (Algo-D5) agree
- * byte-for-byte because they call the same exported function.
- *
- * Top-level dynamic import is used (not a static `import` from `.mjs`)
- * because the project is ESM and `import` of a sibling `.mjs` from a
- * `.ts` file relies on the bundler / loader resolving `.mjs`
- * extensions, which esbuild can do but tsc-only typecheck cannot. The
- * dynamic import is resolved by the runtime (Node ESM) regardless of
- * how the consumer was bundled. Errors are caught and surfaced as a
- * FAIL detail — the helper is required to ship in the npm tarball
- * (package.json files[]); a missing helper means the install is
- * fundamentally broken.
- */
-/**
- * Files `start.mjs` needs to launch the MCP server, checked dependency-free
- * (fs only) so this works even when the integrity helper
- * (`scripts/plugin-cache-integrity.mjs`) is itself missing — a missing helper
- * is itself a partial-install symptom, and the operator most needs to know
- * whether the launch entrypoint survived.
- *
- * - `start.mjs` is the plugin `command` target (`.claude-plugin/plugin.json`)
- *   and has NO fallback: if absent, `node ${CLAUDE_PLUGIN_ROOT}/start.mjs`
- *   fails immediately and the MCP server never starts.
- * - The server is loaded by start.mjs from `server.bundle.mjs`, falling back
- *   to `build/server.js`; it is only "missing" when BOTH are absent.
- */
-export declare function findMissingLaunchFiles(pluginRoot: string): string[];
-/**
- * Run the integrity check synchronously. If the helper module is
- * still loading (not yet cached) returns a FAIL with detail
- * "integrity helper not yet loaded" — caller should retry once the
- * doctor command's IO is complete. In practice the doctor is invoked
- * many MS after module load so this fallback is defensive only.
- */
-export declare function checkPluginCacheIntegritySync(pluginRoot: string): {
-    status: "OK" | "FAIL";
-    detail: string;
-};
-/** Force-await the helper load. Tests use this to deflake the eager fire-and-forget. */
-export declare function ensurePluginCacheIntegrityLoaded(): Promise<void>;

package/build/util/plugin-cache-integrity.js

@@ -1,146 +0,0 @@
-/**
- * TypeScript surface for the start.mjs plugin-cache integrity helper.
- *
- * The actual logic lives in `scripts/plugin-cache-integrity.mjs` (raw
- * `.mjs` so start.mjs can import it without a TS toolchain at boot —
- * #550 fail-fast happens BEFORE any bundle is loaded). This module is
- * the bridge that lets TS consumers (claude-code adapter's
- * getHealthChecks for Algo-D5, the cli doctor surface) call the same
- * function without duplicating the implementation.
- *
- * Single source of truth: scripts/plugin-cache-integrity.mjs. Boot
- * fail-fast (Algo-D4) and doctor diagnostic (Algo-D5) agree
- * byte-for-byte because they call the same exported function.
- *
- * Top-level dynamic import is used (not a static `import` from `.mjs`)
- * because the project is ESM and `import` of a sibling `.mjs` from a
- * `.ts` file relies on the bundler / loader resolving `.mjs`
- * extensions, which esbuild can do but tsc-only typecheck cannot. The
- * dynamic import is resolved by the runtime (Node ESM) regardless of
- * how the consumer was bundled. Errors are caught and surfaced as a
- * FAIL detail — the helper is required to ship in the npm tarball
- * (package.json files[]); a missing helper means the install is
- * fundamentally broken.
- */
-import { existsSync } from "node:fs";
-import { join } from "node:path";
-let cached = null;
-let cachedError = null;
-async function loadHelper() {
-    if (cached)
-        return cached;
-    if (cachedError)
-        return null;
-    try {
-        // Resolve relative to this compiled file. After tsc emits to
-        // build/util/plugin-cache-integrity.js, the helper sits at
-        // ../../scripts/plugin-cache-integrity.mjs. After esbuild bundles
-        // src/cli.ts to cli.bundle.mjs at the repo root, the same relative
-        // path resolves to ./scripts/plugin-cache-integrity.mjs. Both
-        // shapes are walked here.
-        const candidates = [
-            new URL("../../scripts/plugin-cache-integrity.mjs", import.meta.url),
-            new URL("./scripts/plugin-cache-integrity.mjs", import.meta.url),
-        ];
-        let lastErr = null;
-        for (const url of candidates) {
-            try {
-                const mod = (await import(url.href));
-                if (typeof mod?.assertPluginCacheIntegrity === "function") {
-                    cached = mod;
-                    return cached;
-                }
-            }
-            catch (err) {
-                lastErr = err;
-            }
-        }
-        cachedError =
-            lastErr instanceof Error ? lastErr.message : String(lastErr ?? "not found");
-        return null;
-    }
-    catch (err) {
-        cachedError = err instanceof Error ? err.message : String(err);
-        return null;
-    }
-}
-// Eagerly start the load on module init so the first synchronous
-// check() call can hit the cache. The promise is unawaited
-// intentionally — by the time any HealthCheck.check() runs (doctor
-// command, well after MCP server boot), the import has resolved.
-void loadHelper();
-/**
- * Files `start.mjs` needs to launch the MCP server, checked dependency-free
- * (fs only) so this works even when the integrity helper
- * (`scripts/plugin-cache-integrity.mjs`) is itself missing — a missing helper
- * is itself a partial-install symptom, and the operator most needs to know
- * whether the launch entrypoint survived.
- *
- * - `start.mjs` is the plugin `command` target (`.claude-plugin/plugin.json`)
- *   and has NO fallback: if absent, `node ${CLAUDE_PLUGIN_ROOT}/start.mjs`
- *   fails immediately and the MCP server never starts.
- * - The server is loaded by start.mjs from `server.bundle.mjs`, falling back
- *   to `build/server.js`; it is only "missing" when BOTH are absent.
- */
-export function findMissingLaunchFiles(pluginRoot) {
-    const missing = [];
-    if (!existsSync(join(pluginRoot, "start.mjs"))) {
-        missing.push("start.mjs");
-    }
-    if (!existsSync(join(pluginRoot, "server.bundle.mjs")) &&
-        !existsSync(join(pluginRoot, "build", "server.js"))) {
-        missing.push("server.bundle.mjs (or build/server.js)");
-    }
-    return missing;
-}
-/**
- * Run the integrity check synchronously. If the helper module is
- * still loading (not yet cached) returns a FAIL with detail
- * "integrity helper not yet loaded" — caller should retry once the
- * doctor command's IO is complete. In practice the doctor is invoked
- * many MS after module load so this fallback is defensive only.
- */
-export function checkPluginCacheIntegritySync(pluginRoot) {
-    if (cached) {
-        const result = cached.assertPluginCacheIntegrity({ pluginRoot });
-        if (result.ok) {
-            return {
-                status: "OK",
-                detail: `${pluginRoot} (all required runtime siblings present)`,
-            };
-        }
-        return {
-            status: "FAIL",
-            detail: `missing: ${result.missing.join(", ")}`,
-        };
-    }
-    if (cachedError) {
-        // The integrity helper (scripts/plugin-cache-integrity.mjs) ships in
-        // package.json files[]; if it failed to load, the install is already
-        // partial. Don't stop at "helper unavailable" — directly surface whether
-        // the launch entrypoint survived, because a missing start.mjs / server
-        // bundle is exactly what stops the MCP server from starting (and is what
-        // an interrupted /ctx-upgrade swap leaves behind).
-        const launchMissing = findMissingLaunchFiles(pluginRoot);
-        if (launchMissing.length > 0) {
-            return {
-                status: "FAIL",
-                detail: `partial install — critical launch files missing: ${launchMissing.join(", ")} ` +
-                    `(integrity helper also missing: ${cachedError}); the MCP server cannot start. ` +
-                    `Reinstall: npm install -g context-mode@latest`,
-            };
-        }
-        return {
-            status: "FAIL",
-            detail: `integrity helper unavailable: ${cachedError}`,
-        };
-    }
-    return {
-        status: "FAIL",
-        detail: "integrity helper not yet loaded",
-    };
-}
-/** Force-await the helper load. Tests use this to deflake the eager fire-and-forget. */
-export async function ensurePluginCacheIntegrityLoaded() {
-    await loadHelper();
-}

package/build/util/project-dir.d.ts

@@ -1,149 +0,0 @@
-import type { PlatformId } from "../adapters/types.js";
-/**
- * Project-dir resolution helpers — shared between `start.mjs` (the MCP entry
- * point) and `src/server.ts getProjectDir()` (the consumer).
- *
- * Background: when Claude Code runs `/ctx-upgrade`, it kills + respawns the
- * MCP server. The respawn happens with `cwd` set to the plugin install
- * directory (`~/.claude/plugins/cache/context-mode/context-mode/<version>/`).
- * The legacy `start.mjs` then set `CLAUDE_PROJECT_DIR = originalCwd`, which
- * poisoned every downstream `ctx_stats` / SessionDB / hash computation —
- * sessions silently re-rooted under the plugin install path.
- *
- * Defense-in-depth fix (v1.0.113):
- *   - `start.mjs` calls `isPluginInstallPath(originalCwd)` and skips the env
- *     auto-set when true (no poisoning at the source).
- *   - `getProjectDir()` calls `resolveProjectDir(...)` which rejects plugin-
- *     pathed env vars and the plugin cwd, preferring `process.env.PWD`
- *     (shell-set, survives `process.chdir`) before falling back.
- */
-/**
- * Detect whether a path lives inside an agent plugin install tree —
- * specifically `<home>/.claude/plugins/cache/<plugin>/<plugin>/<version>/`,
- * `<home>/.codex/plugins/cache/<plugin>/<plugin>/<version>/`, or the
- * marketplace mirror under `<home>/.{claude,codex}/plugins/marketplaces/...`.
- *
- * Cross-OS: matches both POSIX (`/`) and Windows (`\`) path separators.
- * Independent of `home` location — we only care about the agent plugin
- * suffix pattern.
- */
-export declare function isPluginInstallPath(p: string): boolean;
-/**
- * Read the per-session project dir from Claude Code's transcript files.
- *
- * Claude Code writes session transcripts under
- * `~/.claude/projects/<encoded-cwd>/<session-id>.jsonl`. Each line is a JSON
- * event; an early line (typically line 2) carries a `cwd` field with the
- * literal project directory the session is running against. The encoded dir
- * name itself is lossy (`/` and `.` both become `-`), so we read the JSONL.
- *
- * This is the strongest available signal when Claude Code does NOT propagate
- * `CLAUDE_PROJECT_DIR` to the spawned MCP env (the common case when Claude
- * Code is launched from the desktop app rather than `cd <project> && claude`).
- *
- * Returns `undefined` when no transcript exists, the projects dir is empty,
- * or no transcript carries a `cwd` field — caller falls through.
- *
- * Multi-window safety: the most-recently-modified jsonl wins. When the user
- * actively talks to one Claude Code window, that window's transcript is the
- * one being written to RIGHT NOW, so its mtime is freshest. Other windows'
- * transcripts have older mtimes and are correctly ignored.
- */
-export declare function resolveProjectDirFromTranscript(opts: {
-    projectsRoot: string;
-    /**
-     * Optional freshness guard. Claude Code updates the active transcript while
-     * the session is being used; stale transcripts from previous days must not
-     * become a global project-dir signal for other hosts that merely have
-     * ~/.claude on disk.
-     */
-    maxAgeMs?: number;
-    /** Test seam for maxAgeMs. Defaults to Date.now(). */
-    nowMs?: number;
-}): string | undefined;
-/**
- * Issue #45 / c4529042182 — recover the project-cwd from a Codex CLI
- * session log when the spawned MCP child inherits a non-project cwd
- * (e.g. $HOME when Codex was launched from anywhere outside the project).
- *
- * Codex writes its session transcripts to either
- * `${CODEX_HOME ?? ~/.codex}/sessions/<uuid>.jsonl` (CLI) or a dated desktop
- * layout such as
- * `${CODEX_HOME ?? ~/.codex}/sessions/YYYY/MM/DD/rollout-*.jsonl`.
- * The cwd appears on `meta.cwd` for the CLI shape and on
- * `payload.cwd` in `type: "session_meta"` records for Codex Desktop. Codex
- * publishes NO workspace env var to its child MCP processes — so unlike
- * Claude/Pi/Cursor, we have no env signal at all. The session log is the
- * strongest available signal.
- *
- * Mirror of `resolveProjectDirFromTranscript` for Claude Code; differences:
- *   • Sessions may live flat or in a dated hierarchy (no per-project encoded
- *     subdir like Claude's `~/.claude/projects/<encoded>/`).
- *   • The cwd is nested on `meta.cwd` or `payload.cwd`, not top-level `cwd`.
- *
- * Returns `null` when:
- *   • `codexHome` or its `sessions/` subdir does not exist.
- *   • No `.jsonl` files exist or none has a parseable cwd string.
- *   • The newest log is older than `transcriptMaxAgeMs` (multi-window guard).
- *   • The resolved cwd points at a plugin install path (poisoned).
- */
-export declare function resolveCodexSessionCwd(opts?: {
-    /** Defaults to `process.env.CODEX_HOME ?? path.join(os.homedir(), ".codex")`. */
-    codexHome?: string;
-    /**
-     * Optional freshness guard — Codex appends to the active log while the
-     * session is running, so a stale log from days ago must not become a
-     * global project-dir signal.
-     */
-    transcriptMaxAgeMs?: number;
-    /** Test seam for transcriptMaxAgeMs. Defaults to Date.now(). */
-    now?: number;
-}): string | null;
-/**
- * Pure project-dir resolver. Mirror of the env-var chain inside
- * `src/server.ts getProjectDir()`, but takes its inputs explicitly so the
- * resolver can be exercised under test without process-level mutation.
- *
- * Resolution order:
- *   1. Adapter-priority env vars (CLAUDE / GEMINI / VSCODE / OPENCODE / PI /
- *      IDEA / CONTEXT_MODE) — first non-empty AND non-plugin-path wins.
- *   2. Claude Code transcript heuristic — read `cwd` from the most-recently-
- *      modified `~/.claude/projects/<encoded>/<session>.jsonl`. This is the
- *      most reliable signal when Claude Code launched MCP from a non-project
- *      cwd (desktop-app launch, `/ctx-upgrade` respawn, etc.).
- *   3. `process.env.PWD` — shell-set, NOT updated by `process.chdir()`, so
- *      it survives the `start.mjs` chdir into the plugin dir. Skipped if
- *      it too points at a plugin install path.
- *   4. `cwd` — last resort. Returned even if it is a plugin path; the
- *      caller is responsible for rendering a graceful "no project context"
- *      message rather than panicking. Keeping the function total preserves
- *      operation of project-independent tools (sandbox execute, fetch).
- */
-export declare function resolveProjectDir(opts: {
-    env: Record<string, string | undefined>;
-    cwd: string;
-    pwd: string | undefined;
-    /** Optional override; production code passes `~/.claude/projects`. */
-    transcriptsRoot?: string;
-    /** Optional freshness guard for Claude Code transcript project recovery. */
-    transcriptMaxAgeMs?: number;
-    /** Test seam for transcriptMaxAgeMs. Defaults to Date.now(). */
-    nowMs?: number;
-    /**
-     * Issue #545 — opt-in tightening. When set, the candidate list is built
-     * algorithmically from `workspaceEnvVarsFor(strictPlatform)` plus the
-     * universal escape hatch. Foreign workspace vars (e.g. CLAUDE_PROJECT_DIR
-     * leaked into Pi's MCP child env) cannot win, regardless of cascade order.
-     *
-     * When `undefined`, the legacy literal candidate order is used (semver lock
-     * for `start.mjs` and any non-strict consumer).
-     */
-    strictPlatform?: PlatformId;
-    /**
-     * Issue #45 — override `${CODEX_HOME ?? ~/.codex}` for tests. When
-     * `strictPlatform === "codex"` and the env cascade yields nothing, the
-     * resolver reads `meta.cwd` from the newest session.jsonl under
-     * `${codexHome}/sessions/`.
-     */
-    codexHome?: string;
-}): string;