@nextcommerce/campaigns-os 1.54.0 → 1.57.0

package/campaign-spec/dist/rules/pre-payment-forward-target.js

@@ -0,0 +1,42 @@
+/**
+ * PrePaymentForwardTarget — a `select` or `checkout_step` page takes no
+ * payment, so it must not forward straight to a post-payment page (an upsell,
+ * a downsell or a thank-you page). Doing so skips the Checkout: the shopper
+ * reaches an offer or a receipt with no order placed (campaigns-os#641).
+ *
+ * Only the resolved forward link is judged — routing.ts already ignores a
+ * `success_url` or `on_accept` on these types, and RouteFieldIgnoredForPageType
+ * warns about those separately.
+ */
+import { forwardRouteTarget } from "../routing.js";
+import { POST_PAYMENT_PAGE_TYPES, forwardTargetPage, isPrePaymentPage } from "../checkout-flow.js";
+export const PrePaymentForwardTarget = {
+    id: 'PrePaymentForwardTarget',
+    severity: 'error',
+    tags: ['fast', 'structure', 'spec-only'],
+    check(spec) {
+        const violations = [];
+        spec.funnels.forEach((funnel, funnelIdx) => {
+            const pages = funnel.pages ?? [];
+            pages.forEach((page, pageIdx) => {
+                if (!isPrePaymentPage(page))
+                    return;
+                const target = forwardTargetPage(pages, page);
+                if (!target)
+                    return;
+                const targetType = typeof target.type === 'string' ? target.type : '';
+                if (!POST_PAYMENT_PAGE_TYPES.includes(targetType))
+                    return;
+                violations.push({
+                    ruleId: 'PrePaymentForwardTarget',
+                    severity: 'error',
+                    message: `"${page.type}" page "${page.id}" forwards to "${target.id}" (type "${targetType}") without passing a Checkout. ` +
+                        'Route it (via next_page) to the next checkout step or to the Checkout that takes payment.',
+                    path: `/funnels/${funnelIdx}/pages/${pageIdx}/next_page`,
+                    data: { pageId: page.id, pageType: page.type, target: forwardRouteTarget(page), targetPageId: target.id, targetType },
+                });
+            });
+        });
+        return violations;
+    },
+};

package/campaign-spec/dist/rules/promo-code-input-validation.js

@@ -4,6 +4,7 @@
  * intent because both surfaces apply a voucher/code-backed Offer through the
  * same Campaign Cart SDK/Campaigns API pricing path.
  */
+import { isCheckoutFlowPage } from "../checkout-flow.js";
 function isTruthyString(value) {
     return typeof value === 'string' && value.trim().length > 0;
 }
