wontopos-mcp 1.0.10 → 1.0.12

package/README.md

@@ -40,12 +40,15 @@ claude mcp add wontopos --env WONTOPOS_API_KEY=wos-live-... -- npx -y wontopos-m
 `WONTOPOS_USER_ID` picks the store this tool remembers into (optional, default
 `"default"`) - one per project, per person, or per agent.
 
-Store ids are folded: lowercased, and anything outside `[a-z0-9_]` becomes `_`.
-So `My-Project`, `my_project` and `MY.PROJECT` are **one store** sharing one set
-of memories, and an id with no latin alphanumerics at all (`선우`, `田中`) folds to
-underscores, which every such id on the key also folds to. The server prints the
-folded id at boot whenever it differs from what you configured. Pick ids that stay
-distinct after the fold if the stores must stay apart.
+Store ids are folded: lowercased, and anything outside `[a-z0-9_]` becomes `_`, so
+`My-Project`, `my_project` and `MY.PROJECT` all name **one store**. The boot line
+prints the folded id, which is the one that actually holds the memories. Creating a
+second id that folds onto an existing one is refused with `409 conflict_error`
+rather than silently sharing it, so pick ids that stay distinct after the fold.
+
+The id must also match `[A-Za-z0-9][A-Za-z0-9._-]{0,63}`. An id outside that (`선우`,
+`田中`, an email address) cannot be used at all: creating it answers 400 and every
+other call 404s. Romanize it, or key the store on an internal id.
 
 Create a key in the [console](https://wontopos.com). Optional env:
 `WONTOPOS_USER_ID` (default store, default `"default"`), `WONTOPOS_MODEL`
@@ -114,6 +117,30 @@ automatic retries, redirect refusal, response caps, and key hygiene apply as-is.
 
 ## Changelog
 
+- **1.0.12** - a server that could not answer anything reported itself ready. A store id
+  outside `[A-Za-z0-9][A-Za-z0-9._-]{0,63}` (`선우`, `田中`, an email) cannot be created
+  and cannot be reached, so every tool call 404s - and 1.0.11 warned about it and then
+  served anyway. Worse, the boot check told the agent to fix it with `create_store`,
+  which answers 400 on that same id. A bad API key has always exited loudly; an id that
+  nothing at runtime can repair is the same situation, so it now exits too. The exception
+  is `WONTOPOS_ALLOW_STORE_OVERRIDE=1`, where the agent names a store per call and the
+  configured one is only a default - there the server still has work to do, so it warns
+  and serves.
+- **1.0.11** - fixes a regression 1.0.10 introduced, published the same day. 1.0.10 was
+  right that the folded id should be *announced* and wrong to also *send* it. The API
+  records the raw id next to the folded one on purpose: that is how it tells a genuine
+  collision (`alice-smith` vs `alice.smith`, two people, one collection) from the same id
+  typed again. Sending the pre-folded form destroyed the signal, so a store created as
+  `My-Project` answered a later `create_store` for `my_project` with **409
+  conflict_error** - the store reported colliding with itself. Reads and writes were
+  never affected (the API folds those on lookup either way). Now the raw id travels and
+  only the messages speak in folded terms. Also corrected: 1.0.10 warned that an id with
+  no latin alphanumerics (`선우`, `田中`) makes every such id share one store. Measured
+  against the live rule, that is not what happens - store ids must match
+  `[A-Za-z0-9][A-Za-z0-9._-]{0,63}`, so creating one answers 400 and every other call
+  404s. It is unusable, not shared, and the warning now says so. And the general fold
+  warning was dropped from this package: the SDK emits its own on the boot call, and two
+  near-identical lines in a host log is worse than one.
 - **1.0.10** - the store id is announced as the id that actually holds the memories.
   1.0.8 fixed this for whitespace and stopped there: the API also lowercases an id and
   turns anything outside `[a-z0-9_]` into `_`, so `WONTOPOS_USER_ID=My-Project` read and

package/index.mjs

@@ -47,25 +47,31 @@ const ALLOW_STORE_OVERRIDE = flag(process.env.WONTOPOS_ALLOW_STORE_OVERRIDE);
 // untouched. Say it out loud instead.
 const STORE_FROM_ENV = (process.env.WONTOPOS_USER_ID || "").trim();
 const STORE_AS_CONFIGURED = STORE_FROM_ENV || "default";
-/** The API's store-id rule, mirrored: lowercase, anything outside [a-z0-9_] → "_".
+/** The API's store-id fold, mirrored: lowercase, anything outside [a-z0-9_] → "_".
+ *  The collection that holds the memories is named from this, so it is the honest
+ *  answer to "which store am I on" — WONTOPOS_USER_ID=My-Project reads and writes
+ *  `my_project`, while the ready line, the boot check and create_store all announced
+ *  "My-Project", handing the operator their own spelling back as confirmation.
+ *  1.0.8 fixed exactly that lie for whitespace and stopped there.
  *
- *  Mirrored here NOT to change where memories go — the API folds the id either way,
- *  so the same collection is reached — but so that everything this process SAYS names
- *  the store that actually holds them. 1.0.8 fixed exactly this lie for whitespace and
- *  stopped there; case and punctuation split the message from the store the same way.
- *  WONTOPOS_USER_ID=My-Project reads and writes `my_project` while the ready line, the
- *  boot check and create_store all announced "My-Project".
- *
- *  The collision it implies is the heavier half: ids differing only by case or
- *  punctuation are ONE store and therefore one set of memories. `Alice.Smith`,
- *  `alice-smith` and `alice_smith` are the same person as far as memory is concerned. */
+ *  Used for MESSAGES ONLY. 1.0.10 also sent it, and that was wrong: the API records
+ *  the RAW id alongside the folded one precisely so it can tell a real collision
+ *  ("alice-smith" vs "alice.smith", different people, one collection) from the same
+ *  id typed again. Sending the already-folded form destroys that signal — a store
+ *  created as `My-Project` answered a later create for `my_project` with
+ *  409 conflict_error, claiming the store collided with itself. The raw id goes to
+ *  the API, which owns this mapping; we only stop lying about the result. */
 const canonicalStoreId = (s) => s.toLowerCase().replace(/[^a-z0-9_]/g, "_");
-const STORE = canonicalStoreId(STORE_AS_CONFIGURED);
-/** True when the configured id survives the fold with nothing distinguishing left —
- *  a purely non-Latin id ("선우", "田中") becomes all underscores, so every such id in
- *  the account lands in the SAME store. Worth its own line: it is not a cosmetic
- *  difference like a dash, it is two different people sharing one memory. */
-const STORE_HAS_NO_ASCII = !/[a-z0-9]/.test(STORE);
+const STORE_FOLDED = canonicalStoreId(STORE_AS_CONFIGURED);
+/** What every request carries: the id as configured, trimmed. The API folds it. */
+const STORE = STORE_AS_CONFIGURED;
+/** Store ids are code-level identifiers — the API requires
+ *  `[A-Za-z0-9][A-Za-z0-9._-]{0,63}`, so an id with no latin alphanumerics at all
+ *  ("선우", "田中") is not merely folded, it is unusable: creation answers 400 and
+ *  every other call 404s, because the `__` it folds to can never be created either.
+ *  Measured against the live rule, not inferred. */
+const STORE_ID_RE = /^[A-Za-z0-9][A-Za-z0-9._-]{0,63}$/;
+const STORE_ID_UNUSABLE = !STORE_ID_RE.test(STORE);
 // Cap what a tool result may inject into the model's context. The SDK's 64MB cap
 // protects the process; this protects the conversation (a 2MB memory must not
 // become 2MB of context). Measured in UTF-8 BYTES, not JS chars: `str.length`
@@ -559,24 +565,35 @@ await server.connect(transport);
   };
 }
 console.error(
-  `wontopos-mcp ${VERSION} ready (store: ${STORE}${STORE_FROM_ENV ? "" : " — FALLBACK: WONTOPOS_USER_ID is not set"}${READ_ONLY ? ", read-only" : ""})`
+  `wontopos-mcp ${VERSION} ready (store: ${STORE_FOLDED}${STORE_FROM_ENV ? "" : " — FALLBACK: WONTOPOS_USER_ID is not set"}${READ_ONLY ? ", read-only" : ""})`
 );
 // Say it at boot, once, when the configured id is not the id that holds the memories.
 // The operator wrote this value by hand in a host config file and has no other way to
 // learn it was folded — and the ready line above, which used to repeat their spelling
 // back to them, was the very thing that made it look fine.
