@nextcommerce/campaigns-os 1.46.0 → 1.47.0

package/contracts/effects.v1.json

@@ -4486,7 +4486,7 @@
       ],
       "effect_test": "effects: start --force",
       "test_scope": "full",
-      "notes": "DESTRUCTIVE: --force overwrites an assembly report that carries stage evidence, printing the stage keys it cleared. This is the flag that makes `start` destructive; the base form refuses instead."
+      "notes": "DESTRUCTIVE: --force overwrites an assembly report that carries stage evidence, printing the stage keys it cleared. This is the flag that makes `start` destructive; the base form refuses instead. It also regenerates a stale Design Source Package that this intake synthesized itself: the previous Assembly Report records origin \"synthesized\" and the package bytes still match it. An adopted or hand-edited package is never replaced. The declared writes already cover that path."
     },
     {
       "command": "start",
@@ -4998,7 +4998,7 @@
       ],
       "effect_test": "effects: prepare-build --force",
       "test_scope": "full",
-      "notes": "DESTRUCTIVE: --force overwrites an assembly report that carries stage evidence, printing the stage keys it cleared. This is the flag that makes `prepare-build` destructive; the base form refuses instead. Everything else it writes is the base form's intake."
+      "notes": "DESTRUCTIVE: --force overwrites an assembly report that carries stage evidence, printing the stage keys it cleared. This is the flag that makes `prepare-build` destructive; the base form refuses instead. It also regenerates a stale Design Source Package that this intake synthesized itself: the previous Assembly Report records origin \"synthesized\" and the package bytes still match it. An adopted or hand-edited package is never replaced. The declared writes already cover that path. Everything else it writes is the base form's intake."
     },
     {
       "command": "build",
@@ -5412,7 +5412,7 @@
       ],
       "effect_test": "effects: build --force",
       "test_scope": "full",
-      "notes": "DESTRUCTIVE: --force overwrites an assembly report that carries stage evidence, printing the stage keys it cleared. This is the flag that makes `build` destructive; the base form refuses instead. Everything else it writes is the base form's intake."
+      "notes": "DESTRUCTIVE: --force overwrites an assembly report that carries stage evidence, printing the stage keys it cleared. This is the flag that makes `build` destructive; the base form refuses instead. It also regenerates a stale Design Source Package that this intake synthesized itself: the previous Assembly Report records origin \"synthesized\" and the package bytes still match it. An adopted or hand-edited package is never replaced. The declared writes already cover that path. Everything else it writes is the base form's intake."
     },
     {
       "command": "spec",

package/contracts/release-ledger.json

@@ -3828,6 +3828,344 @@
         }
       ],
       "entry_sha256": "5c5b4362711e980c81eab5e1b643c42de1d8bfd74684dd73596f036925bfbeef"
