@nextcommerce/campaigns-os 1.48.0 → 1.50.0

package/contracts/release-ledger.json

@@ -4631,6 +4631,339 @@
         }
       ],
       "entry_sha256": "abc8749936f439d33b92b3bfdc1c954d0b38df24e5a80a2e3862123494b47f07"
+    },
+    {
+      "id": "RL-0208",
+      "sequence": 200,
+      "date": "2026-10-02",
+      "kind": "release",
+      "surface_version": "1.49.0",
+      "changelog_section": "1.49.0",
+      "changelog_sha256": "89c063cc2229b29d161820612d3724a7daecc03c3d1531c0046b503941bd0667",
+      "agent_impact": "Surface 1.49.0. Record an applied brand layer with campaigns-os record theme --packet <p> after record build, instead of editing report.theme by hand: it reads each built commerce page's stylesheet links, requires brand-theme.css (or checkout-brand.css) after next-core.css on every page that loads next-core.css, and writes report.theme (status applied, load_order after-next-core, css_path, commerce_pages, evidence), clearing any earlier theme waiver. Record a local preview with campaigns-os record deploy --packet <p> --base-url <url> after record polish, instead of editing deploy.preview_url and stages.deploy by hand: the URL must be a loopback origin naming the campaign's route root, every built page under it must answer 2xx, and it writes the packet's deploy.preview_url and stages.deploy completed. Both are refused, writing nothing, otherwise. The Build Packet schema now accepts the template families apollo, apollo-mv-single-step, arjuna and karna, so a packet on those families validates. Bundled skills carry revision 1.49.0+skills.1: an agent that loaded 1.48.0+skills.1 should start a fresh session. Install the 1.49.0 package with the documented local setup command.",
+      "compatibility": "additive",
+      "migration": "none",
+      "changes": [
+        {
+          "class": "compatibility_policy",
+          "path": "compatibility.json",
+          "surface_entry": null,
+          "summary": "Name the package version (1.49.0)."
+        },
+        {
+          "class": "compatibility_policy",
+          "path": "contracts/effects.v1.json",
+          "surface_entry": "contracts/effects.v1.json",
+          "summary": "Declare record theme (writes the Assembly Report) and record deploy (writes the Build Packet and the Assembly Report, and requests each built page on the loopback --base-url), each with its --dry-run form, and the doctor sidecar stamp when one is retained."
+        },
+        {
+          "class": "compatibility_policy",
+          "path": "contracts/supported-surface.json",
+          "surface_entry": "contracts/supported-surface.json",
+          "summary": "Advance the supported surface to 1.49.0 and record the effects contract and Build Packet schema hashes."
+        },
+        {
+          "class": "named_surface",
+          "path": "docs/brand-theme-bridge.md",
+          "surface_entry": "docs/brand-theme-bridge.md",
+          "summary": "Record an applied brand layer with record theme, which writes commerce_pages from the built pages that load next-core.css."
+        },
+        {
+          "class": "named_surface",
+          "path": "docs/build-packet.md",
+          "surface_entry": "docs/build-packet.md",
+          "summary": "Add record theme and record deploy to the record command table, name record theme in the starter-palette lane, and name record deploy where the local-serve URL is recorded."
+        },
+        {
+          "class": "named_surface",
+          "path": "docs/qa-and-test-orders.md",
+          "surface_entry": "docs/qa-and-test-orders.md",
+          "summary": "In the local proof sequence, record the served URL with record deploy once polish is recorded."
+        },
+        {
+          "class": "named_surface",
+          "path": "docs/local-setup.md",
+          "surface_entry": "docs/local-setup.md",
+          "summary": "Pin the local setup install command to the 1.49.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.49.0."
+        },
+        {
+          "class": "named_surface",
+          "path": "docs/runtime-readiness.md",
+          "surface_entry": "docs/runtime-readiness.md",
+          "summary": "Regenerate the runtime readiness reference for surface 1.49.0."
+        },
+        {
+          "class": "named_surface",
+          "path": "docs/skills-revision.md",
+          "surface_entry": "docs/skills-revision.md",
+          "summary": "Use the current 1.49.0+skills.1 bundle in executable examples."
+        },
+        {
+          "class": "generated_runtime",
+          "path": "package-lock.json",
+          "surface_entry": null,
+          "summary": "Update release metadata for 1.49.0."
+        },
+        {
+          "class": "package_export",
+          "path": "package.json",
+          "surface_entry": null,
+          "summary": "Release 1.49.0."
+        },
+        {
+          "class": "schema",
+          "path": "schemas/campaign-runtime-build-packet.v0.schema.json",
+          "surface_entry": "schemas/campaign-runtime-build-packet.v0.schema.json",
+          "summary": "assembly.template_family accepts apollo, apollo-mv-single-step, arjuna and karna, every family the catalog and the private template sources name; nothing is removed."
+        },
+        {
+          "class": "skill",
+          "path": "skills.json",
+          "surface_entry": "skills.json",
+          "summary": "Advance the bundled skill revision to 1.49.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.49.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/campaign-readback-classification/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.49.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/campaign-run-evidence/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.49.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/contribution-intake/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.49.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/next-campaigns-build/SKILL.md",
+          "surface_entry": null,
+          "summary": "Run record theme after record build when a brand theme is applied, instead of editing report.theme; publish the 1.49.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/next-campaigns-os-setup/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.49.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/next-campaigns-os/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.49.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/next-campaigns-polish/SKILL.md",
+          "surface_entry": null,
+          "summary": "Name record build and record theme in the theme gate's apply lane; publish the 1.49.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/next-campaigns-qa/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.49.0+skills.1 bundle revision."
+        },
+        {
+          "class": "cli_surface",
+          "path": "src/cli.mjs",
+          "surface_entry": "record",
+          "summary": "Add record theme and record deploy to the usage text; name record theme in the build prompt and starter-palette notice, and record deploy in next's local-serve deploy action and the deploy prompt."
+        }
+      ],
+      "entry_sha256": "044cecbdb3e7b2bf182ec907320d8beb45361095df4a1df1ec6a119639f1b28d"
+    },
+    {
+      "id": "RL-0209",
+      "sequence": 201,
+      "date": "2026-10-02",
+      "kind": "release",
+      "surface_version": null,
+      "changelog_section": "1.49.0+agent.1",
+      "changelog_sha256": "b2b72f1759ab5a42e177b386aa70d7fbd56a1e2730d5143cf91b14d0f3e3c0ab",
+      "agent_impact": "Run toolkit commands from the campaign folder as npx --no-install campaigns-os …, as the agent context now spells them; a bare campaigns-os resolves through PATH to another copy or to nothing. Reproduce the source design's own proof and urgency elements as designed; do not remove, soften or flag them. An installed agent context keeps the old text until install-agent-context refreshes it.",
+      "compatibility": "compatible",
+      "migration": "none",
+      "changes": [
+        {
+          "class": "documentation",
+          "path": "agents/claude/CLAUDE.md",
+          "surface_entry": "agents/claude/CLAUDE.md",
+          "summary": "Spell every toolkit command npx --no-install campaigns-os, and carry the build skill's rule to reproduce the source design's proof and urgency elements without removing, softening or flagging them."
+        },
+        {
+          "class": "documentation",
+          "path": "agents/codex/AGENTS.md",
+          "surface_entry": "agents/codex/AGENTS.md",
+          "summary": "Spell every toolkit command npx --no-install campaigns-os, and carry the build skill's rule to reproduce the source design's proof and urgency elements without removing, softening or flagging them."
+        },
+        {
+          "class": "documentation",
+          "path": "agents/copilot/copilot-instructions.md",
+          "surface_entry": "agents/copilot/copilot-instructions.md",
+          "summary": "Spell every toolkit command npx --no-install campaigns-os, and carry the build skill's rule to reproduce the source design's proof and urgency elements without removing, softening or flagging them."
+        },
+        {
+          "class": "documentation",
+          "path": "agents/cursor/campaigns-os.mdc",
+          "surface_entry": "agents/cursor/campaigns-os.mdc",
+          "summary": "Spell every toolkit command npx --no-install campaigns-os, and carry the build skill's rule to reproduce the source design's proof and urgency elements without removing, softening or flagging them."
+        }
+      ],
+      "entry_sha256": "11f7c4b1771dc24155cc03b92f942a115b834de9528e12da51bd9d7b73fb3572"
+    },
+    {
+      "id": "RL-0210",
+      "sequence": 202,
+      "date": "2026-10-02",
+      "kind": "release",
+      "surface_version": "1.50.0",
+      "changelog_section": "1.50.0",
+      "changelog_sha256": "dd65c5d7f65efddf1366ea3f1220660d98918bdd558dd18757b61a5152553b23",
+      "agent_impact": "Surface 1.50.0. With qa run --browser, page-binding:<page_id> compares the key the Campaign Cart SDK sent on its Campaigns API requests with the expected key (evidence observation sdk_request, source kind sdk_request): match passes and mismatch is a blocker; the key is never recorded. A page that sends no Campaigns API request, a run with no single expected key, and qa run without --browser keep the static declaration read. A verdict consumer must accept observation sdk_request and source kind sdk_request in page-binding evidence. Ships 1.49.0+agent.1 (the agent context spells npx --no-install campaigns-os and carries the build skill's proof rule) and 1.49.0+agent.2 (a comment-only change). Bundled skills carry revision 1.50.0+skills.1 with unchanged text: an agent that loaded an earlier revision should start a fresh session. Install the 1.50.0 package with the documented local setup command.",
+      "compatibility": "additive",
+      "migration": "none",
+      "changes": [
+        {
+          "class": "compatibility_policy",
+          "path": "compatibility.json",
+          "surface_entry": null,
+          "summary": "Advance the declared version to 1.50.0."
+        },
+        {
+          "class": "compatibility_policy",
+          "path": "contracts/supported-surface.json",
+          "surface_entry": "contracts/supported-surface.json",
+          "summary": "Advance surface_version to 1.50.0 and record the QA verdict schema hash."
+        },
+        {
+          "class": "named_surface",
+          "path": "docs/local-setup.md",
+          "surface_entry": "docs/local-setup.md",
+          "summary": "Pin the 1.50.0 package in the local setup install command."
+        },
+        {
+          "class": "documentation",
+          "path": "docs/orientation-contract-reference.md",
+          "surface_entry": "docs/orientation-contract-reference.md",
+          "summary": "Regenerate at surface 1.50.0."
+        },
+        {
+          "class": "named_surface",
+          "path": "docs/qa-and-test-orders.md",
+          "surface_entry": "docs/qa-and-test-orders.md",
+          "summary": "Describe the browser pass's sdk_request page-binding observation and when the static read still applies."
+        },
+        {
+          "class": "named_surface",
+          "path": "docs/runtime-readiness.md",
+          "surface_entry": "docs/runtime-readiness.md",
+          "summary": "Regenerate at surface 1.50.0."
+        },
+        {
+          "class": "named_surface",
+          "path": "docs/skills-revision.md",
+          "surface_entry": "docs/skills-revision.md",
+          "summary": "Use the current 1.50.0+skills.1 bundle in executable examples."
+        },
+        {
+          "class": "generated_runtime",
+          "path": "package-lock.json",
+          "surface_entry": null,
+          "summary": "Advance the package version to 1.50.0."
+        },
+        {
+          "class": "package_export",
+          "path": "package.json",
+          "surface_entry": null,
+          "summary": "Advance the package version to 1.50.0."
+        },
+        {
+          "class": "schema",
+          "path": "schemas/campaigns-os-qa-verdict.v0.schema.json",
+          "surface_entry": "schemas/campaigns-os-qa-verdict.v0.schema.json",
+          "summary": "Accept observation sdk_request and the sdk_request source kind in page-binding evidence."
+        },
+        {
+          "class": "skill",
+          "path": "skills.json",
+          "surface_entry": "skills.json",
+          "summary": "Advance the bundled skill revision to 1.50.0+skills.1 and each skill version one patch."
+        },
+        {
+          "class": "skill",
+          "path": "skills/next-campaigns-os/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.50.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/next-campaigns-os-setup/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.50.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/next-campaigns-build/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.50.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/next-campaigns-polish/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.50.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/next-campaigns-qa/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.50.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/campaign-lifecycle-orientation/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.50.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/campaign-run-evidence/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.50.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/campaign-readback-classification/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.50.0+skills.1 bundle revision."
+        },
+        {
+          "class": "skill",
+          "path": "skills/contribution-intake/SKILL.md",
+          "surface_entry": null,
+          "summary": "Publish the 1.50.0+skills.1 bundle revision."
+        }
+      ],
+      "entry_sha256": "3fed96311daa5f153704a1ec7ded952e1e00065ce9f81fd4d3350f13beba964a"
     }
   ]
 }

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.48.0",
+  "surface_version": "1.50.0",
   "package_exports": [
     "./commercial-journey",
     "./commercial-parity",
@@ -66,7 +66,7 @@
       "sha256": "f310c1b7844d9b1994864d15858ff0c6f17efc1e5285ba193d181bdb2dd4be2f"
     },
     "schemas/campaign-runtime-build-packet.v0.schema.json": {
-      "sha256": "47c2899f409ed5927cf410bddd63e7bb8a9d154eabf7a07455777aed118212e9"
+      "sha256": "5002529c5979c4d8fef7e298de82ebdf625ffbd11f5284ba684d96d173788d62"
     },
     "schemas/campaign-spec.v4.schema.json": {
       "sha256": "af56c3de638d3c4e1fd5df8c2d733754d9ad16caa23b5bec92ce3a6f71bd0271"
@@ -84,7 +84,7 @@
       "sha256": "3c40fd79f218d1b95f0424f9a2b67db140a306329e2ca02793e2740d3afded59"
     },
     "schemas/campaigns-os-qa-verdict.v0.schema.json": {
-      "sha256": "ec4514e81a791a63bc0b358d7977aa823f3c5524e0f5caaba2712e66f262e18a"
+      "sha256": "8c689d29850b2b894c17438ee4411363033bae6f805820af53b7a04a5693d0e0"
     },
     "schemas/campaigns-os-doctor-output.v0.schema.json": {
       "sha256": "87866e619d2a18f01a208a1682cb14a2079f61df51c642f4e1902b6e6bce0ce5"
@@ -120,7 +120,7 @@
       "sha256": "dfc9abed38d456969e47a21f606d308a03bdf036f3466f7d6e47a602747dacf4"
     },
     "contracts/effects.v1.json": {
-      "sha256": "5f8c6f2f88fc9e0c11c09e265640071d3c1d81fd96c6e05283ed5cfed21d1d59"
+      "sha256": "75cdd0bc33788d8d6af10c995f362987725f622bf42700f1b70b39bbd87e6878"
     },
     "schemas/campaigns-os-effects.v1.schema.json": {
       "sha256": "3eadd22169ab98bc7c2f682af2751267605170581182158d96be035b0cfe44dc"

package/docs/brand-theme-bridge.md

@@ -151,8 +151,9 @@ When `theme inspect` reports `can_generate: true` and the campaign ships
 commerce pages (checkout/upsell/downsell/receipt), the gate **blocks**
 `next polish`, `next deploy`, `next qa`, and `qa run` until one of:
 
-- the brand layer is generated and recorded as applied
-  (`report.theme.status: applied`, `load_order: after-next-core`), or
+- the brand layer is generated, linked and recorded as applied with
+  `campaigns-os record theme --packet <p>` (`report.theme.status: applied`,
+  `load_order: after-next-core`), or
 - an explicit waiver is recorded:
   `campaigns-os theme waive --packet <p> --reason "<why>" --waived-by "<named human>"`
   (optionally `--expires-at <ISO>`; placeholders such as "operator" are refused), or
@@ -197,8 +198,12 @@ If a fresh `brand-theme.css` exists:
 3. Preserve SDK-owned runtime surfaces: `data-next-*`, package selectors,
    payment fields, totals, submit controls, receipt templates, route meta tags,
    and SDK JavaScript.
-4. Record `report.theme.status`, `css_path`, `commerce_pages`, `load_order`,
-   and evidence.
+4. Rebuild, run `campaigns-os record build --packet <p>`, then
+   `campaigns-os record theme --packet <p>`. It reads each built commerce
+   page's stylesheet links and records `report.theme.status`, `css_path`,
+   `commerce_pages`, `load_order` and evidence. It refuses, writing nothing,
+   when a page that loads `next-core.css` does not load the brand layer after
+   it, or when no built commerce page loads `next-core.css`.
 
 ### Where next-core.css belongs
 
@@ -212,8 +217,9 @@ stylesheets off those pages and list them only in the frontmatter styles of
 the pages that render family components, often just checkout.
 
 `report.theme.commerce_pages` is the list of pages where the brand layer was
-applied, recorded by the build. Record the pages you actually scoped, for
-example `commerce_pages: ["checkout"]`. The theme gate does not compare this
+applied. `record theme` writes it from the built pages: every commerce page
+that loads `next-core.css`, for example `commerce_pages: ["checkout"]`. A page
+that loads neither stylesheet is left out and noted in the evidence. The theme gate does not compare this
 list with the funnel. It passes on `report.theme.status: applied` with
 `load_order: after-next-core`. The gate's own `commerce_pages` output is a
 different field: every checkout, upsell, downsell, receipt or thank-you page

package/docs/build-packet.md

@@ -970,8 +970,9 @@ starter palette is acceptable>" --waived-by "<named human>"`, optionally
 (status and severity — never `fail`) and keeps the shipped palette visible in
 the verdict; or hand-author the brand
 layer — write `brand-theme.css`, list it after `next-core.css` in commerce-page
-frontmatter styles, rebuild, and record `report.theme.status: applied` with
-`load_order: after-next-core`. Nothing waives the gate on the operator's
+frontmatter styles, rebuild, `record build`, and `record theme`, which records
+`report.theme.status: applied` with `load_order: after-next-core` from the
+built pages. Nothing waives the gate on the operator's
 behalf. See [Brand Theme Bridge](./brand-theme-bridge.md) for both lanes in
 full.
 
@@ -1237,7 +1238,9 @@ loopback host (`127.0.0.1`, `[::1]`) with a ready line naming the
 `http://localhost:<port>/` fallback, and warns (`deploy.local_serve_url`) when
 the recorded URL is neither.
 `next` at the deploy stage then hands off a serve-locally prompt and action
-instead of a ship-to-host one. The directory to serve is `_site/`; for a
+instead of a ship-to-host one, and the served URL is recorded with
+`campaigns-os record deploy --packet <p> --base-url <url>` (the record command
+table below). The directory to serve is `_site/`; for a
 root-served campaign (`campaign.route_root: "/"`) the handoff adds that pages
 are served at site-root paths while assets keep the `/<public_route_slug>/`
 prefix, so `_site/` needs the same rewrite of root-level page routes onto
@@ -1609,6 +1612,8 @@ hand-editing `.campaign-runtime/` JSON:
 | `campaigns-os record setup --packet <p>` | Build Context `scaffold.required=false` (`handoff_skill` next-campaigns-build) and `stages.setup` completed | the campaign output directory (`assembly.output_dir`) does not exist, or there is no Build Context or Assembly Report |
 | `campaigns-os record build --packet <p>` | `stages.assembly` completed with `build_fingerprint` = doctor's `derived.build_output_fingerprint.value`, `source_package_material_fingerprint` = the report's Design Source Package material fingerprint when present, and `stages.polish` reset to `required` (`required_by` build, `required_for` qa) unless its evidence is bound to this exact output | doctor cannot compute the fingerprint (no `_site/<public_route_slug>/`), setup is still required, or `stages.setup` is not terminal |
 | `campaigns-os record polish --packet <p> --evidence <file>` | `stages.polish` from the file (`docs/polish-evidence.md` §7: completed, blocked or skipped), bound to doctor's current fingerprint; `report.theme.repair_loop_defect` when the file sets it | build is not recorded for the current output, the file has a shape error (named by field), or, for a completed status, the polish gate doctor evaluates would not pass on the result |
+| `campaigns-os record theme --packet <p>` | `report.theme`: status `applied`, `load_order` `after-next-core`, `css_path`, `commerce_pages` and per-page evidence read from each built commerce page's stylesheet links; any earlier theme waiver is cleared | build is not recorded for the current output, the campaign ships no commerce pages, a built commerce page that loads `next-core.css` does not load `brand-theme.css` (or `checkout-brand.css`) after it or links one missing from the built output, or no built commerce page loads `next-core.css` |
+| `campaigns-os record deploy --packet <p> --base-url <url>` | the packet's `deploy.preview_url` and `stages.deploy` completed with the URL in `outputs` and one evidence line per built page that answered (each page is requested under the URL first) | the packet is not `local-serve`, the URL is not a loopback origin naming the campaign's route root, a built page does not answer 2xx, polish is not recorded, the built output changed since build was recorded, or the theme gate is blocked |
 
 Each command also refuses a stage `next` has not reached: while doctor's
 prepare-build gate is set (`next` answers prepare-build) or while an earlier

package/docs/local-setup.md

@@ -3,7 +3,7 @@
 For a new campaign, create an empty working folder and run this from it:
 
 ```sh
-npm init -y && npm install --save-exact next-campaign-page-kit@0.2.0 && npm install --save-dev --save-exact @nextcommerce/campaigns-os@1.48.0 && npx --no-install campaigns-os tooling setup --target . --platform claude
+npm init -y && npm install --save-exact next-campaign-page-kit@0.2.0 && npm install --save-dev --save-exact @nextcommerce/campaigns-os@1.50.0 && npx --no-install campaigns-os tooling setup --target . --platform claude
 ```
 
 `npm init -y` gives the folder its own `package.json`. Without one, npm

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.48.0`
+Supported surface at generation time: `1.50.0`
 
 ## Forward compatibility
 

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

@@ -55,9 +55,10 @@ the toolkit runs that loop in a fixed order:
    with it locally (the parity step renders it to a temp dir, and the deploy
    host renders it from the committed source).
 2. **Serve and prove.** Serve `_site/` on localhost (the `next deploy` handoff
-   names the directory and any root-route rewrite), record the URL on
-   `deploy.preview_url`, then run `polish capture`, `qa run --browser`, and the
-   typed-card order paths against it.
+   names the directory and any root-route rewrite) and run `polish capture`
+   against it. Once polish is recorded, `record deploy --packet <p> --base-url
+   <url>` records the URL on `deploy.preview_url` and the deploy stage; then run
+   `qa run --browser` and the typed-card order paths against it.
 3. **Prove the pin on the production output.** Before committing, run
 
    ```bash
@@ -1927,19 +1928,32 @@ expectations, and commerce-ref validation. A doctor-clean non-packet run means
 matches a spec". Treat it as a residue/visual gate, not equivalent to a
 packet-driven QA pass.
 
-### Per-page credential declarations
+### Per-page credential binding
 
 Canonical `qa run` emits `page-binding:<page_id>` in the existing `api-metadata`
 family, with `campaigns-os-page-binding/v0` evidence (typed in the verdict schema).
-`match` means the statically declared credential equals the expected credential;
+`match` means the page's credential equals the expected credential;
 `mismatch` is a blocker. `unknown` requires manual review. All three carry
 `identity: not_verified`: credential equality never proves a unique Campaign App
 ID, and no App ID is inferred from `campaignId` or `next-campaign-id`.
 
 Expected data reuses the commercial QA resolver (packet, then spec, then an
 explicit supported environment source). Conflicting authored values are unknown.
-The SDK loads `window.nextConfig.apiKey` before `next-api-key` at boot, so meta
-wins at runtime; this check deliberately reports differing declarations as a
+
+With `--browser`, the row comes from the key the Campaign Cart SDK actually
+sent. The SDK sends it as `Authorization` on every Campaigns API request, and
+the browser pass reads that header on each page it loads. The values are
+compared in memory and dropped: the evidence records
+`observation: sdk_request`, `source_kinds: ["sdk_request"]`, and `match` when
+every request carried the expected credential or `mismatch` when any carried
+another. This works whatever the
+page's scripts look like. A page that sent no Campaigns API request, or a run
+with no single expected credential, keeps the static row described below.
+
+Without `--browser`, or for such a page, the row is a static read of what the
+page declares (`observation: static_declaration`). The SDK loads
+`window.nextConfig.apiKey` before `next-api-key` at boot, so meta wins at
+runtime; the static read deliberately reports differing declarations as a
 conflict rather than certifying one. It does not observe SDK execution.
 
 The bounded HTML loader is reused. HTML is parsed without execution; JavaScript

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.48.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.50.0`.
 
 ## What this is
 

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.48.0+skills.1"
+"bundle_revision": "1.50.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.48.0+skills.1` is therefore ahead of `1.40.0+skills.7`.
+  with the prefix**. `1.50.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.48.0+skills.1
+Bundle revision: 1.50.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.48.0+skills.1
+npx --no-install campaigns-os tooling status --skills-revision 1.50.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.48.0+skills.1",
+  "requested": "1.50.0+skills.1",
   "spelling": "bundle",
-  "on_disk": "1.48.0+skills.1",
+  "on_disk": "1.50.0+skills.1",
   "on_disk_skill": null,
-  "message": "match (1.48.0+skills.1)"
+  "message": "match (1.50.0+skills.1)"
 }
 ```
 
 The text view prints one named line, as a header above the rest of the status:
 
 ```
-Skills revision: match (1.48.0+skills.1)
-Skills revision: mismatch: loaded 1.39.0+skills.1, on disk 1.48.0+skills.1 — start a fresh session
-Skills revision: unchecked (on disk 1.48.0+skills.1)
+Skills revision: match (1.50.0+skills.1)
+Skills revision: mismatch: loaded 1.39.0+skills.1, on disk 1.50.0+skills.1 — start a fresh session
+Skills revision: unchecked (on disk 1.50.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.48.0",
+  "version": "1.50.0",
   "description": "Toolkit for agent-assisted NEXT campaign builds.",
   "license": "Apache-2.0",
   "repository": {

package/schemas/campaign-runtime-build-packet.v0.schema.json

@@ -336,6 +336,8 @@
         "template_family": {
           "enum": [
             "undecided",
+            "apollo",
+            "apollo-mv-single-step",
             "olympus",
             "limos",
             "demeter",
@@ -343,6 +345,8 @@
             "olympus-mv-two-step",
             "shop-single-step",
             "shop-three-step",
+            "arjuna",
+            "karna",
             "custom"
           ]
         },