@astrasyncai/verification-gateway 5.4.0 → 5.4.2

package/dist/adapters/nextjs.d.mts

@@ -1,4 +1,22 @@
-import 'next/server';
-import '../types-CD1F9fmp.mjs';
-export { c as createMatcherConfig, a as createMiddleware } from '../nextjs-DGJXzWst.mjs';
-import '../metadata-capture.mjs';
+import * as next_server from 'next/server';
+import { NextRequest } from 'next/server';
+import { N as NextJsMiddlewareOptions } from '../types-BU04qAAR.mjs';
+
+/**
+ * Create Next.js middleware for agent verification.
+ *
+ * v2.9.7 moved per-route policy out of merchant-side source code into the
+ * AstraSync dashboard. The middleware fetches its routes from the backend
+ * via `GET /endpoints/:counterpartyId/routes` on init and refreshes
+ * periodically — see `ExpressMiddlewareOptions` for the rationale (a dual
+ * config source silently conflicts with dashboard policy).
+ */
+declare function createMiddleware(options: NextJsMiddlewareOptions): (request: NextRequest) => Promise<next_server.NextResponse<unknown>>;
+/**
+ * Helper to create matcher config
+ */
+declare function createMatcherConfig(paths: string[]): {
+    matcher: string[];
+};
+
+export { createMatcherConfig, createMiddleware };

package/dist/adapters/nextjs.d.ts

@@ -1,4 +1,22 @@
-import 'next/server';
-import '../types-76TB0fxW.js';
-export { c as createMatcherConfig, a as createMiddleware } from '../nextjs-xM-jdNrX.js';
-import '../metadata-capture.js';
+import * as next_server from 'next/server';
+import { NextRequest } from 'next/server';
+import { N as NextJsMiddlewareOptions } from '../types-BU04qAAR.js';
+
+/**
+ * Create Next.js middleware for agent verification.
+ *
+ * v2.9.7 moved per-route policy out of merchant-side source code into the
+ * AstraSync dashboard. The middleware fetches its routes from the backend
+ * via `GET /endpoints/:counterpartyId/routes` on init and refreshes
+ * periodically — see `ExpressMiddlewareOptions` for the rationale (a dual
+ * config source silently conflicts with dashboard policy).
+ */
+declare function createMiddleware(options: NextJsMiddlewareOptions): (request: NextRequest) => Promise<next_server.NextResponse<unknown>>;
+/**
+ * Helper to create matcher config
+ */
+declare function createMatcherConfig(paths: string[]): {
+    matcher: string[];
+};
+
+export { createMatcherConfig, createMiddleware };

package/dist/adapters/nextjs.js

@@ -36,7 +36,7 @@ __export(nextjs_exports, {
 module.exports = __toCommonJS(nextjs_exports);
 
 // src/version.ts
-var SDK_VERSION = "5.4.0";
+var SDK_VERSION = "5.4.1";
 
 // src/http.ts
 var SDK_USER_AGENT = `astrasync-sdk/${SDK_VERSION}`;
@@ -231,7 +231,14 @@ function getCacheKey(request, counterpartyId) {
     request.callerMetadata?.sourceIp || "",
     request.callerMetadata?.userAgent || "",
     request.callerMetadata?.forwardedFor || "",
-    request.callerMetadata?.agentCardUrl || ""
+    request.callerMetadata?.agentCardUrl || "",
+    // UAT2 Bug B (5.4.1): the commerce phase and cart identity DO affect the
+    // backend verdict — the confirm leg is the ONLY leg that may execute
+    // first-party settlement. Without these, a confirm within the cache TTL of
+    // its start_checkout quote was served the cached quote-leg grant (no
+    // settlementOutcome) and never reached the backend. Same F-A1-07 bug class.
+    request.commercePhase || "",
+    request.checkoutSessionId || ""
   ].join("|");
 }
 function getCachedResult(request, counterpartyId) {