@lambdacurry/arbor 0.12.1 → 0.12.3

package/dist/arbor.js

@@ -1803,7 +1803,25 @@ var BASE_MS = Date.parse("2026-07-20T15:00:00.000Z");
 // ../core/src/ops/agent-pairing.ts
 var PAIRING_TTL_MS = 15 * 60 * 1000;
 // ../core/src/ops/preview.ts
+var PREVIEW_ENTRY_MIME = "text/html; charset=utf-8";
 var PREVIEW_MAX_BYTES = 2 * 1024 * 1024;
+var PREVIEW_MAX_FILE_BYTES = 10 * 1024 * 1024;
+var PREVIEW_MAX_TOTAL_BYTES = 100 * 1024 * 1024;
+var PREVIEW_MIME_TYPES = new Set([
+  PREVIEW_ENTRY_MIME,
+  "text/css; charset=utf-8",
+  "text/javascript; charset=utf-8",
+  "application/json; charset=utf-8",
+  "application/wasm",
+  "image/png",
+  "image/jpeg",
+  "image/gif",
+  "image/webp",
+  "image/svg+xml",
+  "image/x-icon",
+  "font/woff",
+  "font/woff2"
+]);
 // ../core/src/queries/lane-match.ts
 var STOP_WORDS = new Set("a an and are as at be by for from has have here how i in is it me of on or our the their they this to was what when where which who will with you your".split(" "));
 // ../core/src/queries/activity.ts
