@tokenoftrust/storefront-runner 2.2.10 → 2.2.12

package/apps/storefront/src/lib/shared/developerInvites.ts

@@ -1028,8 +1028,7 @@ export interface DeveloperAppBinding {
 /** Best-effort outcome of the app-binding write (never fails the invite). */
 export type AppBindingResult =
   | { recorded: true }
-  // Skipped fail-closed: the write was not attempted/counted because the seam is
-  // unconfigured OR the MCP route isn't mounted yet (401). Not an error.
+  // Skipped: the write was not attempted because the seam is unconfigured. Not an error.
   | { recorded: false; skipped: true; reason: string }
   // Attempted but failed for a real reason (bad body / store fault / transport).
   | { recorded: false; skipped: false; reason: string };
@@ -1047,9 +1046,8 @@ export type AppBindingResult =
  *     (capability/app are optional MCP defaults but sent explicitly). Idempotent.
  *   → 200 { status:'recorded', ... } | 401 bad/missing secret | 400 bad body | 502 store.
  *
- * FAIL-CLOSED: the MCP route is only mounted once the shared secret is set on the
- * MCP deploy, so an unconfigured seam (no URL/secret) OR a 401 is treated as
- * `{ skipped: true }`, not a hard failure. A 400/502/transport fault is a real
+ * An unconfigured seam (no URL/secret) is `{ skipped: true }`. A 401 (wrong secret, or a
+ * URL under the MCP's session-guarded /api surface), 400, 502 or transport fault is a real
  * (non-skipped) failure the caller surfaces as partial success.
  *
  * BEST-EFFORT by contract: this NEVER throws and NEVER blocks the invite. The
@@ -1081,11 +1079,12 @@ export async function recordDeveloperAppBinding(
     );
     if (res.status >= 200 && res.status < 300) return { recorded: true };
     if (res.status === 401) {
-      // Bad/missing secret or the MCP route isn't mounted yet — fail-closed as skipped.
+      // A route answered and refused: the secret does not match, or the URL sits under the
+      // MCP's session-guarded /api surface. Both are misconfiguration, so it is a failure.
       return {
         recorded: false,
-        skipped: true,
-        reason: "unauthorized (mcp service secret rejected or route unmounted)",
+        skipped: false,
+        reason: "unauthorized: the mcp service secret was rejected, or MCP_APP_BINDING_URL is not the /internal path",
       };
     }
     return {

package/apps/storefront/{vitest.config.ts → vitest.config.cts}

@@ -1,5 +1,9 @@
-import { defineConfig } from "vitest/config";
-import { fileURLToPath } from "node:url";
+// .cts so Vite compiles this in memory. An ESM config writes a sibling file, which the read-only
+// verification workspace rejects. The results cache is off: that workspace cannot create
+// node_modules/.vite/vitest.
+process.env.VITE_CJS_IGNORE_WARNING = "1";
+const { defineConfig } = require("vitest/config");
+const path = require("node:path");
 
 // Storefront unit tests — pure TS logic (tenant routing, search, query engine,
 // image-attr resolution, edge cache, etc.). We deliberately do NOT render .astro
@@ -7,12 +11,12 @@ import { fileURLToPath } from "node:url";
 // vite-plugin-head crashes under vitest@2 + astro@7 (configureServer reads an
 // undefined `ssr`). Render *logic* is extracted into testable modules instead
 // (e.g. lib/imageAttrs.ts), and rendered output is verified on a live preview.
-export default defineConfig({
+module.exports = defineConfig({
   // Mirror the `@` -> src alias from tsconfig so tests can import aliased modules
   // (e.g. src/config/tenants.ts, which pulls the theme registry).
   resolve: {
     alias: {
-      "@": fileURLToPath(new URL("./src", import.meta.url)),
+      "@": path.join(__dirname, "src"),
       // `astro:middleware` is a virtual id Astro's own Vite plugin maps onto this
       // real module. Mapping it the same way lets src/middleware/index.ts — the
       // branch-to-handler dispatch — be invoked in a unit test instead of only
@@ -26,5 +30,6 @@ export default defineConfig({
     // *.spec.ts matrix runs separately via playwright.a11y.config.ts).
     include: ["src/**/*.test.ts", "e2e/a11y/**/*.test.ts"],
     environment: "node",
+    cache: false,
   },
 });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tokenoftrust/storefront-runner",
-  "version": "2.2.10",
+  "version": "2.2.12",
   "license": "SEE LICENSE IN LICENSE",
   "description": "World-shareable storefront runner: multi-tenant renderer on Astro/Cloudflare. No control plane.",
   "packageManager": "pnpm@11.9.0",

package/packages/public-runtime/vitest.config.cts

@@ -0,0 +1,13 @@
+// .cts so Vite compiles this in memory. An ESM config writes a sibling file, which the read-only
+// verification workspace rejects. The results cache is off: that workspace cannot create
+// node_modules/.vite/vitest.
+process.env.VITE_CJS_IGNORE_WARNING = "1";
+const { defineConfig } = require("vitest/config");
+
+module.exports = defineConfig({
+  test: {
+    include: ["tests/**/*.test.ts"],
+    environment: "node",
+    cache: false,
+  },
+});

package/packages/public-runtime/vitest.config.ts

@@ -1,8 +0,0 @@
-import { defineConfig } from "vitest/config";
-
-export default defineConfig({
-  test: {
-    include: ["tests/**/*.test.ts"],
-    environment: "node",
-  },
-});