-if (STORE !== STORE_AS_CONFIGURED) {
+// The fold itself is NOT announced here: now that the raw id is what travels, the
+// SDK's own warning (2.2.27) fires on the boot check and says the same thing. Two
+// near-identical lines in a host log is worse than one. The ready line above already
+// names the folded store, which is the part the SDK does not cover.
+//
+// This one has no SDK equivalent — the SDK knows the fold, not the creation rule.
+// A key that can do nothing exits(1). An id that can do nothing used to WARN and then
+// serve — so the host reported a healthy MCP server whose every call 404'd, and the
+// boot check's own advice ("create_store") was impossible: creating this id answers
+// 400 by the same rule. Nothing the agent does at runtime can repair it, so it belongs
+// on the same side as the bad key.
+//
+// Unless the store is not pinned: under ALLOW_STORE_OVERRIDE the agent supplies an id
+// per call and the configured one is only a default, so the server still has work.
+if (STORE_ID_UNUSABLE) {
   console.error(
-    `wontopos-mcp: WONTOPOS_USER_ID ${JSON.stringify(STORE_AS_CONFIGURED)} is stored as ${JSON.stringify(STORE)} ` +
-      "(lowercased, and anything outside [a-z0-9_] becomes \"_\"). Ids that differ only by case or punctuation " +
-      "are ONE store and share one set of memories."
+    `wontopos-mcp: WONTOPOS_USER_ID ${JSON.stringify(STORE)} is not a usable store id. The API requires English ` +
+      "letters, digits and . _ - (1-64 chars, starting with a letter or digit), so creating it answers 400 and " +
+      "every other call 404s. Romanize it or pick a latin id."
   );
-  if (STORE_HAS_NO_ASCII) {
-    console.error(
-      `wontopos-mcp: nothing distinguishing survives the fold — ${JSON.stringify(STORE_AS_CONFIGURED)} became ` +
-        `${JSON.stringify(STORE)}, so EVERY id on this key with no a-z0-9 characters lands in this same store. ` +
-        "Use a latin-alphanumeric id (romanize it, or add a suffix) if these stores must stay apart."
-    );
+  if (!ALLOW_STORE_OVERRIDE) {
+    console.error("wontopos-mcp: every tool call would fail and no tool could repair it. Exiting.");
+    process.exit(1);
   }
 }
 
@@ -585,7 +602,7 @@ if (STORE !== STORE_AS_CONFIGURED) {
 // A missing store is recoverable (the agent can create_store) → warn and serve.
 mem.stats().then(
   (s) => {
-    console.error(`wontopos-mcp: store "${STORE}" verified (${s?.total_memories ?? "?"} memories).`);
+    console.error(`wontopos-mcp: store "${STORE_FOLDED}" verified (${s?.total_memories ?? "?"} memories).`);
     // Verified, but on the fallback store — the case a misconfiguration hides in.
     // The seeded `default` always exists, so this check passes and the operator has
     // no other signal that the store they configured is not the one in use.
@@ -603,15 +620,18 @@ mem.stats().then(
       process.exit(1);
     } else if (status === 404) {
       console.error(
-        `wontopos-mcp: the key works but store "${STORE}" does not exist — ` +
-        (READ_ONLY
-          ? "fix WONTOPOS_USER_ID (read-only mode cannot create stores)."
-          : "ask the agent to create it (create_store) or fix WONTOPOS_USER_ID.")
+        `wontopos-mcp: the key works but store "${STORE_FOLDED}" does not exist — ` +
+        (STORE_ID_UNUSABLE
+          // create_store answers 400 on this id by the same rule, so do not send them there.
+          ? "and it cannot be created under this id. Set WONTOPOS_USER_ID to a latin-alphanumeric id."
+          : READ_ONLY
+            ? "fix WONTOPOS_USER_ID (read-only mode cannot create stores)."
+            : "ask the agent to create it (create_store) or fix WONTOPOS_USER_ID.")
       );
     } else if (status === 402) {
       console.error("wontopos-mcp: the key works but the account has no card or balance (402) — top up at https://wontopos.com/console.");
     } else {
-      console.error(`wontopos-mcp: could not verify store "${STORE}" (${e?.message ?? e}) — continuing anyway.`);
+      console.error(`wontopos-mcp: could not verify store "${STORE_FOLDED}" (${e?.message ?? e}) — continuing anyway.`);
     }
   }
 );

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wontopos-mcp",
-  "version": "1.0.10",
+  "version": "1.0.12",
   "mcpName": "com.wontopos/mcp",
   "description": "(beta) Wontopos (WOS) long-term memory as an MCP server — one memory across Claude Code, Claude Desktop, Cursor, ChatGPT, and your own agents.",
   "keywords": [