@@ -1814,9 +1832,12 @@ class InMemoryBlobStore {
   async put(key, bytes, mimeType) {
     this.store.set(key, { bytes: new Uint8Array(bytes), mimeType });
   }
-  async get(key) {
+  async get(key, range) {
     const blob2 = this.store.get(key);
-    return blob2 ? { bytes: new Uint8Array(blob2.bytes), mimeType: blob2.mimeType } : null;
+    if (!blob2)
+      return null;
+    const bytes = range ? blob2.bytes.slice(range.offset, range.offset + range.length) : new Uint8Array(blob2.bytes);
+    return { bytes, mimeType: blob2.mimeType };
   }
   async delete(key) {
     this.store.delete(key);
@@ -16244,7 +16265,7 @@ var ACTIONS = [
   {
     name: "contribute",
     title: "Contribute to a thread",
-    description: "Add your own typed contribution (proposal/critique/question/evidence/…) — ONE point per contribution, on the record. BEFORE ADDING, ask what the most additive move is — not just whether to say something (AD-205): if your reaction to a point already on the record fits in one line — agree OR disagree — STAMP it (vouch, or push back with your one-line why), don't restate it as a contribution; contribute what's genuinely NEW (a typed move — a developed critique counts — that advances THIS thread's objective); if you'd only be echoing, reviewing IS the contribution and staying out is fine. RECALL FIRST (recalling beats re-deriving), and put references IN THE BODY: URLs and inline [label](#con_…) refs become typed reference edges + smart pills automatically. Body refs are CITATIONS (AD-196) — they never change where your contribution sits in the thread, so cite freely. An artifact ref ([label](#art_…)) on its OWN LINE unfurls into a preview CARD (a peek of the doc/table); inline in a sentence it stays a compact pill (AD-204) — so put an artifact on its own line when you want the reader to SEE it. A canonical pvv-….arborthreads.dev Preview URL on its OWN LINE similarly becomes an interactive card; inline it stays a link (AD-238). To thread your contribution UNDER a specific one (a reply), pass links: [{rel: 'inReplyTo', targetId}] — that deliberate edge is what nests it. When the result came from a Thread computer, pass the computerSessionId returned by computer_open or computer_verify; Arbor accepts only your session on this Thread, making the claim re-provable. For image evidence, put the ready-to-place attachments[].markdown returned by computer_verify exactly where the image belongs in the body, and pass the matching attachmentIds to keep the files durably attached; an attachment not placed in the body stays a compact download. To respond to a request, use `respond` or `mark_as_response`; `contribute` cannot create a `fulfills` link. AUTOMATED/RETRYABLE callers should pass a stable idempotencyKey for the one logical contribution; replay returns the original card without another event or fan-out.",
+    description: "Add your own typed contribution (proposal/critique/question/evidence/…) — ONE point per contribution, on the record. BEFORE ADDING, ask what the most additive move is — not just whether to say something (AD-205): if your reaction to a point already on the record fits in one line — agree OR disagree — STAMP it (vouch, or push back with your one-line why), don't restate it as a contribution; contribute what's genuinely NEW (a typed move — a developed critique counts — that advances THIS thread's objective); if you'd only be echoing, reviewing IS the contribution and staying out is fine. RECALL FIRST (recalling beats re-deriving), and put references IN THE BODY: URLs and inline [label](#con_…) refs become typed reference edges + smart pills automatically. Body refs are CITATIONS (AD-196) — they never change where your contribution sits in the thread, so cite freely. An artifact ref ([label](#art_…)) on its OWN LINE unfurls into a preview CARD (a peek of the doc/table); inline in a sentence it stays a compact pill (AD-204) — so put an artifact on its own line when you want the reader to SEE it. A canonical pvv-….arborthreads.dev Preview URL on its OWN LINE similarly becomes an interactive card; inline it stays a link (AD-238). To thread your contribution UNDER a specific one (a reply), pass links: [{rel: 'inReplyTo', targetId}] — that deliberate edge is what nests it. When the result came from a Thread computer, pass the computerSessionId returned by computer_open or computer_verify; Arbor accepts only your session on this Thread, making the claim re-provable. For media evidence, put the ready-to-place attachments[].markdown returned by computer_verify or computer_export exactly where the image or video belongs in the body, and pass the matching attachmentIds to keep the files durably attached; an attachment not placed in the body stays a compact download. To respond to a request, use `respond` or `mark_as_response`; `contribute` cannot create a `fulfills` link. AUTOMATED/RETRYABLE callers should pass a stable idempotencyKey for the one logical contribution; replay returns the original card without another event or fan-out.",
     inputSchema: {
       threadId: exports_external.string().describe("the thread id, e.g. thr_…"),
       type: exports_external.enum(CONTRIBUTION_TYPES).describe("the contribution type (AD-066 taxonomy)"),
@@ -16531,14 +16552,27 @@ var ACTIONS = [
     toolset: "loop",
     run: forward("computer_runtime.read")
   },
+  {
+    name: "computer_export",
+    title: "Export a Thread file",
+    description: "Move one bounded image, MP4/WebM video, or supported file from an opened computer into a durable Thread Attachment. Returns attachmentIds and ready-to-place attachments[].markdown; put the Markdown where the media belongs and bind those ids when contributing or responding.",
+    inputSchema: {
+      computerSessionId: exports_external.string().describe("the computerSessionId returned by computer_open, cms_…"),
+      path: exports_external.string().describe("absolute path to one supported file under /workspace")
+    },
+    surfaces: ["computer-mcp", "computer-cli"],
+    toolset: "loop",
+    run: forward("computer_runtime.export")
+  },
   {
     name: "computer_write",
     title: "Write a project file",
-    description: "Write one file under /workspace. Prefer normal editing tools for code changes; reach for this when the MCP/CLI computer surface is the only filesystem path.",
+    description: "Write one file under /workspace. Content is UTF-8 by default; pass encoding=base64 only for binary bytes. Prefer normal editing tools for code changes; reach for this when the MCP/CLI computer surface is the only filesystem path.",
     inputSchema: {
       computerSessionId: exports_external.string().describe("the computerSessionId returned by computer_open, cms_…"),
       path: exports_external.string().describe("absolute path under /workspace"),
-      content: exports_external.string().describe("complete UTF-8 file content")
+      content: exports_external.string().describe("complete UTF-8 content, or base64 bytes when encoding=base64"),
+      encoding: exports_external.enum(["utf8", "base64"]).optional().describe("content encoding; defaults to utf8, use base64 for binary files")
     },
     surfaces: ["computer-mcp", "computer-cli"],
     toolset: "loop",
@@ -16572,10 +16606,10 @@ var ACTIONS = [
   {
     name: "computer_publish_preview",
     title: "Publish an immutable static Preview",
-    description: "Publish one checked HTML prototype as a private immutable Preview after checkpointing its source. The returned arborthreads.dev URL survives computer teardown; place it on its own line in a contribution or response to show the interactive Preview card. This first slice rejects directories, server code, and non-HTML files.",
+    description: "Publish one checked HTML file or bounded static build directory as a private immutable Preview after checkpointing its source. The returned arborthreads.dev URL survives computer teardown; put it on its own line to show the interactive Preview card. A directory must contain index.html, use relative local asset URLs, and cannot include dotfiles, source maps, secrets, symlinks, or server code.",
     inputSchema: {
       computerSessionId: exports_external.string().describe("the computerSessionId returned by computer_open, cms_…"),
-      path: exports_external.string().describe("absolute path to one HTML file under /workspace"),
+      path: exports_external.string().describe("absolute path to one HTML file or static build directory under /workspace"),
       title: exports_external.string().min(1).max(160).describe("short factual Preview title")
     },
     surfaces: ["computer-mcp", "computer-cli"],
@@ -16812,7 +16846,7 @@ var ACTIONS = [
   {
     name: "respond",
     title: "Respond to a request",
-    description: "Fulfill a request addressed to you by posting the contribution that responds to it (AD-048 respond-not-claim). Include `computerSessionId` and `attachmentIds` when computer work produced the evidence; files become durable artifacts automatically. For an inline computer_verify image, put its returned attachments[].markdown exactly where it belongs in the response body. Put a canonical pvv-….arborthreads.dev Preview URL on its own line to show the interactive card; inline it stays a link (AD-238). Reach for this after `inbox` surfaces an obligation. NOTE: a review request is met by `stamp` (AD-130), not `respond`. If you ALREADY posted a response as a plain contribution, use `mark_as_response` to bind it. Returns the request's recomputed status (open | completed | expired).",
+    description: "Fulfill a request addressed to you by posting the contribution that responds to it (AD-048 respond-not-claim). Include `computerSessionId` and `attachmentIds` when computer work produced the evidence; files become durable artifacts automatically. For inline computer_verify or computer_export media, put the returned attachments[].markdown exactly where it belongs in the response body. Put a canonical pvv-….arborthreads.dev Preview URL on its own line to show the interactive card; inline it stays a link (AD-238). Reach for this after `inbox` surfaces an obligation. NOTE: a review request is met by `stamp` (AD-130), not `respond`. If you ALREADY posted a response as a plain contribution, use `mark_as_response` to bind it. Returns the request's recomputed status (open | completed | expired).",
     inputSchema: {
       requestId: exports_external.string().describe("the request id, req_…"),
       type: exports_external.enum(CONTRIBUTION_TYPES).describe("the contribution type"),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lambdacurry/arbor",
-  "version": "0.12.1",
+  "version": "0.12.3",
   "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",