+    },
+    {
+      "id": "RL-0191",
+      "sequence": 183,
+      "date": "2026-10-01",
+      "kind": "release",
+      "surface_version": null,
+      "changelog_section": "1.46.0+agent.4",
+      "changelog_sha256": "894c809bfbd9a3345cd56d5ff7664730b9fc3035ee9181f735dae1527f975e2b",
+      "agent_impact": "Skill text only. The next-campaigns-qa and next-campaigns-build skills now state that a required checkout field bound only on a type=\"hidden\" input, a disabled control, a read-only input or read-only textarea, or an aria-disabled=\"true\" control does not count as bound for browser-commerce-structure, and QA reports it in fields_bound.missing. Bundled skills carry revision 1.46.0+skills.2: an agent that loaded 1.46.0+skills.1 text should start a fresh session. QA behaviour is unchanged.",
+      "compatibility": "compatible",
+      "migration": "none",
+      "changes": [
+        {
+          "class": "named_surface",
+          "path": "docs/skills-revision.md",
+          "surface_entry": "docs/skills-revision.md",
+          "summary": "Use the current 1.46.0+skills.2 bundle in executable examples."
+        },
+        {
+          "class": "skill",
+          "path": "skills.json",
+          "surface_entry": "skills.json",
+          "summary": "Advance the bundled skill revision to 1.46.0+skills.2 and each skill version one patch."
+        },
+        {
+          "class": "skill",
+          "path": "skills/campaign-lifecycle-orientation/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.46.0+skills.2 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/campaign-readback-classification/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.46.0+skills.2 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/campaign-run-evidence/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.46.0+skills.2 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/contribution-intake/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.46.0+skills.2 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/next-campaigns-build/SKILL.md",
+          "surface_entry": null,
+          "summary": "State that a checkout field bound only on a hidden, disabled, read-only or aria-disabled control does not count as bound for QA; publish the 1.46.0+skills.2 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/next-campaigns-os-setup/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.46.0+skills.2 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/next-campaigns-os/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.46.0+skills.2 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/next-campaigns-polish/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.46.0+skills.2 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/next-campaigns-qa/SKILL.md",
+          "surface_entry": null,
+          "summary": "State that a required checkout field bound only on a hidden, disabled, read-only or aria-disabled control is not bound and is reported in fields_bound.missing; publish the 1.46.0+skills.2 bundle revision."
+        }
+      ],
+      "entry_sha256": "8e891f36ce261c325f0837bf4c37ca145f60dbdd3ef55ab0ac9c4c4f3f92de7c"
+    },
+    {
+      "id": "RL-0192",
+      "sequence": 184,
+      "date": "2026-10-01",
+      "kind": "release",
+      "surface_version": null,
+      "changelog_section": "1.46.0+agent.5",
+      "changelog_sha256": "16cbe0246a154be864bf97c671e3f82d4118aa8d7ed64722168fb756492c69a7",
+      "agent_impact": "doctor no longer reports built_output.sdk_markup.checkout_bump_is_upsell. A selected checkout order bump is a line item on the checkout order; data-next-is-upsell=\"true\" tags that line as an upsell so platform order reports show upsell items apart from core items, and that is the intended default. Do not remove the attribute, and do not advise anyone to: it would report the bump as a core item. A bump include opts out with is_upsell: false. A run that recorded the warning under an earlier version can disregard it.",
+      "compatibility": "compatible",
+      "migration": "none",
+      "changes": [
+        {
+          "class": "cli_surface",
+          "path": "src/doctor/checks.mjs",
+          "surface_entry": "doctor",
+          "summary": "Stop passing each built page type to the SDK markup check, which no longer reads it now that built_output.sdk_markup.checkout_bump_is_upsell is retired."
+        }
+      ],
+      "entry_sha256": "5f833a760aad0eada255118b29c4b2098fff4bfa4d364d31be121e7655a135ef"
+    },
+    {
+      "id": "RL-0193",
+      "sequence": 185,
+      "date": "2026-10-01",
+      "kind": "amendment",
+      "amends": "RL-0187",
+      "amendment_reason": "RL-0187 and its 1.45.0+agent.5 section told users to remove data-next-is-upsell=\"true\" from checkout bump includes. Tagging a checkout bump line as an upsell is the intended default, so order reports separate upsell items from core items; removing the attribute would report the bump as a core item. The section now says the advice was wrong and that the warning is retired in 1.46.0+agent.5; this amendment carries the corrected section hash.",
+      "surface_version": null,
+      "changelog_section": "1.45.0+agent.5",
+      "changelog_sha256": "74564091423695f83383d296ce664656bc84cb9d21f7f044daffc0315d87110e",
+      "agent_impact": "Disregard RL-0187's advice to remove data-next-is-upsell=\"true\" from a checkout bump. The upsell tag on the bump line is the intended default and the warning that recommended removing it is retired (RL-0192). RL-0187's theme generate and brand-theme-bridge changes stand.",
+      "compatibility": "compatible",
+      "migration": "none",
+      "changes": [
+        {
+          "class": "cli_surface",
+          "path": null,
+          "surface_entry": "doctor",
+          "summary": "Correct the recorded repair advice for built_output.sdk_markup.checkout_bump_is_upsell: the attribute is intended, and the warning is retired."
+        }
+      ],
+      "entry_sha256": "ba5bdb8718c7b405c7cc60e1129f76ebe10011f099aa151bf893d617cc0c4270"
+    },
+    {
+      "id": "RL-0194",
+      "sequence": 186,
+      "date": "2026-10-01",
+      "kind": "release",
+      "surface_version": null,
+      "changelog_section": "1.46.0+agent.6",
+      "changelog_sha256": "8cb11f8b85a7b9abe6791d75a7b7915491477bbe2d3e2f01dae2fb5ca458943a",
+      "agent_impact": "sdk storage-check now accepts a release manifest whose SDK version is above its supported range, such as Campaign Cart v0.4.40 (range 0.4.38 only). Targets outside the declared range still report unknown; a manifest whose SDK version is below its supported maximum is still refused.",
+      "compatibility": "compatible",
+      "migration": "none",
+      "changes": [
+        {
+          "class": "named_surface",
+          "path": "docs/sdk-storage-compatibility.md",
+          "surface_entry": "docs/sdk-storage-compatibility.md",
+          "summary": "A release manifest covers the range it declares, which may end below its own SDK version; targets outside it report unknown."
+        }
+      ],
+      "entry_sha256": "f064edf5031f8fd36197984145f5cbcfca3efd78a76982d3132e254b81964884"
+    },
+    {
+      "id": "RL-0195",
+      "sequence": 187,
+      "date": "2026-10-01",
+      "kind": "release",
+      "surface_version": null,
+      "changelog_section": "1.46.0+agent.8",
+      "changelog_sha256": "c3aa9f4e74bac6c2dbeb05fea5bf7da84bebdb556244c7aafe8481a4248149e6",
+      "agent_impact": "Install next-campaign-page-kit without --save-dev: the documented setup command now installs it with --save-exact as a runtime dependency and the toolkit with --save-dev --save-exact. tooling setup warns, and still proceeds, when page-kit is declared only in devDependencies.",
+      "compatibility": "compatible",
+      "migration": "none",
+      "changes": [
+        {
+          "class": "named_surface",
+          "path": "docs/local-setup.md",
+          "surface_entry": "docs/local-setup.md",
+          "summary": "Split the copy-paste install so page-kit is installed with --save-exact and stays in dependencies, while the toolkit keeps --save-dev --save-exact; note the setup warning for a dev-only page-kit."
+        }
+      ],
+      "entry_sha256": "d13bc2cf8c66ea894b8929b103455153e2a7465e316e71d817ac310aabd58526"
+    },
+    {
+      "id": "RL-0196",
+      "sequence": 188,
+      "date": "2026-10-01",
+      "kind": "release",
+      "surface_version": null,
+      "changelog_section": "1.46.0+agent.9",
+      "changelog_sha256": "6e2850725b14b051323f4a75652c02536ca7aafcd6771d317a07614fae6f6b4b",
+      "agent_impact": "When qa run analytics parity picks its candidate automatically (no --analytics-candidate) and that page is not a receipt, a missing Purchase is now analytics-parity:purchase-present MANUAL_REVIEW/WARN with evidence.page_mismatch, not a blocker. Read page_mismatch and pass the candidate receipt with --analytics-candidate to compare Purchase. An explicit candidate still blocks on a missing Purchase.",
+      "compatibility": "compatible",
+      "migration": "none",
+      "changes": [
+        {
+          "class": "named_surface",
+          "path": "docs/qa-and-test-orders.md",
+          "surface_entry": "docs/qa-and-test-orders.md",
+          "summary": "Describe how the automatic parity candidate reports purchase-present when it is not a receipt page, and the page_mismatch evidence."
+        }
+      ],
+      "entry_sha256": "044a9de53405d944e05045dc62f6f4575b0ebe387225b176904bdd8b02ddcf09"
+    },
+    {
+      "id": "RL-0197",
+      "sequence": 189,
+      "date": "2026-10-01",
+      "kind": "release",
+      "surface_version": null,
+      "changelog_section": "1.46.0+agent.11",
+      "changelog_sha256": "28896ab18e07b78d21437c9b397dee67adb8bbc7791bb53ed1507113d638c5e1",
+      "agent_impact": "Doctor's script syntax gate gives one built_output.script_syntax.missing_script warning per resolved URL, not per raw src spelling. A <script> left unclosed at end of file is no longer parsed by doctor or QA and cannot block; doctor warns under built_output.script_syntax.unclosed_script. A script symlink resolving outside the site root is not read; doctor warns under built_output.script_syntax.symlink_outside_site and lists it in scripts_outside_site[]. Symlinks inside the site root are read as before.",
+      "compatibility": "additive",
+      "migration": "none",
+      "changes": [
+        {
+          "class": "named_surface",
+          "path": "docs/build-packet.md",
+          "surface_entry": "docs/build-packet.md",
+          "summary": "The script syntax gate section records resolved-URL grouping of missing-script warnings, the unclosed-script rule and warning, and the symlink rule: followed inside the site root, warned about and not read outside it."
+        }
+      ],
+      "entry_sha256": "9320297f8b6ea5866e56063b8dc4a364025e15d8963207d43e72396bd7eaf13b"
+    },
+    {
+      "id": "RL-0198",
+      "sequence": 190,
+      "date": "2026-10-01",
+      "kind": "release",
+      "surface_version": "1.47.0",
+      "changelog_section": "1.47.0",
+      "changelog_sha256": "e8ea6bd06d018dd35b8f154c05e395034be3fb6a5476ab17ae00e511fabe16b8",
+      "agent_impact": "Surface 1.47.0. The effects contract's --force notes on start, prepare-build and build now name the regeneration of a stale Design Source Package the intake synthesized itself (writes unchanged). compatibility.json names the package version, guarded by a test. Bundled skills carry revision 1.47.0+skills.1 with unchanged text: an agent that loaded 1.46.0+skills.2 should start a fresh session. Install the 1.47.0 package with the documented local setup command.",
+      "compatibility": "compatible",
+      "migration": "none",
+      "changes": [
+        {
+          "class": "compatibility_policy",
+          "path": "compatibility.json",
+          "surface_entry": null,
+          "summary": "Name the package version (1.47.0) instead of the stale 1.34.0."
+        },
+        {
+          "class": "compatibility_policy",
+          "path": "contracts/effects.v1.json",
+          "surface_entry": "contracts/effects.v1.json",
+          "summary": "Name the regeneration of a stale self-synthesized Design Source Package in the --force notes of start, prepare-build and build."
+        },
+        {
+          "class": "compatibility_policy",
+          "path": "contracts/supported-surface.json",
+          "surface_entry": "contracts/supported-surface.json",
+          "summary": "Advance the supported surface to 1.47.0 and refresh the effects contract hash."
+        },
+        {
+          "class": "named_surface",
+          "path": "docs/local-setup.md",
+          "surface_entry": "docs/local-setup.md",
+          "summary": "Pin the local setup install command to the 1.47.0 package."
+        },
+        {
+          "class": "documentation",
+          "path": "docs/orientation-contract-reference.md",
+          "surface_entry": "docs/orientation-contract-reference.md",
+          "summary": "Regenerate the orientation reference for surface 1.47.0."
+        },
+        {
+          "class": "named_surface",
+          "path": "docs/runtime-readiness.md",
+          "surface_entry": "docs/runtime-readiness.md",
+          "summary": "Regenerate the runtime readiness reference for surface 1.47.0."
+        },
+        {
+          "class": "named_surface",
+          "path": "docs/skills-revision.md",
+          "surface_entry": "docs/skills-revision.md",
+          "summary": "Use the current 1.47.0+skills.1 bundle in executable examples."
+        },
+        {
+          "class": "generated_runtime",
+          "path": "package-lock.json",
+          "surface_entry": null,
+          "summary": "Update release metadata for 1.47.0."
+        },
+        {
+          "class": "package_export",
+          "path": "package.json",
+          "surface_entry": null,
+          "summary": "Release 1.47.0."
+        },
+        {
+          "class": "skill",
+          "path": "skills.json",
+          "surface_entry": "skills.json",
+          "summary": "Advance the bundled skill revision to 1.47.0+skills.1 and each skill version one patch."
+        },
+        {
+          "class": "skill",
+          "path": "skills/campaign-lifecycle-orientation/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.47.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/campaign-readback-classification/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.47.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/campaign-run-evidence/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.47.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/contribution-intake/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.47.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/next-campaigns-build/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.47.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/next-campaigns-os-setup/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.47.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/next-campaigns-os/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.47.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/next-campaigns-polish/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.47.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/next-campaigns-qa/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.47.0+skills.1 bundle revision."
+        }
+      ],
+      "entry_sha256": "cc03e502869034a55209958ac02cce0c2b637b12e3e678646c93cfc7aa3a4eeb"
     }
   ]
 }

