@drawbridge/drawbridge-utils 0.0.145 → 0.0.147

package/dist/connections/index.cjs

@@ -4177,9 +4177,8 @@ var shopify_default2 = {
               adminAccessToken,
               domain: connection2.shop
             });
-            if (subscriptions.length && subscriptions.every((subscription) => typeof subscription.metered === "boolean")) {
-              metered = ((_a = subscriptions.find((subscription) => subscription.usageLineItemId)) == null ? void 0 : _a.usageLineItemId) || null;
-            }
+            const usageLine = (_a = subscriptions.find((subscription) => subscription.usageLineItemId)) == null ? void 0 : _a.usageLineItemId;
+            if (usageLine) metered = usageLine;
           } catch (probeError) {
             billingProbeFailed = true;
             (_b = logger2 == null ? void 0 : logger2.warn) == null ? void 0 : _b.call(logger2, "shopify.health.billing.probe.failed", {
@@ -4550,19 +4549,17 @@ var shopify_default2 = {
   //
   // Scope drift is NOT here: drawbridge-sync writes it onto the connection
   // document, and the document's own warnings render beside these.
-  // Both cards carry `action : 'billing'`: the dashboard renders it as a real
-  // button that mints the corrective subscription (POST .../billing) and sends
-  // the owner to Shopify's confirmation screen — the fix lives in OUR
-  // dashboard, and the one Shopify-hosted step is the charge consent no app
-  // can perform for a merchant.
+  // Both cards send the merchant INTO THE APP via the store link already on
+  // this page — the App Home is where the issue renders (its error section)
+  // and where the fix runs (the release-then-reselect flow). No dashboard
+  // button: two entry points into a cancel flow is two ways to get it wrong.
   tasks: (data2) => {
     var _a;
     return [
       ...(data2 == null ? void 0 : data2.status) === "pending" ? [
         {
-          action: "billing",
-          message: "Approve the Drawbridge plan to activate this connection. You'll be asked to select a plan on Shopify, then everything else happens here.",
-          title: "Approve your plan",
+          message: "Open the Drawbridge app in your Shopify admin and choose your plan. The connection activates once Shopify confirms it.",
+          title: "Choose your plan",
           type: "warning"
         }
       ] : [],
@@ -4575,8 +4572,7 @@ var shopify_default2 = {
       // nagging on silence.
       ...(data2 == null ? void 0 : data2.status) === "active" && ((_a = data2 == null ? void 0 : data2.source) == null ? void 0 : _a.metered) === null ? [
         {
-          action: "billing",
-          message: "Order billing isn't set up for this store, so campaign-attributed orders aren't being charged. You'll need to reselect your plan on Shopify and approve it to fix this.",
+          message: "Order billing isn't set up for this store, so campaign-attributed orders aren't being charged. Open the Drawbridge app in your Shopify admin \u2014 it shows this issue and walks you through reselecting your plan.",
           title: "Fix order billing",
           type: "error"
         }

package/dist/connections/index.d.cts

@@ -4943,20 +4943,20 @@ var shopify = {
 							domain : connection.shop
 						});
 
-						// Only an ACTIVE approval says anything about metering — no
-						// subscriptions (mid-install, plan pending) leaves the stamp
-						// untouched rather than asserting null from silence. The
-						// every-boolean guard is version skew insurance: an older
-						// @drawbridge/shopify returns subscriptions without the flag
-						// (and without usageLineItemId), and reading that silence as
-						// unmetered would nag every healthy merchant to re-approve a
-						// plan that is fine — the flag being boolean proves an SDK
-						// that also reports the line id.
-						if( subscriptions.length && subscriptions.every( ( subscription ) => typeof subscription.metered === 'boolean' ) ){
-
-							metered = subscriptions.find( ( subscription ) => subscription.usageLineItemId )?.usageLineItemId || null;
-
-						}
+						// A usage line on the approval is POSITIVE evidence and gets
+						// stamped. Its ABSENCE proves nothing: measured 2026-09-04
+						// (both 2026-04 and unstable, against a plan whose meter
+						// exists), managed-pricing App-Events meters never
+						// materialize as subscription line items — AppUsagePricing is
+						// the legacy usage-charge model. Reading absence as
+						// "unmetered" flagged healthy stores, so absence is NO
+						// VERDICT: the stamp, the Issue, the card and the
+						// meter-missing pager all stay silent until a signal that can
+						// actually observe the meter exists (Partner API
+						// USAGE_CHARGE_APPLIED accrual events are that signal).
+						const usageLine = subscriptions.find( ( subscription ) => subscription.usageLineItemId )?.usageLineItemId;
+
+						if( usageLine ) metered = usageLine;
 
 					} catch ( probeError ) {
 
@@ -5417,18 +5417,16 @@ var shopify = {
 	//
 	// Scope drift is NOT here: drawbridge-sync writes it onto the connection
 	// document, and the document's own warnings render beside these.
-	// Both cards carry `action : 'billing'`: the dashboard renders it as a real
-	// button that mints the corrective subscription (POST .../billing) and sends
-	// the owner to Shopify's confirmation screen — the fix lives in OUR
-	// dashboard, and the one Shopify-hosted step is the charge consent no app
-	// can perform for a merchant.
+	// Both cards send the merchant INTO THE APP via the store link already on
+	// this page — the App Home is where the issue renders (its error section)
+	// and where the fix runs (the release-then-reselect flow). No dashboard
+	// button: two entry points into a cancel flow is two ways to get it wrong.
 	tasks : ( data ) => [
 		...( data?.status === 'pending'
 			? [
 				{
-					action : 'billing',
-					message : 'Approve the Drawbridge plan to activate this connection. You\'ll be asked to select a plan on Shopify, then everything else happens here.',
-					title : 'Approve your plan',
+					message : 'Open the Drawbridge app in your Shopify admin and choose your plan. The connection activates once Shopify confirms it.',
+					title : 'Choose your plan',
 					type : 'warning'
 				}
 			]
@@ -5444,8 +5442,7 @@ var shopify = {
 		...( data?.status === 'active' && data?.source?.metered === null
 			? [
 				{
-					action : 'billing',
-					message : 'Order billing isn\'t set up for this store, so campaign-attributed orders aren\'t being charged. You\'ll need to reselect your plan on Shopify and approve it to fix this.',
+					message : 'Order billing isn\'t set up for this store, so campaign-attributed orders aren\'t being charged. Open the Drawbridge app in your Shopify admin — it shows this issue and walks you through reselecting your plan.',
 					title : 'Fix order billing',
 					type : 'error'
 				}

package/dist/connections/index.d.ts

@@ -4943,20 +4943,20 @@ var shopify = {
 							domain : connection.shop
 						});
 
-						// Only an ACTIVE approval says anything about metering — no
-						// subscriptions (mid-install, plan pending) leaves the stamp
-						// untouched rather than asserting null from silence. The
-						// every-boolean guard is version skew insurance: an older
-						// @drawbridge/shopify returns subscriptions without the flag
-						// (and without usageLineItemId), and reading that silence as
-						// unmetered would nag every healthy merchant to re-approve a
-						// plan that is fine — the flag being boolean proves an SDK
-						// that also reports the line id.
-						if( subscriptions.length && subscriptions.every( ( subscription ) => typeof subscription.metered === 'boolean' ) ){
-
-							metered = subscriptions.find( ( subscription ) => subscription.usageLineItemId )?.usageLineItemId || null;
-
-						}
+						// A usage line on the approval is POSITIVE evidence and gets
+						// stamped. Its ABSENCE proves nothing: measured 2026-09-04
+						// (both 2026-04 and unstable, against a plan whose meter
+						// exists), managed-pricing App-Events meters never
+						// materialize as subscription line items — AppUsagePricing is
+						// the legacy usage-charge model. Reading absence as
+						// "unmetered" flagged healthy stores, so absence is NO
+						// VERDICT: the stamp, the Issue, the card and the
+						// meter-missing pager all stay silent until a signal that can
+						// actually observe the meter exists (Partner API
+						// USAGE_CHARGE_APPLIED accrual events are that signal).
+						const usageLine = subscriptions.find( ( subscription ) => subscription.usageLineItemId )?.usageLineItemId;
+
+						if( usageLine ) metered = usageLine;
 
 					} catch ( probeError ) {
 
@@ -5417,18 +5417,16 @@ var shopify = {
 	//
 	// Scope drift is NOT here: drawbridge-sync writes it onto the connection
 	// document, and the document's own warnings render beside these.
-	// Both cards carry `action : 'billing'`: the dashboard renders it as a real
-	// button that mints the corrective subscription (POST .../billing) and sends
-	// the owner to Shopify's confirmation screen — the fix lives in OUR
-	// dashboard, and the one Shopify-hosted step is the charge consent no app
-	// can perform for a merchant.
+	// Both cards send the merchant INTO THE APP via the store link already on
+	// this page — the App Home is where the issue renders (its error section)
+	// and where the fix runs (the release-then-reselect flow). No dashboard
+	// button: two entry points into a cancel flow is two ways to get it wrong.
 	tasks : ( data ) => [
 		...( data?.status === 'pending'
 			? [
 				{
-					action : 'billing',
-					message : 'Approve the Drawbridge plan to activate this connection. You\'ll be asked to select a plan on Shopify, then everything else happens here.',
-					title : 'Approve your plan',
+					message : 'Open the Drawbridge app in your Shopify admin and choose your plan. The connection activates once Shopify confirms it.',
+					title : 'Choose your plan',
 					type : 'warning'
 				}
 			]
@@ -5444,8 +5442,7 @@ var shopify = {
 		...( data?.status === 'active' && data?.source?.metered === null
 			? [
 				{
-					action : 'billing',
-					message : 'Order billing isn\'t set up for this store, so campaign-attributed orders aren\'t being charged. You\'ll need to reselect your plan on Shopify and approve it to fix this.',
+					message : 'Order billing isn\'t set up for this store, so campaign-attributed orders aren\'t being charged. Open the Drawbridge app in your Shopify admin — it shows this issue and walks you through reselecting your plan.',
 					title : 'Fix order billing',
 					type : 'error'
 				}

package/dist/connections/index.js

@@ -4103,9 +4103,8 @@ var shopify_default2 = {
               adminAccessToken,
               domain: connection2.shop
             });
-            if (subscriptions.length && subscriptions.every((subscription) => typeof subscription.metered === "boolean")) {
-              metered = ((_a = subscriptions.find((subscription) => subscription.usageLineItemId)) == null ? void 0 : _a.usageLineItemId) || null;
-            }
+            const usageLine = (_a = subscriptions.find((subscription) => subscription.usageLineItemId)) == null ? void 0 : _a.usageLineItemId;
+            if (usageLine) metered = usageLine;
           } catch (probeError) {
             billingProbeFailed = true;
             (_b = logger2 == null ? void 0 : logger2.warn) == null ? void 0 : _b.call(logger2, "shopify.health.billing.probe.failed", {
@@ -4476,19 +4475,17 @@ var shopify_default2 = {
   //
   // Scope drift is NOT here: drawbridge-sync writes it onto the connection
   // document, and the document's own warnings render beside these.
-  // Both cards carry `action : 'billing'`: the dashboard renders it as a real
-  // button that mints the corrective subscription (POST .../billing) and sends
-  // the owner to Shopify's confirmation screen — the fix lives in OUR
-  // dashboard, and the one Shopify-hosted step is the charge consent no app
-  // can perform for a merchant.
+  // Both cards send the merchant INTO THE APP via the store link already on
+  // this page — the App Home is where the issue renders (its error section)
+  // and where the fix runs (the release-then-reselect flow). No dashboard
+  // button: two entry points into a cancel flow is two ways to get it wrong.
   tasks: (data2) => {
     var _a;
     return [
       ...(data2 == null ? void 0 : data2.status) === "pending" ? [
         {
-          action: "billing",
-          message: "Approve the Drawbridge plan to activate this connection. You'll be asked to select a plan on Shopify, then everything else happens here.",
-          title: "Approve your plan",
+          message: "Open the Drawbridge app in your Shopify admin and choose your plan. The connection activates once Shopify confirms it.",
+          title: "Choose your plan",
           type: "warning"
         }
       ] : [],
@@ -4501,8 +4498,7 @@ var shopify_default2 = {
       // nagging on silence.
       ...(data2 == null ? void 0 : data2.status) === "active" && ((_a = data2 == null ? void 0 : data2.source) == null ? void 0 : _a.metered) === null ? [
         {
-          action: "billing",
-          message: "Order billing isn't set up for this store, so campaign-attributed orders aren't being charged. You'll need to reselect your plan on Shopify and approve it to fix this.",
+          message: "Order billing isn't set up for this store, so campaign-attributed orders aren't being charged. Open the Drawbridge app in your Shopify admin \u2014 it shows this issue and walks you through reselecting your plan.",
           title: "Fix order billing",
           type: "error"
         }

package/dist/providers.cjs

@@ -4102,9 +4102,8 @@ var shopify_default2 = {
               adminAccessToken,
               domain: connection2.shop
             });
-            if (subscriptions.length && subscriptions.every((subscription) => typeof subscription.metered === "boolean")) {
-              metered = ((_a = subscriptions.find((subscription) => subscription.usageLineItemId)) == null ? void 0 : _a.usageLineItemId) || null;
-            }
+            const usageLine = (_a = subscriptions.find((subscription) => subscription.usageLineItemId)) == null ? void 0 : _a.usageLineItemId;
+            if (usageLine) metered = usageLine;
           } catch (probeError) {
             billingProbeFailed = true;
             (_b = logger2 == null ? void 0 : logger2.warn) == null ? void 0 : _b.call(logger2, "shopify.health.billing.probe.failed", {
@@ -4475,19 +4474,17 @@ var shopify_default2 = {
   //
   // Scope drift is NOT here: drawbridge-sync writes it onto the connection
   // document, and the document's own warnings render beside these.
-  // Both cards carry `action : 'billing'`: the dashboard renders it as a real
-  // button that mints the corrective subscription (POST .../billing) and sends
-  // the owner to Shopify's confirmation screen — the fix lives in OUR
-  // dashboard, and the one Shopify-hosted step is the charge consent no app
-  // can perform for a merchant.
+  // Both cards send the merchant INTO THE APP via the store link already on
+  // this page — the App Home is where the issue renders (its error section)
+  // and where the fix runs (the release-then-reselect flow). No dashboard
+  // button: two entry points into a cancel flow is two ways to get it wrong.
   tasks: (data2) => {
     var _a;
     return [
       ...(data2 == null ? void 0 : data2.status) === "pending" ? [
         {
-          action: "billing",
-          message: "Approve the Drawbridge plan to activate this connection. You'll be asked to select a plan on Shopify, then everything else happens here.",
-          title: "Approve your plan",
+          message: "Open the Drawbridge app in your Shopify admin and choose your plan. The connection activates once Shopify confirms it.",
+          title: "Choose your plan",
           type: "warning"
         }
       ] : [],
@@ -4500,8 +4497,7 @@ var shopify_default2 = {
       // nagging on silence.
       ...(data2 == null ? void 0 : data2.status) === "active" && ((_a = data2 == null ? void 0 : data2.source) == null ? void 0 : _a.metered) === null ? [
         {
-          action: "billing",
-          message: "Order billing isn't set up for this store, so campaign-attributed orders aren't being charged. You'll need to reselect your plan on Shopify and approve it to fix this.",
+          message: "Order billing isn't set up for this store, so campaign-attributed orders aren't being charged. Open the Drawbridge app in your Shopify admin \u2014 it shows this issue and walks you through reselecting your plan.",
           title: "Fix order billing",
           type: "error"
         }

package/dist/providers.js

@@ -4058,9 +4058,8 @@ var shopify_default2 = {
               adminAccessToken,
               domain: connection2.shop
             });
-            if (subscriptions.length && subscriptions.every((subscription) => typeof subscription.metered === "boolean")) {
-              metered = ((_a = subscriptions.find((subscription) => subscription.usageLineItemId)) == null ? void 0 : _a.usageLineItemId) || null;
-            }
+            const usageLine = (_a = subscriptions.find((subscription) => subscription.usageLineItemId)) == null ? void 0 : _a.usageLineItemId;
+            if (usageLine) metered = usageLine;
           } catch (probeError) {
             billingProbeFailed = true;
             (_b = logger2 == null ? void 0 : logger2.warn) == null ? void 0 : _b.call(logger2, "shopify.health.billing.probe.failed", {
@@ -4431,19 +4430,17 @@ var shopify_default2 = {
   //
   // Scope drift is NOT here: drawbridge-sync writes it onto the connection
   // document, and the document's own warnings render beside these.
-  // Both cards carry `action : 'billing'`: the dashboard renders it as a real
-  // button that mints the corrective subscription (POST .../billing) and sends
-  // the owner to Shopify's confirmation screen — the fix lives in OUR
-  // dashboard, and the one Shopify-hosted step is the charge consent no app
-  // can perform for a merchant.
+  // Both cards send the merchant INTO THE APP via the store link already on
+  // this page — the App Home is where the issue renders (its error section)
+  // and where the fix runs (the release-then-reselect flow). No dashboard
+  // button: two entry points into a cancel flow is two ways to get it wrong.
   tasks: (data2) => {
     var _a;
     return [
       ...(data2 == null ? void 0 : data2.status) === "pending" ? [
         {
-          action: "billing",
-          message: "Approve the Drawbridge plan to activate this connection. You'll be asked to select a plan on Shopify, then everything else happens here.",
-          title: "Approve your plan",
+          message: "Open the Drawbridge app in your Shopify admin and choose your plan. The connection activates once Shopify confirms it.",
+          title: "Choose your plan",
           type: "warning"
         }
       ] : [],
@@ -4456,8 +4453,7 @@ var shopify_default2 = {
       // nagging on silence.
       ...(data2 == null ? void 0 : data2.status) === "active" && ((_a = data2 == null ? void 0 : data2.source) == null ? void 0 : _a.metered) === null ? [
         {
-          action: "billing",
-          message: "Order billing isn't set up for this store, so campaign-attributed orders aren't being charged. You'll need to reselect your plan on Shopify and approve it to fix this.",
+          message: "Order billing isn't set up for this store, so campaign-attributed orders aren't being charged. Open the Drawbridge app in your Shopify admin \u2014 it shows this issue and walks you through reselecting your plan.",
           title: "Fix order billing",
           type: "error"
         }

package/package.json

@@ -216,5 +216,5 @@
     "prepublishOnly": ". \"$HOME/.nvm/nvm.sh\" && nvm use && tsup && node --test"
   },
   "types": "dist/index.d.ts",
-  "version": "0.0.145"
+  "version": "0.0.147"
 }