@lambdacurry/arbor 0.21.23 → 0.21.24

package/dist/arbor.js

@@ -2011,6 +2011,11 @@ var threadComputers = sqliteTable("thread_computers", {
   successorComputerId: text("successor_computer_id"),
   restoredFromSnapshotId: text("restored_from_snapshot_id"),
   currentSnapshotId: text("current_snapshot_id"),
+  workspaceMutationStarted: integer("workspace_mutation_started").notNull().default(0),
+  workspaceMutationAcknowledged: integer("workspace_mutation_acknowledged").notNull().default(0),
+  workspaceDurableMutationVersion: integer("workspace_durable_mutation_version"),
+  workspaceRecoveryLeaseId: text("workspace_recovery_lease_id"),
+  workspaceRecoveryLeaseExpiresAt: ts("workspace_recovery_lease_expires_at"),
   createdByProfileId: text("created_by_profile_id").notNull().references(() => profiles.id),
   createdExecutionContextId: text("created_execution_context_id").notNull().references(() => executionContexts.id),
   createdAt: ts("created_at").notNull()
@@ -2057,10 +2062,13 @@ var computerSessions = sqliteTable("computer_sessions", {
   executionContextId: text("execution_context_id").notNull().references(() => executionContexts.id),
   configKey: text("config_key").notNull(),
   startingSnapshotId: text("starting_snapshot_id"),
+  openIdempotencyKey: text("open_idempotency_key"),
+  openIdempotencyFingerprint: text("open_idempotency_fingerprint"),
   attachedAt: ts("attached_at").notNull()
 }, (t) => ({
   computerIdx: index("computer_sessions_computer_idx").on(t.computerId, t.attachedAt),
-  threadIdx: index("computer_sessions_thread_idx").on(t.threadId, t.attachedAt)
+  threadIdx: index("computer_sessions_thread_idx").on(t.threadId, t.attachedAt),
+  openIdempotencyIdx: uniqueIndex("computer_sessions_open_idempotency_idx").on(t.profileId, t.threadId, t.openIdempotencyKey)
 }));
 var computerRuns = sqliteTable("computer_runs", {
   id: text("id").primaryKey(),
@@ -2841,6 +2849,11 @@ var RUN_PROVIDER_LIFECYCLE_PHASE_SET = new Set(RUN_PROVIDER_LIFECYCLE_PHASES);
 
 // ../core/src/ops/computer.ts
 var MAX_COMPUTER_REPOSITORIES = 10;
+var COMPUTER_WORKSPACE_RECOVERY_CHECKPOINT_DEADLINE_MS = 10 * 60 * 1000;
+var COMPUTER_WORKSPACE_RECOVERY_ATTACH_DEADLINE_MS = 31 * 60 * 1000;
+var COMPUTER_WORKSPACE_RECOVERY_HEALTH_DEADLINE_MS = 2 * 60 * 1000;
+var COMPUTER_WORKSPACE_RECOVERY_HEADROOM_MS = 2 * 60 * 1000;
+var COMPUTER_WORKSPACE_RECOVERY_LEASE_MS = COMPUTER_WORKSPACE_RECOVERY_CHECKPOINT_DEADLINE_MS + COMPUTER_WORKSPACE_RECOVERY_ATTACH_DEADLINE_MS + COMPUTER_WORKSPACE_RECOVERY_HEALTH_DEADLINE_MS + COMPUTER_WORKSPACE_RECOVERY_HEADROOM_MS;
 
 // ../core/src/ops/request.ts
 var REQUEST_TTL_MS = 14 * 24 * 60 * 60 * 1000;
@@ -18333,6 +18346,11 @@ var MCP_OUTPUT_SCHEMAS = {
     defaultCwd: exports_external.string(),
     capabilities: computerOpenCapabilities,
     agentBrief: computerOpenAgentBrief,
+    startupReceipt: exports_external.object({
+      computerSessionId: id,
+      replayed: exports_external.boolean(),
+      mutationRetrySafety: exports_external.literal("safe")
+    }),
     reconciliation: exports_external.union([
       exports_external.object({
         action: exports_external.literal("automatic_reprovision"),
@@ -18712,6 +18730,11 @@ var OUTPUT_SHAPERS = {
       "restorationOutcome",
       "addedRepositories"
     ]);
+    const startupReceipt = selected(result.startupReceipt, [
+      "computerSessionId",
+      "replayed",
+      "mutationRetrySafety"
+    ]);
     return defined([
       ["computerSessionId", result.computerSessionId],
       [
@@ -18743,6 +18766,7 @@ var OUTPUT_SHAPERS = {
           ["activeRuns", activeRuns]
         ]) : undefined
       ],
+      ["startupReceipt", startupReceipt],
       ["reconciliation", reconciliation]
     ]);
   },
@@ -19681,6 +19705,7 @@ var ACTION_DEFINITIONS = [
     description: "Open a Thread project environment and return its session/workspace, verified root repository instruction pointers, Agent Brief, capabilities, Runs, and reconciliation receipt. Forward profile-revision or additive authorized repository drift auto-reconciles through a successor; removal, setup, backend/provider/profile changes, or ambiguous drift refuse with computer_reprovision guidance.",
     inputSchema: {
       threadId: exports_external.string().describe("the Arbor Thread whose stable computer to open, thr_…"),
+      idempotencyKey: exports_external.string().min(1).max(200).describe("stable key for this ONE logical open; retry the same call unchanged—even after a lost response—to reuse the same ComputerSession; never mint a new key for an unresolved attempt"),
       vcpus: exports_external.number().int().min(1).max(4).optional().describe("optional container vCPU request"),
       label: exports_external.string().optional().describe("short runtime label for operator diagnostics")
     },
@@ -22635,7 +22660,7 @@ async function renderMe(ctx, action) {
 ` : "") + spaceLines;
   emitDual(me, human, action, ctx);
 }
-var CLI_NOTE = `On this CLI, before your first write: commands are NOUN-VERB (\`thread get\`, \`space get\`, not \`get thread\`). The underscore tool-names you see in MCP, recall, and docs (\`set_space_charter\`, \`transition_thread\`) work as CLI commands VERBATIM too — \`set_space_charter …\` and \`set space charter …\` are the same command, either form. Computer work is one parallel family: start project work with \`arbor computer open --thread-id thr_…\`, keep its cms_… receipt, then pass it as \`--computer-session-id\` to later tools. Checkpoint intermediate complete units; \`computer stop\` performs the final checkpoint before teardown. Internal Currybox grants are exchanged per call and never printed. A public screenshot is lighter: \`arbor computer verify --thread-id thr_… --target-url https://…\` runs directly, with no open/checkpoint/stop ceremony, and returns a gated download URL plus ready-to-place Markdown; put that Markdown where the image belongs in the contribution body and pass the matching attachment id. A single-argument command also takes a bare positional — \`recall "your question"\`, \`thread get thr_…\` — so you don't have to name the obvious flag. Flag names are kebab-derived from the inputs (\`--thread-id\`, \`--request-id\`, \`--contribution-id\` — not \`--thread\`/\`--request\`), so check \`arbor help\` or \`arbor <command> --help\` (now focused on that command's flags) instead of guessing. Pass long/markdown bodies via \`--body-file -\` (stdin), never shell-quoted; a one-line \`--summary\` (1-2 short sentences, hard limit 500 chars) on a long contribution becomes its recall snippet. List inputs always accept a REPEATED flag, one item each (\`--guidance "…" --guidance "…"\`) — the form that works everywhere. A single value additionally comma-splits for TOKEN lists (\`--capabilities a,b,c\`), but stays one literal item for PROSE lists (\`--guidance\`, \`--ways-to-help\`, \`--contribution-lanes\`) so a comma inside a sentence can't shred it; \`arbor <command> --help\` names which form each list flag takes. \`tree\` is the lifecycle map (default depth \`topics\`): choose a Topic, then \`recall --topic top_… "your question"\` before targeted \`thread get\`/\`artifact get\`; use \`topic get\` or deeper tree only when you intentionally need Topic-wide context or enumeration. If \`inbox\` is empty, that's "nothing needs you" — but if you're unsure your auth resolved, \`whoami\` confirms it.`;
+var CLI_NOTE = `On this CLI, before your first write: commands are NOUN-VERB (\`thread get\`, \`space get\`, not \`get thread\`). The underscore tool-names you see in MCP, recall, and docs (\`set_space_charter\`, \`transition_thread\`) work as CLI commands VERBATIM too — \`set_space_charter …\` and \`set space charter …\` are the same command, either form. Computer work is one parallel family: start project work with \`arbor computer open --thread-id thr_… --idempotency-key scope-open-1\`, reuse that key only for the same logical open, keep its cms_… receipt, then pass it as \`--computer-session-id\` to later tools. Checkpoint intermediate complete units; \`computer stop\` performs the final checkpoint before teardown. Internal Currybox grants are exchanged per call and never printed. A public screenshot is lighter: \`arbor computer verify --thread-id thr_… --target-url https://…\` runs directly, with no open/checkpoint/stop ceremony, and returns a gated download URL plus ready-to-place Markdown; put that Markdown where the image belongs in the contribution body and pass the matching attachment id. A single-argument command also takes a bare positional — \`recall "your question"\`, \`thread get thr_…\` — so you don't have to name the obvious flag. Flag names are kebab-derived from the inputs (\`--thread-id\`, \`--request-id\`, \`--contribution-id\` — not \`--thread\`/\`--request\`), so check \`arbor help\` or \`arbor <command> --help\` (now focused on that command's flags) instead of guessing. Pass long/markdown bodies via \`--body-file -\` (stdin), never shell-quoted; a one-line \`--summary\` (1-2 short sentences, hard limit 500 chars) on a long contribution becomes its recall snippet. List inputs always accept a REPEATED flag, one item each (\`--guidance "…" --guidance "…"\`) — the form that works everywhere. A single value additionally comma-splits for TOKEN lists (\`--capabilities a,b,c\`), but stays one literal item for PROSE lists (\`--guidance\`, \`--ways-to-help\`, \`--contribution-lanes\`) so a comma inside a sentence can't shred it; \`arbor <command> --help\` names which form each list flag takes. \`tree\` is the lifecycle map (default depth \`topics\`): choose a Topic, then \`recall --topic top_… "your question"\` before targeted \`thread get\`/\`artifact get\`; use \`topic get\` or deeper tree only when you intentionally need Topic-wide context or enumeration. If \`inbox\` is empty, that's "nothing needs you" — but if you're unsure your auth resolved, \`whoami\` confirms it.`;
 function renderOrient(ctx) {
   emitDual({ orientation: ORIENTATION, cliNote: CLI_NOTE }, `${ORIENTATION}
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lambdacurry/arbor",
-  "version": "0.21.23",
+  "version": "0.21.24",
   "description": "The Arbor CLI — a shared workspace for people and agents. The human + headless-agent write path over Arbor's guarded operation surface.",
   "keywords": [
     "agents",