package/contracts/supported-surface.json

@@ -1,6 +1,6 @@
 {
   "_note": "The downstream contract manifest. Everything listed here is SUPPORTED SURFACE: consumers (campaigns-agent, campaign-builder, the private ops repo, page-kit campaign repos) may depend on it, and changing it is a deliberate act — hashed entries require a surface_version bump in the same change (check-supported-surface.mjs --base, mirroring the skills.json bump gate), named entries must keep existing at their path, cli_commands must keep resolving in the CLI dispatch, package_exports must stay exported, and every entry must ship in the npm pack (files[] coverage). Anything NOT listed here — src/** internals, scripts/** checkers, examples/**, prompts/**, contracts/** other than this file and the entries named[] below (the orientation contract, the release ledger, and the consumer-facing orientation fixtures) — is implementation: consumers may read it for context but must not build on it, and it can change without notice. Rationale and the compatibility promise: docs/supported-surface.md.",
-  "surface_version": "1.46.0",
+  "surface_version": "1.47.0",
   "package_exports": [
     "./commercial-journey",
     "./commercial-parity",
@@ -120,7 +120,7 @@
       "sha256": "dfc9abed38d456969e47a21f606d308a03bdf036f3466f7d6e47a602747dacf4"
     },
     "contracts/effects.v1.json": {
-      "sha256": "794fe51952685e5afe6eee1988ce0230aae7a15a64fa1efdb350624158796f9c"
+      "sha256": "5f8c6f2f88fc9e0c11c09e265640071d3c1d81fd96c6e05283ed5cfed21d1d59"
     },
     "schemas/campaigns-os-effects.v1.schema.json": {
       "sha256": "3eadd22169ab98bc7c2f682af2751267605170581182158d96be035b0cfe44dc"

package/contracts/template-brand-contract.shared-commerce.v0.json

@@ -55,12 +55,12 @@
       },
       "asset_pin": {
         "repo": "NextCommerceCo/campaign-cart-starter-templates",
-        "sha": "11352c30c596db258679fd3a552b906086b11bb9",
+        "sha": "3793b1de3b77cc31dffe9176f47e8e99ea6134aa",
         "path": "src/<family>/assets/<asset>",
         "note": "asset_sha256 is the sha256 of each shipped starter asset at this commit (the commerce-surface-catalog _synced_from_sha pin; the bytes are identical across every family). A served asset whose bytes hash to the shipped value is the untouched starter asset and counts as residue even though its markup names no method; different bytes mean it was edited in place. check-template-doctrine verifies these hashes against the pinned checkout."
       },
-      "rule": "Remove unless the method is listed in CampaignSpec available_payment_methods / available_express_payment_methods. Template chrome outside the SDK payment-method include counts as implied payment-method residue.",
-      "note": "paypal intentionally has two selectors. QA fails if any selector for an unsupported method remains visible."
+      "rule": "Remove unless the method is listed in CampaignSpec available_payment_methods / available_express_payment_methods. Template chrome outside the SDK payment-method include counts as implied payment-method residue. The starter payment-logos.html row renders one <img data-payment-logo> per method and hides the ones the campaign does not offer, so it needs no removal; when one of its logos is flagged, set payment_flags.show_<method>: false in the page frontmatter instead of deleting markup.",
+      "note": "paypal intentionally has two selectors. QA fails if any selector for an unsupported method remains visible. images/upsell-payment-logos.svg stays listed: the starter still renders it ungated under payment_flags.style: flat and on the olympus-mv-two-step select page."
     }
   },
   "demo_assets": {

package/docs/build-packet.md

@@ -858,15 +858,35 @@ file. A referenced local script that is not in the built output is a warning,
 not a blocker, under `built_output.script_syntax.missing_script`, one warning
 per src naming the pages that load it: the browser gets a 404 for it and
 nothing it would define runs, but whether the page needs it is not known here.
+Missing scripts are grouped by the URL the browser resolves, not the raw src,
+so `check	out.js` and `checkout.js` (the URL parser removes the tab) are one
+warning; the src shown is the first spelling met.
 The src is also listed in `scripts_unresolved[]`. While a parse failure blocks
 the gate, the missing scripts stay on the gate's `warned[]` rather than also
 surfacing as warnings.
 
+A `<script>` the page ends inside, with no `</script>` before end of file, is
+not parsed: the browser never runs a script element whose end tag never
+arrives. Doctor warns about it under `built_output.script_syntax.unclosed_script`,
+one warning per page, because a page that ends mid-script is usually truncated
+output. QA neither fetches nor parses such a script.
+
+**Symlinks under `_site`.** A script that is a symlink, or sits under a
+symlinked directory, is read the way a static server serves it, by following
+the link, as long as its real path stays inside the site root (`_site/`). A
+parse failure in it is reported under the path the page loads. A script whose
+real path resolves outside the site root is not read. Doctor warns, and does
+not block, under `built_output.script_syntax.symlink_outside_site`, naming the
+link (never its target) and saying the target is outside the site root. The
+link is listed in `scripts_outside_site[]` with `file`, `src` and `pages`, not
+in `scripts_unresolved[]`.
+
 The gate's evidence lands beside the other checkpoint gates at
 `derived.checkpoint_gates[]` (`id: built_output.script_syntax`, status `pass` |
 `blocked` | `not_applicable`, `findings[]` with `file`, `line`, `column`,
-`source_type` and `pages`, `warned[]` with `src` and `pages`,
-`scripts_scanned`, `scripts_unresolved[]`, `pages_scanned`). Fixtures: `fixtures/script-syntax/{good,bad}`. It passes, parsing every
+`source_type` and `pages`, `warned[]` with `code`, `src` and `pages` (and
+`file` for a symlink outside the site root), `scripts_scanned`,
+`scripts_unresolved[]`, `scripts_outside_site[]`, `pages_scanned`). Fixtures: `fixtures/script-syntax/{good,bad}`. It passes, parsing every
 local script the pages load and with no missing-script warning, on the
 canonical rendered output of every certified starter family
 (`fixtures/certified-families/`). QA applies the same rule to the page scripts

