openzoo 0.12.2 → 0.12.4

package/lib/bindpath.js

@@ -25,9 +25,18 @@ import { config } from './config.js';
 import { corpusHash, rememberContext, lookupContext } from './contexts.js';
 import { withNamespace } from './namespace.js';
 
-/** Bodies over this go in their own part. Under the ~8MB transport ceiling
- *  with room for JSON escaping, which can inflate text substantially. */
-export const MAX_PART_BYTES = Number(process.env.OPENZOO_BIND_PART_BYTES || 4_000_000);
+/**
+ * Bodies over this go in their own part.
+ *
+ * Sized by TIME, not just by the transport ceiling. Each append re-indexes a
+ * larger context, so parts get progressively slower — MEASURED binding a 23MB
+ * Rust tree, 4MB parts ran 25s → 30s → 65s. A minutes-long bind is also a
+ * minutes-long window in which any gateway restart destroys all the work done
+ * so far (a deploy mid-bind cost exactly that, five good parts thrown away).
+ * Smaller parts cost more round trips, finish sooner, and lose less when
+ * something upstream cycles.
+ */
+export const MAX_PART_BYTES = Number(process.env.OPENZOO_BIND_PART_BYTES || 2_000_000);
 
 /** Text-ish files worth binding. Anything else is skipped rather than
  *  silently binding a binary as mojibake. */

package/lib/namespace.js

@@ -14,10 +14,27 @@ import { loadOrCreateWallet } from './wallet.js';
  * Derived from the PUBLIC key, never the secret: it must be stable across
  * restarts and reveal nothing. It is hashed again server-side, so the value on
  * the wire is not the address either.
+ *
+ * OPT-IN (OPENZOO_NAMESPACE=1), and off by default, deliberately.
+ *
+ * Isolation is only sound if EVERY surface agrees on the namespace. In
+ * practice they do not: the MCP server, the CLI and the proxy are separate
+ * processes that a user upgrades at different times (npx happily serves a
+ * stale cached build), so a corpus bound by a namespaced `zoo_bind` became
+ * invisible to a chat sent through an older proxy — the context vanished,
+ * every spill bind returned 400, and the gateway fell open and forwarded the
+ * whole body at full price. MEASURED twice in one session, in both directions.
+ *
+ * A header the client controls was the wrong mechanism: real isolation should
+ * key off the settling payer, which the gateway already knows and cannot get
+ * out of sync. Until that exists, defaulting off restores the behaviour that
+ * always worked, and the gateway's fallback keeps namespaced contexts
+ * reachable for anyone who opts in.
  */
 let cached = null;
 
 export function namespaceHeaderValue() {
+  if (process.env.OPENZOO_NAMESPACE !== '1') return '';
   if (cached) return cached;
   try {
     const w = loadOrCreateWallet();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openzoo",
-  "version": "0.12.2",
+  "version": "0.12.4",
   "description": "Local x402-paying proxy + MCP server for openzoo.fun — point any OpenAI-compatible harness (Cursor, Claude Code, aider, SDKs) at localhost and it pays per call from a local burner wallet. Solana and Base rails live; Robinhood experimental.",
   "license": "MIT",
   "type": "module",