pi-freeflow 1.15.0 → 1.15.1

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 1.15.1
+
+### Patch Changes
+
+- Requests now roll over to the next relay when the current one answers with a disabled-deployment verdict, instead of failing on the first relay and requiring a manual switch. Other payment and quota refusals still surface immediately.
+
+## 1.15.0
+
+### Minor Changes
+
+- Free-tier requests now use native session identifiers and an up-to-date client version, after the upstream gateway began rejecting older formats with a free-tier error. `/freeflow test` also gains an end-to-end chat check that verifies a relay can actually run inference, not just list models.
+
 ## 1.14.0
 
 ### Minor Changes

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "pi-freeflow",
   "type": "module",
-  "version": "1.15.0",
+  "version": "1.15.1",
   "description": "Thin provider for OMP/Pi — model list + dumb relay proxy + log; host pi-ai owns thinking/normalization",
   "main": "extensions/index.ts",
   "types": "src/index.ts",

package/src/relay.ts

@@ -38,6 +38,26 @@ export function isRetriableStatus(status: number): boolean {
 		(status >= 520 && status <= 530)
 	);
 }
+
+/** Vercel edge markers identifying a relay-host (not upstream) verdict. */
+function hasVercelEdgeMarkers(res: Response): boolean {
+	return (
+		Boolean(res.headers.get("x-vercel-error")) ||
+		Boolean(res.headers.get("x-vercel-id")) ||
+		res.headers.get("server")?.toLowerCase().includes("vercel") === true
+	);
+}
+
+/**
+ * Gated 402 roll predicate: a 402 is a relay-host failure only when it
+ * carries Vercel edge markers or a DEPLOYMENT_DISABLED body match.
+ * Generic 402s (payment/quota) carry neither and must surface immediately.
+ */
+function isRelayDeploymentDisabled(res: Response, bodyText: string | null): boolean {
+	if (res.status !== 402) return false;
+	if (hasVercelEdgeMarkers(res)) return true;
+	return bodyText !== null && bodyText.includes("DEPLOYMENT_DISABLED");
+}
 /**
  * Per-conversation reasoning affinity. Callers sending caller-bound reasoning
  * pass the relay that issued it; `onServed` reports the relay that actually
@@ -230,6 +250,43 @@ export async function relayFetch(
 				}
 				continue;
 			}
+			// Relay deployment disabled (402 DEPLOYMENT_DISABLED from Vercel):
+			// A disabled deployment is a relay-host failure, so roll to the next
+			// relay. A blanket 402 must NOT roll: generic 402s are payment/quota
+			// verdicts that must surface immediately, so gate strictly on Vercel
+			// edge markers or a DEPLOYMENT_DISABLED body match and otherwise fall
+			// through to the terminal path below. The body is peeked via a clone so
+			// the downstream stream stays intact; on any clone/read failure decide
+			// on headers alone (headerless failure reads as a generic 402).
+			if (res.status === 402) {
+				let disabledBody: string | null = null;
+				try {
+					disabledBody = (await res.clone().text()).slice(0, 8192);
+				} catch {
+					disabledBody = null;
+				}
+				if (isRelayDeploymentDisabled(res, disabledBody)) {
+					markRelayFailure(targetUrl, 402, "Deployment disabled (DEPLOYMENT_DISABLED) on relay host");
+					lastResponse?.body?.cancel().catch(() => {});
+					lastResponse = res;
+					lastResponseRelay = targetUrl;
+					log(
+						"warn",
+						`relay ${targetUrl} returned 402 DEPLOYMENT_DISABLED in ${elapsed}s — rolling to next relay`,
+						{ upstream: url },
+						rid,
+					);
+					const now = Date.now();
+					if (now - lastRollNotify > ROLL_NOTIFY_MS) {
+						lastRollNotify = now;
+						const ui = getStatusUi();
+						if (ui?.notify) {
+							ui.notify(`relay ${shortRelayLabel(targetUrl)} failed (HTTP 402) — rolled to next relay`, "warning");
+						}
+					}
+					continue;
+				}
+			}
 			if (isRetriableStatus(res.status)) {
 				markRelayFailure(targetUrl, res.status);
 				lastResponse?.body?.cancel().catch(() => {});