package/docs/local-setup.md

@@ -3,18 +3,21 @@
 For a new campaign, choose its working folder and run this from that folder:
 
 ```sh
-npm install --save-dev --save-exact @nextcommerce/campaigns-os@1.46.0 next-campaign-page-kit@0.2.0 && npx --no-install campaigns-os tooling setup --target . --platform claude
+npm install --save-exact next-campaign-page-kit@0.2.0 && npm install --save-dev --save-exact @nextcommerce/campaigns-os@1.47.0 && npx --no-install campaigns-os tooling setup --target . --platform claude
 ```
 
 Review the release source/provenance before installation as described in
 `AGENTS.md`. npm installs the dependencies first; `--no-install` then runs only
-the project's installed CLI. Keep `package.json` and `package-lock.json` in
-Git. For an existing project, preserve its reviewed pin: run `npm ci`, then
+the project's installed CLI. Page-kit stays a runtime dependency and the
+toolkit a dev dependency: installing page-kit with `--save-dev` would move it
+out of `dependencies` and break builds that run `npm ci --omit=dev`. Keep
+`package.json` and `package-lock.json` in Git. For an existing project, preserve its reviewed pin: run `npm ci`, then
 `npx --no-install campaigns-os tooling setup --target . --platform claude`
 on a release that supports setup. Changing the pin is a separate update.
 
 Setup checks the exact toolkit pin, its lockfile version and the installed
