@compilr-dev/sdk 0.29.3 → 0.29.5

package/dist/index.d.ts

@@ -110,6 +110,8 @@ export type { FileEpisodeStoreOptions, EpisodeRecorderConfig, WorkSummaryAnchorC
 export { resolveNext, evaluateBranchCondition, walkPastBranches, lookupLabel, applyBacktrack, } from './flow-runner/index.js';
 export type { BacktrackResult } from './flow-runner/index.js';
 export { readMCPConfigFile, writeMCPConfigFile, resolveServerEntry, loadMCPServers, saveMCPServerEntry, deleteMCPServerEntry, getServerNames, readMCPConfig, assertWritable, canConnect, } from './mcp-config.js';
+export { buildProjectUpdate } from './platform/project-patch.js';
+export type { ProjectPatch, ProjectUpdateResult } from './platform/project-patch.js';
 export type { MCPServerEntry, MCPConfigFile, ResolvedMCPServer, MCPConfigRead, ConfigValue, } from './mcp-config.js';
 export { serverHealth, needsAttention, describeHealth, estimateToolTokens, estimateServerCost, formatTokens, disabledTools, isToolEnabled, setToolEnabled, filterMcpToolsByEnablement, isSecretRef, secretRefFor, parseSecretRef, looksLikeSecret, resolveValues, describeMissing, planSecretStorage, toStoredValues, secretRefsOf, } from './mcp/index.js';
 export type { MCPServerHealth, MCPServerState, MCPConnectionStatus, HealthInput, MCPToolShape, ServerCost, SecretRef, ResolveResult, } from './mcp/index.js';

package/dist/index.js

@@ -233,6 +233,8 @@ export { resolveNext, evaluateBranchCondition, walkPastBranches, lookupLabel, ap
 // Shared MCP Configuration
 // =============================================================================
 export { readMCPConfigFile, writeMCPConfigFile, resolveServerEntry, loadMCPServers, saveMCPServerEntry, deleteMCPServerEntry, getServerNames, readMCPConfig, assertWritable, canConnect, } from './mcp-config.js';
+// Projects — the one allow-list both hosts write through (projects-restyling Phase 5)
+export { buildProjectUpdate } from './platform/project-patch.js';
 // MCP — health, per-tool enablement, secrets, cost (mcp-restyling Phase 1)
 export { serverHealth, needsAttention, describeHealth, estimateToolTokens, estimateServerCost, formatTokens, disabledTools, isToolEnabled, setToolEnabled, filterMcpToolsByEnablement, isSecretRef, secretRefFor, parseSecretRef, looksLikeSecret, resolveValues, describeMissing, planSecretStorage, toStoredValues, secretRefsOf, } from './mcp/index.js';
 // =============================================================================

package/dist/platform/project-patch.d.ts

@@ -0,0 +1,52 @@
+/**
+ * What a person may change about a project, and how it maps to the repository.
+ *
+ * ⚠️ ONE ALLOW-LIST, IN THE SDK, BECAUSE BOTH HOSTS WRITE PROJECTS. Desktop and the CLI each had
+ * their own hand-written snake_case mapping, and they had already drifted: the CLI turned an empty
+ * string into `undefined`, so a git remote could be set there but never CLEARED, while Desktop
+ * treated `''` as a deliberate clear. Same screen, same field, two different meanings for erasing
+ * it.
+ *
+ * ⚠️ AN ALLOW-LIST, NOT A SPREAD. `UpdateProjectInput` reaches machine state — `current_item_id`,
+ * `last_context`, `metadata` — and the SLUG via `name`. `projects.name` is UNIQUE NOT NULL and a
+ * real key, so an editor that could set it by sending one extra field could collide it or break
+ * every reference to it. The slug is derived at creation and frozen.
+ */
+import type { UpdateProjectInput } from './types.js';
+/** The camelCase fields an editor may write. Deliberately narrower than UpdateProjectInput. */
+export interface ProjectPatch {
+    displayName?: string;
+    description?: string;
+    /**
+     * Where the project lives.
+     *
+     * ⚠️ RE-POINTS THE PROJECT; IT DOES NOT MOVE ANYTHING. This is how a project whose folder was
+     * moved on disk is repaired — a host offering it should say so, because "Path" reads like a
+     * thing that relocates files.
+     */
+    path?: string;
+    docsPath?: string;
+    language?: string;
+    framework?: string;
+    packageManager?: string;
+    runtimeVersion?: string;
+    gitRemote?: string;
+    gitBranch?: string;
+    workflowMode?: string;
+    status?: string;
+}
+export type ProjectUpdateResult = {
+    ok: true;
+    input: UpdateProjectInput;
+} | {
+    ok: false;
+    error: string;
+};
+/**
+ * Map a patch onto the repository's input, or refuse it.
+ *
+ * ⚠️ AN EMPTY STRING IS A DELIBERATE CLEAR, NOT "LEAVE ALONE". Only `undefined` means untouched.
+ * Clearing a git remote has to be possible, and a host that cannot do it has no way to undo a
+ * typo in one.
+ */
+export declare function buildProjectUpdate(patch: ProjectPatch): ProjectUpdateResult;

package/dist/platform/project-patch.js

@@ -0,0 +1,69 @@
+/**
+ * What a person may change about a project, and how it maps to the repository.
+ *
+ * ⚠️ ONE ALLOW-LIST, IN THE SDK, BECAUSE BOTH HOSTS WRITE PROJECTS. Desktop and the CLI each had
+ * their own hand-written snake_case mapping, and they had already drifted: the CLI turned an empty
+ * string into `undefined`, so a git remote could be set there but never CLEARED, while Desktop
+ * treated `''` as a deliberate clear. Same screen, same field, two different meanings for erasing
+ * it.
+ *
+ * ⚠️ AN ALLOW-LIST, NOT A SPREAD. `UpdateProjectInput` reaches machine state — `current_item_id`,
+ * `last_context`, `metadata` — and the SLUG via `name`. `projects.name` is UNIQUE NOT NULL and a
+ * real key, so an editor that could set it by sending one extra field could collide it or break
+ * every reference to it. The slug is derived at creation and frozen.
+ */
+/*
+  ⚠️ `path` IS NOT IN HERE. `UpdateProjectInput` has no `path` key — it is written through the
+  repository's own column — so listing it beside the others would have needed a lie in the type.
+  It is handled explicitly in the loop, where the difference is visible.
+*/
+const FIELD_MAP = {
+    displayName: 'display_name',
+    description: 'description',
+    docsPath: 'docs_path',
+    language: 'language',
+    framework: 'framework',
+    packageManager: 'package_manager',
+    runtimeVersion: 'runtime_version',
+    gitRemote: 'git_remote',
+    gitBranch: 'git_branch',
+    workflowMode: 'workflow_mode',
+    status: 'status',
+};
+/**
+ * Map a patch onto the repository's input, or refuse it.
+ *
+ * ⚠️ AN EMPTY STRING IS A DELIBERATE CLEAR, NOT "LEAVE ALONE". Only `undefined` means untouched.
+ * Clearing a git remote has to be possible, and a host that cannot do it has no way to undo a
+ * typo in one.
+ */
+export function buildProjectUpdate(patch) {
+    const displayName = patch.displayName?.trim();
+    if (displayName !== undefined && displayName === '') {
+        return { ok: false, error: 'A project needs a name.' };
+    }
+    const path = patch.path?.trim();
+    if (path !== undefined && path === '') {
+        return {
+            ok: false,
+            error: 'A project needs a path — clearing it would lose track of the folder.',
+        };
+    }
+    const input = {};
+    if (path !== undefined)
+        input.path = path;
+    for (const key of Object.keys(FIELD_MAP)) {
+        const value = patch[key];
+        if (value === undefined)
+            continue;
+        if (key === 'displayName')
+            input.display_name = displayName;
+        else if (key === 'workflowMode')
+            input.workflow_mode = value;
+        else if (key === 'status')
+            input.status = value;
+        else
+            input[FIELD_MAP[key]] = value;
+    }
+    return { ok: true, input };
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@compilr-dev/sdk",
-  "version": "0.29.3",
+  "version": "0.29.5",
   "description": "Universal agent runtime for building AI-powered applications",
   "type": "module",
   "main": "dist/index.js",
@@ -30,6 +30,10 @@
       "types": "./dist/models/index.d.ts",
       "import": "./dist/models/index.js"
     },
+    "./mcp": {
+      "types": "./dist/mcp/index.d.ts",
+      "import": "./dist/mcp/index.js"
+    },
     "./package.json": "./package.json"
   },
   "files": [