@@ -39,7 +40,7 @@ export const PromoCodeInputValidation = {
                 const code = promo.offer_code;
                 const refOffer = ref ? index.byRefId.get(String(ref)) : null;
                 const codeOffer = code ? index.byCode.get(String(code).toUpperCase()) : null;
-                if (page.type !== 'checkout') {
+                if (!isCheckoutFlowPage(page)) {
                     violations.push({
                         ruleId: 'PromoCodeInputValidation',
                         severity: 'warning',

package/campaign-spec/dist/rules/schema-version.d.ts

@@ -9,13 +9,18 @@
  * lineage errors here at authoring/export time instead of surfacing as
  * downstream shape drift.
  *
- * SUPPORTED_SCHEMA_VERSIONS must stay identical to the schema_version enum in
- * schemas/campaign-spec.v4.schema.json (and compatibility.json's campaign_spec
- * range). The rule stays pure (no filesystem), so the constant duplicates the
+ * SUPPORTED_SCHEMA_VERSIONS must stay identical to the schema_version enums of
+ * schemas/campaign-spec.v4.schema.json and schemas/campaign-spec.v5.schema.json,
+ * concatenated (and compatibility.json's campaign_spec range). The rule stays pure (no filesystem), so the constant duplicates the
  * schema enum — the sync test in ../test/rules/schema-version.test.ts is the
  * drift gate, following the UnknownTopLevelFields pattern.
  */
 import type { Rule } from '../types.ts';
-/** Supported CampaignSpec lineage versions — keep in sync with the v4 JSON Schema enum. */
+/**
+ * Supported CampaignSpec lineage versions — the v4 JSON Schema enum followed by
+ * the v5 one, in that order. A 4.2/4.3 spec is upgraded to v5 on read
+ * (checkout-flow.ts), so this rule sees `5.0` for it after normalize(); the v4
+ * entries stay so a caller running the rule on an un-normalized spec agrees.
+ */
 export declare const SUPPORTED_SCHEMA_VERSIONS: readonly string[];
 export declare const SchemaVersion: Rule;

package/campaign-spec/dist/rules/schema-version.js

@@ -9,14 +9,19 @@
  * lineage errors here at authoring/export time instead of surfacing as
  * downstream shape drift.
  *
- * SUPPORTED_SCHEMA_VERSIONS must stay identical to the schema_version enum in
- * schemas/campaign-spec.v4.schema.json (and compatibility.json's campaign_spec
- * range). The rule stays pure (no filesystem), so the constant duplicates the
+ * SUPPORTED_SCHEMA_VERSIONS must stay identical to the schema_version enums of
+ * schemas/campaign-spec.v4.schema.json and schemas/campaign-spec.v5.schema.json,
+ * concatenated (and compatibility.json's campaign_spec range). The rule stays pure (no filesystem), so the constant duplicates the
  * schema enum — the sync test in ../test/rules/schema-version.test.ts is the
  * drift gate, following the UnknownTopLevelFields pattern.
  */
-/** Supported CampaignSpec lineage versions — keep in sync with the v4 JSON Schema enum. */
-export const SUPPORTED_SCHEMA_VERSIONS = Object.freeze(['4.2', '4.3']);
+/**
+ * Supported CampaignSpec lineage versions — the v4 JSON Schema enum followed by
+ * the v5 one, in that order. A 4.2/4.3 spec is upgraded to v5 on read
+ * (checkout-flow.ts), so this rule sees `5.0` for it after normalize(); the v4
+ * entries stay so a caller running the rule on an un-normalized spec agrees.
+ */
+export const SUPPORTED_SCHEMA_VERSIONS = Object.freeze(['4.2', '4.3', '5.0']);
 export const SchemaVersion = {
     id: 'SchemaVersion',
     severity: 'error',

package/campaign-spec/dist/types.d.ts

@@ -2,8 +2,9 @@
  * Type surface for the CampaignSpec contract layer.
  *
  * The CampaignSpec is the central authoring contract of this repo (see
- * ../CONTEXT.md). v4.3 is the authoring shape; v4.2 funnels[] is the canonical
- * internal shape that rules operate on (after normalize()).
+ * ../CONTEXT.md). v5.0 is the authoring shape; funnels[] is the canonical
+ * internal shape that rules operate on (after normalize(), which upgrades a
+ * v4.2/v4.3 spec to the v5 page vocabulary — see checkout-flow.ts).
  *
  * Types here are intentionally permissive on optional fields — the rule
  * registry catches missing/malformed fields, rather than the type system
@@ -63,7 +64,23 @@ export type PageType = 'presell' | 'landing'
  * Not to be confused with the page ID "select", which several family
  * contracts use for this page and which is a separate namespace.
  */
- | 'select' | 'checkout' | 'upsell' | 'downsell' | 'thankyou';
+ | 'select'
+/**
+ * A page with a checkout form that collects details and moves on without
+ * placing an order: the information and shipping steps of a split checkout
+ * (campaigns-os#641). Routes forward through `next_page`; it takes no
+ * payment, so `success_url` and `on_accept` are ignored here as on `select`.
+ * Renders as SDK page type `checkout`; its form carries
+ * `data-next-checkout-step` and `data-next-step-number`.
+ */
+ | 'checkout_step'
+/**
+ * The page that takes payment. Exactly one on every path from an entry page
+ * to an upsell. Routes forward through `success_url` (or `next_page`) to an
+ * upsell, downsell or thank-you page. A campaign may hold several, one per
+ * path.
+ */
+ | 'checkout' | 'upsell' | 'downsell' | 'thankyou';
 /**
  * Offer condition/benefit blocks, as exported by the Map Builder. Both share
  * the { type, value, description } shape (e.g. condition

package/campaign-spec/dist/types.js

@@ -2,8 +2,9 @@
  * Type surface for the CampaignSpec contract layer.
  *
  * The CampaignSpec is the central authoring contract of this repo (see
- * ../CONTEXT.md). v4.3 is the authoring shape; v4.2 funnels[] is the canonical
- * internal shape that rules operate on (after normalize()).
+ * ../CONTEXT.md). v5.0 is the authoring shape; funnels[] is the canonical
+ * internal shape that rules operate on (after normalize(), which upgrades a
+ * v4.2/v4.3 spec to the v5 page vocabulary — see checkout-flow.ts).
  *
  * Types here are intentionally permissive on optional fields — the rule
  * registry catches missing/malformed fields, rather than the type system

package/compatibility.json

@@ -1,9 +1,9 @@
 {
   "package": "@nextcommerce/campaigns-os",
-  "version": "1.54.0",
+  "version": "1.57.0",
   "status": "developer-preview",
   "contracts": {
-    "campaign_spec": "4.2-4.3",
+    "campaign_spec": "4.2-5.0",
     "build_packet": "campaign-runtime-build-packet/v0",
     "build_context": "campaign-runtime-build-context/v0",
     "assembly_report": "campaign-runtime-assembly-report/v0",

package/contracts/fixtures/runtime-recipe/accept/current.json

@@ -3,7 +3,7 @@
   "_growth_note": "When a bound below is genuinely reached, the answer is to find out why before raising it. A dependency install that exceeds its bound on a warm machine is a supply-chain change, not a slow morning; an output inventory that exceeds its file or byte bound is a build that went wrong, not a package that grew 50x overnight. Raising a bound is the fallback, it advances recipe_revision, and it owes a release-ledger entry. Widening the accepted npm range follows the same path, and its trigger is external and checkable: widen when a Node release line ships that npm major by default, not when a particular machine happens to have it installed.",
   "schema": "campaigns-os-runtime-recipe/v1",
   "recipe_kind": "campaigns-os-node-v1",
-  "recipe_revision": "1.0.2",
+  "recipe_revision": "1.0.3",
   "refusal_reason_code": "runtime_recipe_refused",
   "fail_closed": true,
   "unperformable_check_disposition": "failed",
@@ -106,6 +106,7 @@
     "fingerprint_algorithm": "sha256",
     "files": [
       "campaign-spec/analytics-vocabulary.ts",
+      "campaign-spec/checkout-flow.ts",
       "campaign-spec/index.ts",
       "campaign-spec/normalize.ts",
       "campaign-spec/package.json",
@@ -113,7 +114,9 @@
       "campaign-spec/rules/analytics-contract-shape.ts",
       "campaign-spec/rules/assembly-hints-shape.ts",
       "campaign-spec/rules/campaign-metadata.ts",
+      "campaign-spec/rules/checkout-forward-target.ts",
       "campaign-spec/rules/checkout-has-success-url.ts",
+      "campaign-spec/rules/checkout-step-reaches-checkout.ts",
       "campaign-spec/rules/cycle-detection.ts",
       "campaign-spec/rules/design-source-shape.ts",
       "campaign-spec/rules/downsell-without-upsell.ts",
@@ -124,9 +127,11 @@
       "campaign-spec/rules/funnel-weight-sum.ts",
       "campaign-spec/rules/index.ts",
       "campaign-spec/rules/offer-ref-integrity.ts",
+      "campaign-spec/rules/one-checkout-per-path.ts",
       "campaign-spec/rules/package-pricing-sanity.ts",
       "campaign-spec/rules/page-count.ts",
       "campaign-spec/rules/page-id-uniqueness.ts",
+      "campaign-spec/rules/pre-payment-forward-target.ts",
       "campaign-spec/rules/promo-code-input-validation.ts",
       "campaign-spec/rules/promo-codes-shape.ts",
       "campaign-spec/rules/route-field-ignored-for-page-type.ts",

package/contracts/fixtures/runtime-recipe/accept/minimal.json

@@ -1,7 +1,7 @@
 {
   "schema": "campaigns-os-runtime-recipe/v1",
   "recipe_kind": "campaigns-os-node-v1",
-  "recipe_revision": "1.0.2",
+  "recipe_revision": "1.0.3",
   "refusal_reason_code": "runtime_recipe_refused",
   "fail_closed": true,
   "unperformable_check_disposition": "failed",
@@ -101,6 +101,7 @@
     "fingerprint_algorithm": "sha256",
     "files": [
       "campaign-spec/analytics-vocabulary.ts",
+      "campaign-spec/checkout-flow.ts",
       "campaign-spec/index.ts",
       "campaign-spec/normalize.ts",
       "campaign-spec/package.json",
@@ -108,7 +109,9 @@
       "campaign-spec/rules/analytics-contract-shape.ts",
       "campaign-spec/rules/assembly-hints-shape.ts",
       "campaign-spec/rules/campaign-metadata.ts",
+      "campaign-spec/rules/checkout-forward-target.ts",
       "campaign-spec/rules/checkout-has-success-url.ts",
+      "campaign-spec/rules/checkout-step-reaches-checkout.ts",
       "campaign-spec/rules/cycle-detection.ts",
       "campaign-spec/rules/design-source-shape.ts",
       "campaign-spec/rules/downsell-without-upsell.ts",
@@ -119,9 +122,11 @@
       "campaign-spec/rules/funnel-weight-sum.ts",
       "campaign-spec/rules/index.ts",
       "campaign-spec/rules/offer-ref-integrity.ts",
+      "campaign-spec/rules/one-checkout-per-path.ts",
       "campaign-spec/rules/package-pricing-sanity.ts",
       "campaign-spec/rules/page-count.ts",
       "campaign-spec/rules/page-id-uniqueness.ts",
+      "campaign-spec/rules/pre-payment-forward-target.ts",
       "campaign-spec/rules/promo-code-input-validation.ts",
       "campaign-spec/rules/promo-codes-shape.ts",
       "campaign-spec/rules/route-field-ignored-for-page-type.ts",

package/contracts/fixtures/runtime-recipe/dist-states.json

@@ -2,7 +2,7 @@
   "_note": "Declarative descriptions of the prepared-runtime states an output-check implementation must distinguish. A test builds each state from the accepted recipe rather than from paths written down here, so adding a module to the input set cannot leave a fixture describing an inventory that no longer exists.",
   "schema": "campaigns-os-runtime-recipe-dist-states/v1",
   "directory": "campaign-spec/dist",
-  "expected_file_count": 76,
+  "expected_file_count": 86,
   "states": [
     {
       "id": "healthy",

package/contracts/fixtures/runtime-recipe/reject/advisory-enforcement.json

@@ -3,7 +3,7 @@
   "_growth_note": "When a bound below is genuinely reached, the answer is to find out why before raising it. A dependency install that exceeds its bound on a warm machine is a supply-chain change, not a slow morning; an output inventory that exceeds its file or byte bound is a build that went wrong, not a package that grew 50x overnight. Raising a bound is the fallback, it advances recipe_revision, and it owes a release-ledger entry. Widening the accepted npm range follows the same path, and its trigger is external and checkable: widen when a Node release line ships that npm major by default, not when a particular machine happens to have it installed.",
   "schema": "campaigns-os-runtime-recipe/v1",
   "recipe_kind": "campaigns-os-node-v1",
-  "recipe_revision": "1.0.2",
+  "recipe_revision": "1.0.3",
   "refusal_reason_code": "runtime_recipe_refused",
   "fail_closed": false,
   "unperformable_check_disposition": "failed",
@@ -106,6 +106,7 @@
     "fingerprint_algorithm": "sha256",
     "files": [
       "campaign-spec/analytics-vocabulary.ts",
+      "campaign-spec/checkout-flow.ts",
       "campaign-spec/index.ts",
       "campaign-spec/normalize.ts",
       "campaign-spec/package.json",
@@ -113,7 +114,9 @@
       "campaign-spec/rules/analytics-contract-shape.ts",
       "campaign-spec/rules/assembly-hints-shape.ts",
       "campaign-spec/rules/campaign-metadata.ts",
+      "campaign-spec/rules/checkout-forward-target.ts",
       "campaign-spec/rules/checkout-has-success-url.ts",
+      "campaign-spec/rules/checkout-step-reaches-checkout.ts",
       "campaign-spec/rules/cycle-detection.ts",
       "campaign-spec/rules/design-source-shape.ts",
       "campaign-spec/rules/downsell-without-upsell.ts",
@@ -124,9 +127,11 @@
       "campaign-spec/rules/funnel-weight-sum.ts",
       "campaign-spec/rules/index.ts",
       "campaign-spec/rules/offer-ref-integrity.ts",
+      "campaign-spec/rules/one-checkout-per-path.ts",
       "campaign-spec/rules/package-pricing-sanity.ts",
       "campaign-spec/rules/page-count.ts",
       "campaign-spec/rules/page-id-uniqueness.ts",
+      "campaign-spec/rules/pre-payment-forward-target.ts",
       "campaign-spec/rules/promo-code-input-validation.ts",
       "campaign-spec/rules/promo-codes-shape.ts",
       "campaign-spec/rules/route-field-ignored-for-page-type.ts",

package/contracts/fixtures/runtime-recipe/reject/allowlist-without-hosts.json

@@ -3,7 +3,7 @@
   "_growth_note": "When a bound below is genuinely reached, the answer is to find out why before raising it. A dependency install that exceeds its bound on a warm machine is a supply-chain change, not a slow morning; an output inventory that exceeds its file or byte bound is a build that went wrong, not a package that grew 50x overnight. Raising a bound is the fallback, it advances recipe_revision, and it owes a release-ledger entry. Widening the accepted npm range follows the same path, and its trigger is external and checkable: widen when a Node release line ships that npm major by default, not when a particular machine happens to have it installed.",
   "schema": "campaigns-os-runtime-recipe/v1",
   "recipe_kind": "campaigns-os-node-v1",
-  "recipe_revision": "1.0.2",
+  "recipe_revision": "1.0.3",
   "refusal_reason_code": "runtime_recipe_refused",
   "fail_closed": true,
   "unperformable_check_disposition": "failed",
@@ -104,6 +104,7 @@
     "fingerprint_algorithm": "sha256",
     "files": [
       "campaign-spec/analytics-vocabulary.ts",
+      "campaign-spec/checkout-flow.ts",
       "campaign-spec/index.ts",
       "campaign-spec/normalize.ts",
       "campaign-spec/package.json",
@@ -111,7 +112,9 @@
       "campaign-spec/rules/analytics-contract-shape.ts",
       "campaign-spec/rules/assembly-hints-shape.ts",
       "campaign-spec/rules/campaign-metadata.ts",
+      "campaign-spec/rules/checkout-forward-target.ts",
       "campaign-spec/rules/checkout-has-success-url.ts",
+      "campaign-spec/rules/checkout-step-reaches-checkout.ts",
       "campaign-spec/rules/cycle-detection.ts",
       "campaign-spec/rules/design-source-shape.ts",
       "campaign-spec/rules/downsell-without-upsell.ts",
@@ -122,9 +125,11 @@
       "campaign-spec/rules/funnel-weight-sum.ts",
       "campaign-spec/rules/index.ts",
       "campaign-spec/rules/offer-ref-integrity.ts",
+      "campaign-spec/rules/one-checkout-per-path.ts",
       "campaign-spec/rules/package-pricing-sanity.ts",
       "campaign-spec/rules/page-count.ts",
       "campaign-spec/rules/page-id-uniqueness.ts",
+      "campaign-spec/rules/pre-payment-forward-target.ts",
       "campaign-spec/rules/promo-code-input-validation.ts",
       "campaign-spec/rules/promo-codes-shape.ts",
       "campaign-spec/rules/route-field-ignored-for-page-type.ts",

package/contracts/fixtures/runtime-recipe/reject/committed-output-claim.json

@@ -3,7 +3,7 @@
   "_growth_note": "When a bound below is genuinely reached, the answer is to find out why before raising it. A dependency install that exceeds its bound on a warm machine is a supply-chain change, not a slow morning; an output inventory that exceeds its file or byte bound is a build that went wrong, not a package that grew 50x overnight. Raising a bound is the fallback, it advances recipe_revision, and it owes a release-ledger entry. Widening the accepted npm range follows the same path, and its trigger is external and checkable: widen when a Node release line ships that npm major by default, not when a particular machine happens to have it installed.",
   "schema": "campaigns-os-runtime-recipe/v1",
   "recipe_kind": "campaigns-os-node-v1",
-  "recipe_revision": "1.0.2",
+  "recipe_revision": "1.0.3",
   "refusal_reason_code": "runtime_recipe_refused",
   "fail_closed": true,
   "unperformable_check_disposition": "failed",
@@ -106,6 +106,7 @@
     "fingerprint_algorithm": "sha256",
     "files": [
       "campaign-spec/analytics-vocabulary.ts",
+      "campaign-spec/checkout-flow.ts",
       "campaign-spec/index.ts",
       "campaign-spec/normalize.ts",
       "campaign-spec/package.json",
@@ -113,7 +114,9 @@
       "campaign-spec/rules/analytics-contract-shape.ts",
       "campaign-spec/rules/assembly-hints-shape.ts",
       "campaign-spec/rules/campaign-metadata.ts",
+      "campaign-spec/rules/checkout-forward-target.ts",
       "campaign-spec/rules/checkout-has-success-url.ts",
+      "campaign-spec/rules/checkout-step-reaches-checkout.ts",
       "campaign-spec/rules/cycle-detection.ts",
       "campaign-spec/rules/design-source-shape.ts",
       "campaign-spec/rules/downsell-without-upsell.ts",
@@ -124,9 +127,11 @@
       "campaign-spec/rules/funnel-weight-sum.ts",
       "campaign-spec/rules/index.ts",
       "campaign-spec/rules/offer-ref-integrity.ts",
+      "campaign-spec/rules/one-checkout-per-path.ts",
       "campaign-spec/rules/package-pricing-sanity.ts",
       "campaign-spec/rules/page-count.ts",
       "campaign-spec/rules/page-id-uniqueness.ts",
+      "campaign-spec/rules/pre-payment-forward-target.ts",
       "campaign-spec/rules/promo-code-input-validation.ts",
       "campaign-spec/rules/promo-codes-shape.ts",
       "campaign-spec/rules/route-field-ignored-for-page-type.ts",

package/contracts/fixtures/runtime-recipe/reject/engines-disagreement-warns.json

@@ -3,7 +3,7 @@
   "_growth_note": "When a bound below is genuinely reached, the answer is to find out why before raising it. A dependency install that exceeds its bound on a warm machine is a supply-chain change, not a slow morning; an output inventory that exceeds its file or byte bound is a build that went wrong, not a package that grew 50x overnight. Raising a bound is the fallback, it advances recipe_revision, and it owes a release-ledger entry. Widening the accepted npm range follows the same path, and its trigger is external and checkable: widen when a Node release line ships that npm major by default, not when a particular machine happens to have it installed.",
   "schema": "campaigns-os-runtime-recipe/v1",
   "recipe_kind": "campaigns-os-node-v1",
-  "recipe_revision": "1.0.2",
+  "recipe_revision": "1.0.3",
   "refusal_reason_code": "runtime_recipe_refused",
   "fail_closed": true,
   "unperformable_check_disposition": "failed",
@@ -106,6 +106,7 @@
     "fingerprint_algorithm": "sha256",
     "files": [
       "campaign-spec/analytics-vocabulary.ts",
+      "campaign-spec/checkout-flow.ts",
       "campaign-spec/index.ts",
       "campaign-spec/normalize.ts",
       "campaign-spec/package.json",
@@ -113,7 +114,9 @@
       "campaign-spec/rules/analytics-contract-shape.ts",
       "campaign-spec/rules/assembly-hints-shape.ts",
       "campaign-spec/rules/campaign-metadata.ts",
+      "campaign-spec/rules/checkout-forward-target.ts",
       "campaign-spec/rules/checkout-has-success-url.ts",
+      "campaign-spec/rules/checkout-step-reaches-checkout.ts",
       "campaign-spec/rules/cycle-detection.ts",
       "campaign-spec/rules/design-source-shape.ts",
       "campaign-spec/rules/downsell-without-upsell.ts",
@@ -124,9 +127,11 @@
       "campaign-spec/rules/funnel-weight-sum.ts",
       "campaign-spec/rules/index.ts",
       "campaign-spec/rules/offer-ref-integrity.ts",
+      "campaign-spec/rules/one-checkout-per-path.ts",
       "campaign-spec/rules/package-pricing-sanity.ts",
       "campaign-spec/rules/page-count.ts",
       "campaign-spec/rules/page-id-uniqueness.ts",
+      "campaign-spec/rules/pre-payment-forward-target.ts",
       "campaign-spec/rules/promo-code-input-validation.ts",
       "campaign-spec/rules/promo-codes-shape.ts",
       "campaign-spec/rules/route-field-ignored-for-page-type.ts",

package/contracts/fixtures/runtime-recipe/reject/lifecycle-scripts-enabled.json

@@ -3,7 +3,7 @@
   "_growth_note": "When a bound below is genuinely reached, the answer is to find out why before raising it. A dependency install that exceeds its bound on a warm machine is a supply-chain change, not a slow morning; an output inventory that exceeds its file or byte bound is a build that went wrong, not a package that grew 50x overnight. Raising a bound is the fallback, it advances recipe_revision, and it owes a release-ledger entry. Widening the accepted npm range follows the same path, and its trigger is external and checkable: widen when a Node release line ships that npm major by default, not when a particular machine happens to have it installed.",
   "schema": "campaigns-os-runtime-recipe/v1",
   "recipe_kind": "campaigns-os-node-v1",
-  "recipe_revision": "1.0.2",
+  "recipe_revision": "1.0.3",
   "refusal_reason_code": "runtime_recipe_refused",
   "fail_closed": true,
   "unperformable_check_disposition": "failed",
@@ -106,6 +106,7 @@
     "fingerprint_algorithm": "sha256",
     "files": [
       "campaign-spec/analytics-vocabulary.ts",
+      "campaign-spec/checkout-flow.ts",
       "campaign-spec/index.ts",
       "campaign-spec/normalize.ts",
       "campaign-spec/package.json",
@@ -113,7 +114,9 @@
       "campaign-spec/rules/analytics-contract-shape.ts",
       "campaign-spec/rules/assembly-hints-shape.ts",
       "campaign-spec/rules/campaign-metadata.ts",
+      "campaign-spec/rules/checkout-forward-target.ts",
       "campaign-spec/rules/checkout-has-success-url.ts",
+      "campaign-spec/rules/checkout-step-reaches-checkout.ts",
       "campaign-spec/rules/cycle-detection.ts",
       "campaign-spec/rules/design-source-shape.ts",
       "campaign-spec/rules/downsell-without-upsell.ts",
@@ -124,9 +127,11 @@
       "campaign-spec/rules/funnel-weight-sum.ts",
       "campaign-spec/rules/index.ts",
       "campaign-spec/rules/offer-ref-integrity.ts",
+      "campaign-spec/rules/one-checkout-per-path.ts",
       "campaign-spec/rules/package-pricing-sanity.ts",
       "campaign-spec/rules/page-count.ts",
       "campaign-spec/rules/page-id-uniqueness.ts",
+      "campaign-spec/rules/pre-payment-forward-target.ts",
       "campaign-spec/rules/promo-code-input-validation.ts",
       "campaign-spec/rules/promo-codes-shape.ts",
       "campaign-spec/rules/route-field-ignored-for-page-type.ts",

package/contracts/fixtures/runtime-recipe/reject/missing-required-field.json

@@ -3,7 +3,7 @@
   "_growth_note": "When a bound below is genuinely reached, the answer is to find out why before raising it. A dependency install that exceeds its bound on a warm machine is a supply-chain change, not a slow morning; an output inventory that exceeds its file or byte bound is a build that went wrong, not a package that grew 50x overnight. Raising a bound is the fallback, it advances recipe_revision, and it owes a release-ledger entry. Widening the accepted npm range follows the same path, and its trigger is external and checkable: widen when a Node release line ships that npm major by default, not when a particular machine happens to have it installed.",
   "schema": "campaigns-os-runtime-recipe/v1",
   "recipe_kind": "campaigns-os-node-v1",
-  "recipe_revision": "1.0.2",
+  "recipe_revision": "1.0.3",
   "refusal_reason_code": "runtime_recipe_refused",
   "fail_closed": true,
   "unperformable_check_disposition": "failed",

package/contracts/fixtures/runtime-recipe/reject/unknown-kind.json

@@ -3,7 +3,7 @@
   "_growth_note": "When a bound below is genuinely reached, the answer is to find out why before raising it. A dependency install that exceeds its bound on a warm machine is a supply-chain change, not a slow morning; an output inventory that exceeds its file or byte bound is a build that went wrong, not a package that grew 50x overnight. Raising a bound is the fallback, it advances recipe_revision, and it owes a release-ledger entry. Widening the accepted npm range follows the same path, and its trigger is external and checkable: widen when a Node release line ships that npm major by default, not when a particular machine happens to have it installed.",
   "schema": "campaigns-os-runtime-recipe/v1",
   "recipe_kind": "campaigns-os-node-v2",
-  "recipe_revision": "1.0.2",
+  "recipe_revision": "1.0.3",
   "refusal_reason_code": "runtime_recipe_refused",
   "fail_closed": true,
   "unperformable_check_disposition": "failed",
@@ -106,6 +106,7 @@
     "fingerprint_algorithm": "sha256",
     "files": [
       "campaign-spec/analytics-vocabulary.ts",
+      "campaign-spec/checkout-flow.ts",
       "campaign-spec/index.ts",
       "campaign-spec/normalize.ts",
       "campaign-spec/package.json",
@@ -113,7 +114,9 @@
       "campaign-spec/rules/analytics-contract-shape.ts",
       "campaign-spec/rules/assembly-hints-shape.ts",
       "campaign-spec/rules/campaign-metadata.ts",
+      "campaign-spec/rules/checkout-forward-target.ts",
       "campaign-spec/rules/checkout-has-success-url.ts",
+      "campaign-spec/rules/checkout-step-reaches-checkout.ts",
       "campaign-spec/rules/cycle-detection.ts",
       "campaign-spec/rules/design-source-shape.ts",
       "campaign-spec/rules/downsell-without-upsell.ts",
@@ -124,9 +127,11 @@
       "campaign-spec/rules/funnel-weight-sum.ts",
       "campaign-spec/rules/index.ts",
       "campaign-spec/rules/offer-ref-integrity.ts",
+      "campaign-spec/rules/one-checkout-per-path.ts",
       "campaign-spec/rules/package-pricing-sanity.ts",
       "campaign-spec/rules/page-count.ts",
       "campaign-spec/rules/page-id-uniqueness.ts",
+      "campaign-spec/rules/pre-payment-forward-target.ts",
       "campaign-spec/rules/promo-code-input-validation.ts",
       "campaign-spec/rules/promo-codes-shape.ts",
       "campaign-spec/rules/route-field-ignored-for-page-type.ts",

package/contracts/fixtures/runtime-recipe/reject/unknown-network-policy.json

@@ -3,7 +3,7 @@
   "_growth_note": "When a bound below is genuinely reached, the answer is to find out why before raising it. A dependency install that exceeds its bound on a warm machine is a supply-chain change, not a slow morning; an output inventory that exceeds its file or byte bound is a build that went wrong, not a package that grew 50x overnight. Raising a bound is the fallback, it advances recipe_revision, and it owes a release-ledger entry. Widening the accepted npm range follows the same path, and its trigger is external and checkable: widen when a Node release line ships that npm major by default, not when a particular machine happens to have it installed.",
   "schema": "campaigns-os-runtime-recipe/v1",
   "recipe_kind": "campaigns-os-node-v1",
-  "recipe_revision": "1.0.2",
+  "recipe_revision": "1.0.3",
   "refusal_reason_code": "runtime_recipe_refused",
   "fail_closed": true,
   "unperformable_check_disposition": "failed",
@@ -106,6 +106,7 @@
     "fingerprint_algorithm": "sha256",
     "files": [
       "campaign-spec/analytics-vocabulary.ts",
+      "campaign-spec/checkout-flow.ts",
       "campaign-spec/index.ts",
       "campaign-spec/normalize.ts",
       "campaign-spec/package.json",
@@ -113,7 +114,9 @@
       "campaign-spec/rules/analytics-contract-shape.ts",
       "campaign-spec/rules/assembly-hints-shape.ts",
       "campaign-spec/rules/campaign-metadata.ts",
+      "campaign-spec/rules/checkout-forward-target.ts",
       "campaign-spec/rules/checkout-has-success-url.ts",
+      "campaign-spec/rules/checkout-step-reaches-checkout.ts",
       "campaign-spec/rules/cycle-detection.ts",
       "campaign-spec/rules/design-source-shape.ts",
       "campaign-spec/rules/downsell-without-upsell.ts",
@@ -124,9 +127,11 @@
       "campaign-spec/rules/funnel-weight-sum.ts",
       "campaign-spec/rules/index.ts",
       "campaign-spec/rules/offer-ref-integrity.ts",
+      "campaign-spec/rules/one-checkout-per-path.ts",
       "campaign-spec/rules/package-pricing-sanity.ts",
       "campaign-spec/rules/page-count.ts",
       "campaign-spec/rules/page-id-uniqueness.ts",
+      "campaign-spec/rules/pre-payment-forward-target.ts",
       "campaign-spec/rules/promo-code-input-validation.ts",
       "campaign-spec/rules/promo-codes-shape.ts",
       "campaign-spec/rules/route-field-ignored-for-page-type.ts",

package/contracts/fixtures/runtime-recipe/reject/unknown-output-check.json

@@ -3,7 +3,7 @@
   "_growth_note": "When a bound below is genuinely reached, the answer is to find out why before raising it. A dependency install that exceeds its bound on a warm machine is a supply-chain change, not a slow morning; an output inventory that exceeds its file or byte bound is a build that went wrong, not a package that grew 50x overnight. Raising a bound is the fallback, it advances recipe_revision, and it owes a release-ledger entry. Widening the accepted npm range follows the same path, and its trigger is external and checkable: widen when a Node release line ships that npm major by default, not when a particular machine happens to have it installed.",
   "schema": "campaigns-os-runtime-recipe/v1",
   "recipe_kind": "campaigns-os-node-v1",
-  "recipe_revision": "1.0.2",
+  "recipe_revision": "1.0.3",
   "refusal_reason_code": "runtime_recipe_refused",
   "fail_closed": true,
   "unperformable_check_disposition": "failed",
@@ -106,6 +106,7 @@
     "fingerprint_algorithm": "sha256",
     "files": [
       "campaign-spec/analytics-vocabulary.ts",
+      "campaign-spec/checkout-flow.ts",
       "campaign-spec/index.ts",
       "campaign-spec/normalize.ts",
       "campaign-spec/package.json",
@@ -113,7 +114,9 @@
       "campaign-spec/rules/analytics-contract-shape.ts",
       "campaign-spec/rules/assembly-hints-shape.ts",
       "campaign-spec/rules/campaign-metadata.ts",
+      "campaign-spec/rules/checkout-forward-target.ts",
       "campaign-spec/rules/checkout-has-success-url.ts",
+      "campaign-spec/rules/checkout-step-reaches-checkout.ts",
       "campaign-spec/rules/cycle-detection.ts",
       "campaign-spec/rules/design-source-shape.ts",
       "campaign-spec/rules/downsell-without-upsell.ts",
@@ -124,9 +127,11 @@
       "campaign-spec/rules/funnel-weight-sum.ts",
       "campaign-spec/rules/index.ts",
       "campaign-spec/rules/offer-ref-integrity.ts",
+      "campaign-spec/rules/one-checkout-per-path.ts",
       "campaign-spec/rules/package-pricing-sanity.ts",
       "campaign-spec/rules/page-count.ts",
       "campaign-spec/rules/page-id-uniqueness.ts",
+      "campaign-spec/rules/pre-payment-forward-target.ts",
       "campaign-spec/rules/promo-code-input-validation.ts",
       "campaign-spec/rules/promo-codes-shape.ts",
       "campaign-spec/rules/route-field-ignored-for-page-type.ts",

package/contracts/fixtures/runtime-recipe/reject/unknown-revision.json

@@ -106,6 +106,7 @@
     "fingerprint_algorithm": "sha256",
     "files": [
       "campaign-spec/analytics-vocabulary.ts",
+      "campaign-spec/checkout-flow.ts",
       "campaign-spec/index.ts",
       "campaign-spec/normalize.ts",
       "campaign-spec/package.json",
@@ -113,7 +114,9 @@
       "campaign-spec/rules/analytics-contract-shape.ts",
       "campaign-spec/rules/assembly-hints-shape.ts",
       "campaign-spec/rules/campaign-metadata.ts",
+      "campaign-spec/rules/checkout-forward-target.ts",
       "campaign-spec/rules/checkout-has-success-url.ts",
+      "campaign-spec/rules/checkout-step-reaches-checkout.ts",
       "campaign-spec/rules/cycle-detection.ts",
       "campaign-spec/rules/design-source-shape.ts",
       "campaign-spec/rules/downsell-without-upsell.ts",
@@ -124,9 +127,11 @@
       "campaign-spec/rules/funnel-weight-sum.ts",
       "campaign-spec/rules/index.ts",
       "campaign-spec/rules/offer-ref-integrity.ts",
+      "campaign-spec/rules/one-checkout-per-path.ts",
       "campaign-spec/rules/package-pricing-sanity.ts",
       "campaign-spec/rules/page-count.ts",
       "campaign-spec/rules/page-id-uniqueness.ts",
+      "campaign-spec/rules/pre-payment-forward-target.ts",
       "campaign-spec/rules/promo-code-input-validation.ts",
       "campaign-spec/rules/promo-codes-shape.ts",
       "campaign-spec/rules/route-field-ignored-for-page-type.ts",