-page-kit dependency before it changes files. It composes the existing
+page-kit dependency before it changes files, and warns when page-kit is
+declared only in `devDependencies`. It composes the existing
 installers to:
 
 1. Install the QA browser through this toolkit's own Playwright package.

package/docs/orientation-contract-reference.md

@@ -26,7 +26,7 @@ Ledger schema id: `campaigns-os-release-ledger/v1`
 Change policy version: `1.0.0`  
 Reason-code vocabulary version: `1.0.0`  
 Limits version: `1.0.0`  
-Supported surface at generation time: `1.46.0`
+Supported surface at generation time: `1.47.0`
 
 ## Forward compatibility
 

package/docs/qa-and-test-orders.md

@@ -1004,6 +1004,22 @@ the baseline, and when no candidate page is captured the leg emits
 `no_in_scope_page_captured` (skipped) or `no_capture_page_answered`
 (`FAIL`/`BLOCKER`).
 
+The automatic candidate is never a receipt page: the campaign root is not one,
+and a built entry counts as one only when its topology `page_type` is `receipt`
+or `thankyou`. The leg does not substitute the topology's receipt step, because
+a receipt loaded without an order fires no Purchase. So when the automatic
+candidate is not a receipt and fires no Purchase, `purchase-present` is
+`MANUAL_REVIEW`/`WARN` instead of a blocker, and its `evidence.page_mismatch`
+names the mismatch: `reason` (`receipt_baseline_non_receipt_candidate` when the
+baseline fired a Purchase, else `candidate_not_receipt`),
+`baseline_fired_purchase`, `candidate_receipt: false`, `candidate_source`
+(`campaign_root` or `built_entry`) and `candidate_page_type`. To compare
+Purchase, pass the candidate receipt with `--analytics-candidate`. An explicit
+candidate, or an automatic one whose page type is a receipt, still blocks on a
+missing Purchase, and a non-receipt candidate that does fire a Purchase gets the
+full set of Purchase checks, with its page recorded in `evidence.candidate_page`
+on `purchase-present`.
+
 | Flag | Meaning |
 |---|---|
 | `--analytics-baseline <url>` | Legacy funnel URL to capture as the parity baseline (enables the leg) |
