@mulmoclaude/core 0.30.0 → 1.0.0

package/assets/helps/custom-view.md

@@ -208,11 +208,42 @@ if (res.ok) {
 } // non-ok: leave the placeholder — 404 = not an image-field value / unresolvable
 ```
 
+**Never fire one fetch per image in parallel** (`Promise.all` over every
+record) — the host caps in-flight `/image` + `/query` requests at **4 per
+collection** and answers the rest **429**, so a first paint of a dozen
+images half-fails. Resolve through a small worker pool instead:
+
+```js
+// Throttled resolver: N paths, at most 3 in flight, one retry on 429.
+async function resolveImages(paths, onResolved, workers = 3) {
+  const queue = [...paths];
+  const work = async () => {
+    for (let path = queue.shift(); path !== undefined; path = queue.shift()) {
+      let res = await fetch(dataUrl + "/image?path=" + encodeURIComponent(path) + "&maxEdge=256", {
+        headers: { Authorization: "Bearer " + token },
+      });
+      if (res.status === 429) {
+        await new Promise((r) => setTimeout(r, 500));
+        res = await fetch(dataUrl + "/image?path=" + encodeURIComponent(path) + "&maxEdge=256", {
+          headers: { Authorization: "Bearer " + token },
+        });
+      }
+      if (res.ok) onResolved(path, (await res.json()).dataUrl);
+    }
+  };
+  await Promise.all(Array.from({ length: workers }, work));
+}
+```
+
 - **Only current image-field values resolve.** The host checks `path`
   against the collection's records: it must be the CURRENT value of a
   schema `image`-type field — the token cannot read arbitrary workspace
   files. A stale or hand-built path answers 404.
 - `maxEdge` clamps to 64–1024 (default 512) — request the size you render.
+- **429 = concurrency/rate limit, not a bad path.** Both a shared in-flight
+  cap (4 per collection, shared with `/query`) and a per-minute budget guard
+  this endpoint; a 429'd path resolves fine on retry — never mark it failed
+  without one.
 - Cache the resolved `data:` URLs per path in your view (a simple `Map`)
   and re-resolve inside your `onChange` callback only for paths you haven't
   seen — each request re-scans the records server-side.

package/assets/helps/error-recovery.md

@@ -463,3 +463,30 @@ Two ways the link can be minted, and the tool picks automatically:
 - **Drive shows nothing / "I can't find the user's file"** — not an error. The app holds the
   `drive.file` scope, so it can only ever see files IT created; the user's wider Drive is
   invisible by design. Say so plainly instead of implying an empty Drive.
+
+## Custom view — some images 429 / only a few thumbnails render
+
+### Symptoms
+
+- A collection's custom view renders records fine, but only a handful of its
+  `image`-type field thumbnails appear; the rest stay placeholders.
+- The view's error UI (or console) shows **HTTP 429** from
+  `<dataUrl>/image` with **"too many concurrent queries for this collection —
+  retry shortly"**.
+
+### Cause
+
+The view resolves every image at once — typically a `Promise.all` over all
+records firing one `GET <dataUrl>/image` each. The host caps in-flight
+`/image` + `/query` requests at **4 per collection** (each request re-scans
+the records for authorization), and answers the overflow 429. The paths are
+valid; only the burst is.
+
+### Fix
+
+Edit the view's image-resolution code (`views/*.html` under the collection's
+skill directory) to throttle: a small worker pool (≤ 3 concurrent) draining a
+queue of paths, with one short-delay retry on 429. See the throttled-resolver
+example in `custom-view.md` ("Displaying images"). Do NOT widen the server
+cap, switch to base64-embedding images in the HTML, or treat the 429'd paths
+as bad values.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mulmoclaude/core",
-  "version": "0.30.0",
+  "version": "1.0.0",
   "description": "Shared server-side core for MulmoClaude and MulmoTerminal — the always-shipped-together subsystems consolidated behind subpath exports so the two hosts can't drift. Server-only except the browser-safe ./whisper/client, ./workspace-setup/slug, ./translation/client, ./remote-view and ./remote-host entries. All host specifics are injected.",
   "type": "module",
   "exports": {
@@ -182,7 +182,7 @@
   "peerDependencies": {
     "@receptron/task-scheduler": "*",
     "firebase": "^12.0.0",
-    "gui-chat-protocol": "^0.4.0"
+    "gui-chat-protocol": "^1.1.0"
   },
   "peerDependenciesMeta": {
     "firebase": {
@@ -192,7 +192,7 @@
   "devDependencies": {
     "@receptron/task-scheduler": "*",
     "@types/node": "^26.1.1",
-    "gui-chat-protocol": "^0.4.0",
+    "gui-chat-protocol": "^1.1.0",
     "tsx": "^4.23.1",
     "typescript": "^6.0.3",
     "vite": "^8.1.5",