@@ -1019,7 +1035,9 @@ Point both at the **thank-you / receipt page** for the highest-value `dl_purchas
 check, or drive the same offer through each funnel so client-fired values line up.
 
 What the diff asserts (BLOCKER unless noted):
-- `purchase-present` — candidate fires a purchase event.
+- `purchase-present` — candidate fires a purchase event (`MANUAL_REVIEW`
+  naming the page mismatch when the automatic candidate is not a receipt and
+  fires none; see above).
 - `purchase-value` / `purchase-currency` — match the baseline's **client-fired**
   value (compared client-vs-client; never vs a backend total, since tax is
   computed backend and is not in the client value on headless checkouts).

package/docs/runtime-readiness.md

@@ -8,7 +8,7 @@
 
 How a checkout of this repository at one commit becomes a usable installed runtime, and how a consumer decides whether a prepared one is still trustworthy. Everything below is generated from `contracts/runtime-recipe.campaigns-os-node-v1.json`, which is the only authority for these values.
 
-Recipe kind `campaigns-os-node-v1`, revision `1.0.2`, validated by `schemas/campaigns-os-runtime-recipe.v1.schema.json` (`Campaigns OS Runtime Recipe v1`). Supported surface at generation time: `1.46.0`.
+Recipe kind `campaigns-os-node-v1`, revision `1.0.2`, validated by `schemas/campaigns-os-runtime-recipe.v1.schema.json` (`Campaigns OS Runtime Recipe v1`). Supported surface at generation time: `1.47.0`.
 
 ## What this is
 

package/docs/sdk-storage-compatibility.md

@@ -8,7 +8,7 @@ npx --no-install campaigns-os sdk storage-check --target . --target-sdk 0.4.38 -
 
 Omit `--json` for the concise human report. Exit 0 means source-compatible; exit 2 means incompatible or unknown; invalid arguments or manifests exit 1. No merchant files or pins are rewritten. This is independent of doctor's built HTML markup check.
 
-The manifest is generated and owned by Campaign Cart, from its storage registry. The scanner has no independent SDK key list and fetches no remote code. Supply `docs/compatibility/storage-migrations.v1.json` from an unmodified checkout of a Campaign Cart release tag, v0.4.40 or later. The report records the full file SHA-256, SDK version, supported target range, registry/extractor/input digest, and Git provenance. When the supplied bytes equal their repository HEAD blob, provenance is `verified-git-blob` with commit and repository path. Proposed, modified, or copied manifests are labeled `unverified-local-file`; the label never certifies a release. Review/pin SDK provenance separately before acting on findings. Targets outside the manifest's supported SDK range report unknown.
+The manifest is generated and owned by Campaign Cart, from its storage registry. The scanner has no independent SDK key list and fetches no remote code. Supply `docs/compatibility/storage-migrations.v1.json` from an unmodified checkout of a Campaign Cart release tag, v0.4.40 or later. The report records the full file SHA-256, SDK version, supported target range, registry/extractor/input digest, and Git provenance. When the supplied bytes equal their repository HEAD blob, provenance is `verified-git-blob` with commit and repository path. Proposed, modified, or copied manifests are labeled `unverified-local-file`; the label never certifies a release. Review/pin SDK provenance separately before acting on findings. A release manifest covers the target range it declares, which may end below its own SDK version: the v0.4.40 manifest, for example, covers 0.4.38 only. Targets outside the manifest's supported SDK range report unknown. A manifest whose SDK version is below its supported maximum is invalid.
 
 `--target` must name the Git root. `--scope` is mandatory: comma-separated literal repository-relative directory/file paths; use `.` only when the complete repository is intended. Add shared JavaScript directories explicitly. `--exclude` uses the same syntax and records explicit exclusions. Archives receive no implicit exemption. Only Git-tracked `.html`, `.htm`, `.js`, `.mjs`, and `.cjs` files in the selected scope are scanned, using current working-tree bytes and per-file digests; untracked files and built dependencies are outside this evidence. A selected HTML page's local script outside the selected files reports unknown. Relative scripts affected by an HTML `<base href>` also report unknown; review their actual dependency paths. Remote SDK and third-party scripts are not fetched or analyzed.
 

package/docs/skills-revision.md

@@ -16,7 +16,7 @@ that the copy on disk moved.
 `skills.json` carries one top-level field:
 
 ```json
-"bundle_revision": "1.46.0+skills.1"
+"bundle_revision": "1.47.0+skills.1"
 ```
 
 The spelling is `<package version>+skills.<n>`:
@@ -25,7 +25,7 @@ The spelling is `<package version>+skills.<n>`:
   skills ship with (`check-skill-versions.mjs` fails if the two disagree);
 - `<n>` is a plain counter, not a semver component. It says "this is the *n*th
   skill-text revision published against that package version" and it **resets
-  with the prefix**. `1.46.0+skills.1` is therefore ahead of `1.40.0+skills.7`.
+  with the prefix**. `1.47.0+skills.1` is therefore ahead of `1.40.0+skills.7`.
 
 It is one identity for the bundle as a whole, on purpose. Per-skill versions
 still exist and still gate per-skill changes, but an agent that loaded one skill
@@ -37,7 +37,7 @@ The first body line of every bundled `SKILL.md`, immediately after the
 frontmatter, is exactly:
 
 ```
-Bundle revision: 1.46.0+skills.1
+Bundle revision: 1.47.0+skills.1
 ```
 
 followed by a short paragraph telling the agent to run the check below at the
@@ -48,7 +48,7 @@ text the agent is actually reading, not from a file it would have to go and open
 ## The check
 
 ```bash
-npx --no-install campaigns-os tooling status --skills-revision 1.46.0+skills.1
+npx --no-install campaigns-os tooling status --skills-revision 1.47.0+skills.1
 ```
 
 The value is compared against the bundle revision of the **CLI the command runs
@@ -90,20 +90,20 @@ reports the choice as `skills.scope` (`requested`, `installed_platforms`, or
 "revision_check": "match",
 "skills_revision": {
   "status": "match",
-  "requested": "1.46.0+skills.1",
+  "requested": "1.47.0+skills.1",
   "spelling": "bundle",
-  "on_disk": "1.46.0+skills.1",
+  "on_disk": "1.47.0+skills.1",
   "on_disk_skill": null,
-  "message": "match (1.46.0+skills.1)"
+  "message": "match (1.47.0+skills.1)"
 }
 ```
 
 The text view prints one named line, as a header above the rest of the status:
 
 ```
-Skills revision: match (1.46.0+skills.1)
-Skills revision: mismatch: loaded 1.39.0+skills.1, on disk 1.46.0+skills.1 — start a fresh session
-Skills revision: unchecked (on disk 1.46.0+skills.1)
+Skills revision: match (1.47.0+skills.1)
+Skills revision: mismatch: loaded 1.39.0+skills.1, on disk 1.47.0+skills.1 — start a fresh session
+Skills revision: unchecked (on disk 1.47.0+skills.1)
 ```
 
 `unchecked` is the state when the flag is absent. It is not an error — an

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nextcommerce/campaigns-os",
-  "version": "1.46.0",
+  "version": "1.47.0",
   "description": "Toolkit for agent-assisted NEXT campaign builds.",
   "license": "Apache-2.0",
   "repository": {

package/skills/campaign-lifecycle-orientation/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: campaign-lifecycle-orientation
-version: 1.0.17
+version: 1.0.19
 description: Orient a reader to the Campaigns OS lifecycle artifacts a run has already emitted, without advancing any stage or changing any state.
 ---
 
-Bundle revision: 1.46.0+skills.1
-Run `npx --no-install campaigns-os tooling status --skills-revision 1.46.0+skills.1`
+Bundle revision: 1.47.0+skills.1
+Run `npx --no-install campaigns-os tooling status --skills-revision 1.47.0+skills.1`
 from the campaign's Page Kit folder, where it runs the project's pinned copy and
 never installs one, at the start of each task. Start a fresh session if it
 reports `mismatch`: this text is already in your context and is never re-read