@nextcommerce/campaigns-os 1.47.0 → 1.48.0

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

@@ -96,6 +96,32 @@ recapture. A hosted target (`netlify`, `cloudflare-pages`, …) is unaffected:
 its build stage renders production as before and `page-kit parity` refuses the
 packet (`local_proof.parity.not_local_serve`).
 
+### Missing evidence carried forward on the local preview
+
+On a `local-serve` packet served from a loopback host (`localhost`,
+`127.0.0.1`, `[::1]`, for both `deploy.preview_url` and `--base-url`), some
+missing evidence is carried forward as a warning instead of blocking the
+loop. The campaign must still prove its commerce there: store and campaign
+binding, routes, SDK loading, prices and a typed-card order. Only these
+checks are carried forward:
+
+| Check | When |
+| --- | --- |
+| `polish.evidence_missing`, `polish.report_missing` | Polish was never recorded for this build. |
+| `polish.hidden_eager_media.no_capturable_routes` | Every mapped page is template stock (`skip_reason`), so polish capture has no design route to capture. |
+| `polish.hidden_eager_media.capture_malformed` | Only when no page-load capture was recorded at all. |
+| Template-residue severity | With `theme_gate.nothing_generatable`, the starter template is the design, so residue findings are warnings rather than blockers. |
+
+A carried-forward gate has status `carried_forward`. Doctor reports it as a
+warning starting "Carried forward on the local preview"; `next` moves past
+polish to deploy and QA; QA records it as a `warn` row, so the verdict is at
+best `ready_with_exceptions`. The evidence is reported as missing, never as
+passed. Any other check keeps its meaning. A hosted preview or production
+packet, and a `local-serve` packet served from any other host, gets the strict
+gates. `record polish` and the waiver commands also keep them strict. Progress
+snapshots record a carried-forward gate as `not_applicable`, because their
+schema has no carried-forward state.
+
 ## Resolve
 
 Use resolve before a full run:
@@ -482,7 +508,15 @@ the three checks and each `evidence.checks[]` entry carries `kind`
 (`family_shell` or `sdk_wiring`).
 The upsell and checkout bundle price checks count the SDK's
 `[data-next-bundle-display*='price']` alongside the contract's price rows; a
-hidden, zero-size or empty bundle-display node does not count.
+hidden, zero-size or empty bundle-display node does not count. A checkout that
+shows no price because QA opened it directly, with an empty SDK cart and no
+package selection of its own, is `skipped` rather than failed:
+`pricing.checkout_price_visible` records `cart_count` and
+`checkout_selection_surface` and says so. That checkout's cart is filled on
+an earlier page, for example by a landing link carrying `forcePackageId`, and
+the test order enters it from there. A checkout with its own package
+selection, or a filled cart, still fails when no price shows. If the cart
+probe itself fails, the row stays failed and records `empty_cart_probe_error`.
 Promoted template families must also have
 `contracts/template-brand-contract.<family>.v0.json`; QA emits a blocker if the
 selected family is missing its brand/residue/pricing contract instead of
@@ -1749,6 +1783,17 @@ shared real inbox rather than a synthetic one). When neither is set, the runner
 falls back to a single stable synthetic address — still one reused customer, but
 not deliverable.
 
+Reusing one customer has one cost. The platform refuses an order whose customer,
+items and total match one it accepted or is still processing in the last 30
+minutes ("Duplicate order detected, order not created"). A successful test order
+does not hold that window, so the paths of one run do not collide. Two QA runs
+against the same campaign at once do, and so can a rerun soon after an attempt
+that died mid-submit. QA reports it on the path's `browser-test-order` row as
+`order create rejected: HTTP 400: Duplicate order detected …` followed by
+`duplicate_order` and the remedy: re-run with a different `--test-email-prefix`
+(or `--test-email`), or wait. The shipping address is not part of the match, so
+changing `--test-address1` does not help.
+
 The browser driver intentionally behaves like a user:
 
 - package selection uses rendered `[data-next-package-id]` controls when
@@ -1919,7 +1964,9 @@ ASCII whitespace and compared case-insensitively as the browser does; classic
 `built_output.script_syntax` in [the Build Packet doc](build-packet.md).
 
 External executable scripts other than the recognized jsDelivr Campaign Cart
-loader/index are inspected only on the page's origin. Each page admits at most
+loader or index are inspected only on the page's origin. Three Campaign Cart
+paths count as the SDK and are never fetched: `dist/loader.js` (the one the
+starter templates load), `dist/index.js` and `public/loader.js`. Each page admits at most
 6 such references; each run fetches at most 24 distinct URLs (deduplicated),
 256 KiB per response and 6 MiB aggregate, 5 seconds per request including body
 read (at most 30 seconds of sequential config requests per page). Redirects,

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.47.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.48.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.47.0+skills.1"
+"bundle_revision": "1.48.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.47.0+skills.1` is therefore ahead of `1.40.0+skills.7`.
+  with the prefix**. `1.48.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.47.0+skills.1
+Bundle revision: 1.48.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.47.0+skills.1
+npx --no-install campaigns-os tooling status --skills-revision 1.48.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.47.0+skills.1",
+  "requested": "1.48.0+skills.1",
   "spelling": "bundle",
-  "on_disk": "1.47.0+skills.1",
+  "on_disk": "1.48.0+skills.1",
   "on_disk_skill": null,
-  "message": "match (1.47.0+skills.1)"
+  "message": "match (1.48.0+skills.1)"
 }
 ```
 
 The text view prints one named line, as a header above the rest of the status:
 
 ```
-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)
+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)
 ```
 
 `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.47.0",
+  "version": "1.48.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.19
+version: 1.0.22
 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.47.0+skills.1
-Run `npx --no-install campaigns-os tooling status --skills-revision 1.47.0+skills.1`
+Bundle revision: 1.48.0+skills.1
+Run `npx --no-install campaigns-os tooling status --skills-revision 1.48.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

package/skills/campaign-readback-classification/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: campaign-readback-classification
-version: 1.0.19
+version: 1.0.22
 description: Classify a selected campaign from the readback projection's v2 fields and write a read-only handoff without turning diagnosis into permission.
 ---
 
-Bundle revision: 1.47.0+skills.1
-Run `npx --no-install campaigns-os tooling status --skills-revision 1.47.0+skills.1`
+Bundle revision: 1.48.0+skills.1
+Run `npx --no-install campaigns-os tooling status --skills-revision 1.48.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

package/skills/campaign-run-evidence/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: campaign-run-evidence
-version: 1.0.19
+version: 1.0.22
 description: Interpret existing Campaigns OS doctor, QA and proof-depth evidence without claiming more proof than the artifacts contain.
 ---
 
-Bundle revision: 1.47.0+skills.1
-Run `npx --no-install campaigns-os tooling status --skills-revision 1.47.0+skills.1`
+Bundle revision: 1.48.0+skills.1
+Run `npx --no-install campaigns-os tooling status --skills-revision 1.48.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
@@ -65,7 +65,12 @@ Saved-Map QA may publish it under the existing consent and flag controls; a
 publication failure does not erase the local one. Local-spec packet verdicts
 stay local even with `--post-verdict`, and `qa publish` refuses those packets.
 The readback projects `.campaign-runtime/qa-verdict.json` when
-that sidecar has been copied into the campaign repository. A markdown QA
+that sidecar has been copied into the campaign repository. The sidecar is a
+committable projection: it always empties `test_orders`, `entry_urls`,
+`page_urls` and `tested_urls`, so an empty `test_orders` there says nothing
+about ordering. Its typed-card proof is the `browser-test-order:<path>`
+assertions, each with a `browser-order-total-parity:<path>` row beside it; the
+full verdict under `qa-output/` keeps the order records. A markdown QA
 report, a ledger or a gate script is not a verdict and must not be scanned for
 a disposition, a run id or a blocker. Where two JSON verdicts exist, interpret
 the one the projection loaded; do not walk a report looking for a later rerun.

package/skills/contribution-intake/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: contribution-intake
-version: 1.0.19
+version: 1.0.22
 description: Turn a suggestion about the agent surface into a classified, evidence-checked proposal and, only with attended approval, one issue on this repository's tracker.
 ---
 
-Bundle revision: 1.47.0+skills.1
-Run `npx --no-install campaigns-os tooling status --skills-revision 1.47.0+skills.1`
+Bundle revision: 1.48.0+skills.1
+Run `npx --no-install campaigns-os tooling status --skills-revision 1.48.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

package/skills/next-campaigns-build/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: next-campaigns-build
-version: 1.0.24
+version: 1.0.27
 description: Assemble a NEXT campaign from a doctor-cleared Build Packet, CampaignSpec/API values, prepared HTML/assets, page-kit, and starter-template contracts.
 ---
 
-Bundle revision: 1.47.0+skills.1
-Run `npx --no-install campaigns-os tooling status --skills-revision 1.47.0+skills.1`
+Bundle revision: 1.48.0+skills.1
+Run `npx --no-install campaigns-os tooling status --skills-revision 1.48.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
@@ -86,6 +86,7 @@ Build rules:
 - Preserve SDK-owned checkout/cart/upsell/receipt/payment/address/totals/submit surfaces.
 - If `doctor` (tier `A`: inspection that writes nothing, plus one read-only live campaign request once the site is built and a public campaign key resolves; `--write` is also tier `A` and writes doctor output; `--built` is tier `B`) reports `derived.scope.mode = "partial"`, build the pages listed in `derived.scope.built_pages` from their prepared source. Keep every out-of-scope route unbuilt by default, including pages marked `template_stock: true`; never publish placeholder presell/landing pages that remain on another host. Materialize a stock page only with explicit per-page operator opt-in (including a required pre-checkout `select` stand-in). For opted-in pages use the locked family's own page for that role with its dependent `_includes/`, `_layouts/`, and assets, wire it from CampaignSpec, and build a required select step first. Do not attest stock screenshots as design source. Built stock pages rejoin preview QA once their HTML exists. Carry remaining `skip_reason` declarations into the report and label the preview route/visual-testable rather than full-funnel launch-ready.
 - For `landing` and `presell` pages, prefer the prepared source HTML when `source_html.pages[].path` points at a real standalone page. Preserve the design/content through a passthrough page-kit layout, inject the SDK loader/config as needed, and repoint CTAs into the CampaignSpec flow. Treat `source_html.pages[].path` and `context.page_map[].source_path` as source provenance. Treat `source_html.pages[].page_kit`, `context.page_map[].page_kit`, and `context.page_map[].output_path` as the Page Kit target file, route, CPK `page_type`, and frontmatter projection.
+- Reproduce the source design's own proof and urgency elements as designed: reviews and testimonials, ratings, "Verified Purchase" labels, recent-purchase popups, stock counters, countdowns and guarantees. They are the merchant's content and the merchant's responsibility; Campaigns OS does not review them, so do not remove, soften or flag them. The starter templates shipping without some of these elements is not a reason to drop the source's.
 - Prepared source HTML means page-kit-ready markup, not a wholesale Liquid rewrite. Standalone HTML mockups that are meant to stay whole (their `source_screenshot` proof is of the full document) keep their document wrappers: the source-html manifest records `wrapper_policy: preserve_document_wrappers` (or `--wrapper-policy preserve_document_wrappers` on `start` / `prepare-build`), and doctor reports the wrappers as a warning. Otherwise, standalone AI/exported HTML should keep page-owned body markup, remove document wrappers, add YAML frontmatter, move shared CSS/assets into the campaign structure, and use Liquid helpers only where page-kit needs campaign-rooted links/assets/includes.
 - For `checkout`, `upsell`, `downsell`, and `receipt` pages, treat the selected starter-template commerce surface as the SDK contract reference: preserve required `data-next-*` controls, hidden fields, payment/address/totals/submit wiring, and `next_dont_touch` regions. The surrounding HTML wrapper, page composition, imagery, copy hierarchy, and brand layer are campaign/source-owned. Do not carry starter visual chrome forward when prepared source design should own that surface. QA checks what the checkout does, not family class names: do not add family shell classes (`.checkout-wrapper`, `.checkout-layout__left/right`) to the campaign's own grid or swap source-owned field markup for family includes to satisfy QA. Keep the checkout working instead: a `<form data-next-checkout="form">`, the contact and shipping fields bound with `data-next-checkout-field` inside it, and a visible cart total. A required field bound only on a `type="hidden"` input, a disabled control, a read-only input or read-only textarea, or a control with `aria-disabled="true"` does not count as bound: QA reports it in `fields_bound.missing`.
 - Read `context.theme` and `.campaign-runtime/theme/theme-report.json` when present. If a fresh `brand-theme.css` artifact exists, copy it into the campaign asset tree and load it after `next-core.css` on checkout, upsell, downsell, and receipt pages. If policy is `inspect_only`, either run `campaigns-os theme generate` (tier `B`: writes the theme artifacts and doctor output under the target; `--force` is tier `C`) or record an explicit skipped reason before applying a new brand layer.

package/skills/next-campaigns-os/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: next-campaigns-os
-version: 1.0.39
+version: 1.0.42
 description: Coordinate Campaigns OS lifecycle workflows from CampaignSpec, Build Packet, starter-template contracts, stage reports, deploy evidence, and QA proof depth.
 ---
 
-Bundle revision: 1.47.0+skills.1
-Run `npx --no-install campaigns-os tooling status --skills-revision 1.47.0+skills.1`
+Bundle revision: 1.48.0+skills.1
+Run `npx --no-install campaigns-os tooling status --skills-revision 1.48.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

package/skills/next-campaigns-os-setup/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: next-campaigns-os-setup
-version: 2.0.22
+version: 2.0.25
 description: Bootstrap or prepare a target page-kit campaign repo from a doctor-cleared Campaigns OS Build Packet before full build wiring. Formerly installed as next-campaigns-setup; renamed 2026-08 to stop colliding with the published NextCommerceCo/skills scaffolder of that name.
 ---
 
-Bundle revision: 1.47.0+skills.1
-Run `npx --no-install campaigns-os tooling status --skills-revision 1.47.0+skills.1`
+Bundle revision: 1.48.0+skills.1
+Run `npx --no-install campaigns-os tooling status --skills-revision 1.48.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

package/skills/next-campaigns-polish/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: next-campaigns-polish
-version: 1.1.23
+version: 1.1.26
 description: Run the visual/runtime polish pass after build and before QA for a Campaigns OS campaign.
 ---
 
-Bundle revision: 1.47.0+skills.1
-Run `npx --no-install campaigns-os tooling status --skills-revision 1.47.0+skills.1`
+Bundle revision: 1.48.0+skills.1
+Run `npx --no-install campaigns-os tooling status --skills-revision 1.48.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
@@ -56,7 +56,7 @@ Responsibilities:
 - Compare prepared source design against built campaign pages.
 - Scan the prepared source assets for brand marks such as `logo*.png`, `logo*.svg`, and obvious header/logo images before leaving starter-template logos in place.
 - Scan **visible** rendered text inside the family's content/commerce surfaces (the selectors enumerated in `contracts/template-brand-contract.<family>.v0.json`) for placeholder/residue copy the build should have replaced — the *literal starter defaults*: lorem-ipsum, the unmodified starter headings (`Product Name` / `Package Title` / `Your headline`), `[VERIFY …]` author notes, `TODO` markers. Match the literal starter strings, not any authored copy that merely contains those words, and skip `<script>` / `<style>` / JSON-LD / `data-*` attributes. Treat a surviving literal starter default on a content/commerce surface as a polish blocker — replace it from the prepared source / CampaignSpec; do not draft substitute copy (if the design's authored copy is genuinely missing, flag it rather than invent it). This is *copy* residue, complementary to the computed-style / asset residue gated by `next-campaigns-qa` + the brand contract — not a duplicate of it.
-- Flag template *defaults* left where they disagree with the prepared design — e.g. the same benefit icon repeated across a grid *when the design uses distinct icons*, or a guarantee badge/term that disagrees with the design — as polish defects, not just logos. Judge against the prepared source, not taste: copy or imagery the source/CampaignSpec does not supply (e.g. a placeholder testimonial name/quote/role) is residue; "looks generic" on its own is not.
+- Flag template *defaults* left where they disagree with the prepared design — e.g. the same benefit icon repeated across a grid *when the design uses distinct icons*, or a guarantee badge/term that disagrees with the design — as polish defects, not just logos. Judge against the prepared source, not taste: copy or imagery the source/CampaignSpec does not supply (e.g. a placeholder testimonial name/quote/role) is residue; "looks generic" on its own is not. Copy the source does supply, including its proof and urgency elements (reviews, "Verified Purchase" labels, recent-purchase popups, stock counters, countdowns, guarantees), is the merchant's content: keep it as designed and do not record it as an issue or an unconfirmed claim.
 - **Brand-bleed (cloned-source de-brand) pass.** When a campaign is cloned from a proven sibling, the sibling's brand defaults ride along. Inspect the built pages and assets for residual cross-brand bleed and clear it before recording: (1) a residual promo/sale banner or coupon code/copy from the source campaign (including a baked-in *fake* code); (2) a prior-campaign / sibling favicon left in place; (3) scaffold or non-design fonts the design did not specify (e.g. starter `Plus Jakarta`); (4) hardcoded non-token colors — any brand color literal that should be a token, such as next-core's `#C670FE` "Most Popular" pill. Clear each from the prepared source / CampaignSpec and brand theme (tokens, not literals); flag — do not invent — anything the design genuinely doesn't supply. Treat surviving bleed as a polish blocker. This complements the favicon/logo and copy-residue checks above; it is the cross-brand contamination angle, not a duplicate.
 - Read the assembly report decisions before polishing. Do not reintroduce source-HTML elements that build intentionally dropped because CampaignSpec/API did not support them, such as unavailable payment methods.
 - **Remove or rename a contract-listed payment-chrome asset; never edit one in place.** The assets named in `contracts/template-brand-contract.<family>.v0.json` under `default_residue.payment_chrome.assets` are keyed by QA on the *referenced basename*, not on their contents. Stripping the unsupported marks from inside a shared file such as `upsell-payment-logos.svg` leaves the reference in place, so QA reports residue for an asset that no longer carries any — and on 2026-09-06 the repair loop's remedy for that report deleted a cards-only trust strip that was correct. Delete the asset, or write a new one under a new name and repoint the reference. QA downgrades an edited-in-place asset to `manual_review` rather than a blocker, but that is a safety net for a mistake, not the supported way to do this.

package/skills/next-campaigns-qa/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: next-campaigns-qa
-version: 1.3.23
+version: 1.3.26
 description: Run spec-aware QA from a saved Map or local-spec Build Packet and tested campaign URL after build, polish, and deploy/local evidence exist, including Playwright typed-card test-order proof.
 ---
 
-Bundle revision: 1.47.0+skills.1
-Run `npx --no-install campaigns-os tooling status --skills-revision 1.47.0+skills.1`
+Bundle revision: 1.48.0+skills.1
+Run `npx --no-install campaigns-os tooling status --skills-revision 1.48.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

package/skills.json

@@ -1,7 +1,7 @@
 {
   "name": "campaigns-os-skills",
   "description": "Skills bundled with Campaigns OS. `skills.sh` installs these into the shared agent skill directories (~/.claude/skills, ~/.codex/skills), so each one is a versioned package: bump the version whenever a package changes. `bundle_revision` identifies the bundle as a whole — `<package version>+skills.<n>`, where the prefix is this package's version and `<n>` counts the skill-text revisions published against it. It advances whenever ANY bundled skill changes, every SKILL.md states it on its first body line, and `campaigns-os tooling status --skills-revision <value>` compares the value an agent read from a skill against the bundle on disk. See docs/skills-revision.md.",
-  "bundle_revision": "1.47.0+skills.1",
+  "bundle_revision": "1.48.0+skills.1",
   "homepage": "https://github.com/NextCommerceCo/campaigns-os",
   "retired_skills": [
     {
@@ -16,7 +16,7 @@
     {
       "id": "next-campaigns-os",
       "name": "Campaigns OS Lifecycle",
-      "version": "1.0.39",
+      "version": "1.0.42",
       "path": "skills/next-campaigns-os/SKILL.md",
       "domain": "campaigns",
       "description": "Coordinate Campaigns OS lifecycle workflows from CampaignSpec, Build Packet, starter-template contracts, stage reports, deploy evidence, and QA proof depth."
@@ -24,7 +24,7 @@
     {
       "id": "next-campaigns-os-setup",
       "name": "Campaigns OS Setup",
-      "version": "2.0.22",
+      "version": "2.0.25",
       "path": "skills/next-campaigns-os-setup/SKILL.md",
       "domain": "campaigns",
       "description": "Bootstrap or prepare a target page-kit campaign repo from a doctor-cleared Campaigns OS Build Packet before full build wiring. Formerly next-campaigns-setup; renamed to release that name to the published NextCommerceCo/skills scaffolder."
@@ -32,7 +32,7 @@
     {
       "id": "next-campaigns-build",
       "name": "Campaign Build",
-      "version": "1.0.24",
+      "version": "1.0.27",
       "path": "skills/next-campaigns-build/SKILL.md",
       "domain": "campaigns",
       "description": "Assemble a NEXT campaign from a doctor-cleared Build Packet, CampaignSpec/API values, prepared HTML/assets, page-kit, and starter-template contracts."
@@ -40,7 +40,7 @@
     {
       "id": "next-campaigns-polish",
       "name": "Campaign Polish",
-      "version": "1.1.23",
+      "version": "1.1.26",
       "path": "skills/next-campaigns-polish/SKILL.md",
       "domain": "campaigns",
       "description": "Run the visual/runtime polish pass after build and before QA for a Campaigns OS campaign."
@@ -48,7 +48,7 @@
     {
       "id": "next-campaigns-qa",
       "name": "Campaign QA",
-      "version": "1.3.23",
+      "version": "1.3.26",
       "path": "skills/next-campaigns-qa/SKILL.md",
       "domain": "campaigns",
       "description": "Run spec-aware QA from a saved Map or local-spec Build Packet and tested campaign URL after build, polish, and deploy/local evidence exist, including Playwright typed-card test-order proof."
@@ -56,7 +56,7 @@
     {
       "id": "campaign-lifecycle-orientation",
       "name": "Campaign Lifecycle Orientation",
-      "version": "1.0.19",
+      "version": "1.0.22",
       "path": "skills/campaign-lifecycle-orientation/SKILL.md",
       "domain": "campaigns",
       "description": "Orient a reader to the Campaigns OS lifecycle artifacts a run has already emitted, without advancing their state: the shared vocabulary, doctor as a gate, the stage record, and the store-theme/Page Kit two-worlds trap."
@@ -64,7 +64,7 @@
     {
       "id": "campaign-run-evidence",
       "name": "Campaign Run Evidence",
-      "version": "1.0.19",
+      "version": "1.0.22",
       "path": "skills/campaign-run-evidence/SKILL.md",
       "domain": "campaigns",
       "description": "Interpret existing doctor, QA verdict and proof-depth evidence without claiming more proof than the artifacts contain, and keep funnel proof apart from merchant launch readiness."
@@ -72,7 +72,7 @@
     {
       "id": "campaign-readback-classification",
       "name": "Campaign Readback Classification",
-      "version": "1.0.19",
+      "version": "1.0.22",
       "path": "skills/campaign-readback-classification/SKILL.md",
       "domain": "campaigns",
       "description": "Classify a selected campaign from the campaigns-os-readback/v2 fields (artifacts, staleness.stale_keys, clean, doctor, divergences, skip_cascades) and write a read-only handoff without turning diagnosis into permission."
@@ -80,7 +80,7 @@
     {
       "id": "contribution-intake",
       "name": "Contribution Intake",
-      "version": "1.0.19",
+      "version": "1.0.22",
       "path": "skills/contribution-intake/SKILL.md",
       "domain": "campaigns",
       "description": "Turn a suggestion about the agent surface into a classified, evidence-checked and redacted proposal, filed on this repository tracker only with attended approval."

package/src/cli.mjs

@@ -296,15 +296,18 @@ Usage:
   campaigns-os start (--spec <json> | --map-id <id>) --source <html-dir> --target <page-kit-dir> --template-family <family>
                      [--brief <yaml|json>] [--proxy-base <url>] [--cached-spec] [--theme-policy <inspect_only|auto|off>]
                      [--wrapper-policy <strip_document_wrappers|preserve_document_wrappers|not_required|unknown>] [--design-manifest <path>]
-                     [--allow-uncertified-template "<reason>"] [--order-path-depth <off|common|full>] [--no-run-session] [--force]   # --force overwrites an assembly report that carries stage evidence (destructive; prints the cleared stage keys) and regenerates a stale Design Source Package an earlier intake synthesized and nobody changed
+                     [--allow-uncertified-template "<reason>"] [--order-path-depth <off|common|full>]
+                     [--deploy-target <target>] [--preview-url <url>] [--production-url <url>] [--no-run-session] [--force]   # --force overwrites an assembly report that carries stage evidence (destructive; prints the cleared stage keys) and regenerates a stale Design Source Package an earlier intake synthesized and nobody changed
   campaigns-os prepare-build (--spec <json> | --map-id <id>) --source <html-dir> --target <page-kit-dir> --template-family <family>
                              [--brief <yaml|json>] [--proxy-base <url>] [--cached-spec] [--theme-policy <inspect_only|auto|off>]
                              [--wrapper-policy <strip_document_wrappers|preserve_document_wrappers|not_required|unknown>] [--design-manifest <path>]
-                             [--allow-uncertified-template "<reason>"] [--order-path-depth <off|common|full>] [--no-run-session] [--force]
+                             [--allow-uncertified-template "<reason>"] [--order-path-depth <off|common|full>]
+                             [--deploy-target <target>] [--preview-url <url>] [--production-url <url>] [--no-run-session] [--force]
   campaigns-os build (--spec <json> | --map-id <id>) --source <html-dir> --target <page-kit-dir> --template-family <family>
                      [--brief <yaml|json>] [--proxy-base <url>] [--cached-spec] [--theme-policy <inspect_only|auto|off>]
                      [--wrapper-policy <strip_document_wrappers|preserve_document_wrappers|not_required|unknown>] [--design-manifest <path>]
-                     [--allow-uncertified-template "<reason>"] [--order-path-depth <off|common|full>] [--no-run-session] [--force]   # intake alias for prepare-build + doctor
+                     [--allow-uncertified-template "<reason>"] [--order-path-depth <off|common|full>]
+                     [--deploy-target <target>] [--preview-url <url>] [--production-url <url>] [--no-run-session] [--force]   # intake alias for prepare-build + doctor
   campaigns-os doctor --packet <campaign-runtime.build.json> [--context <json>] [--report <json>] [--strip-paths] [--write] [--no-write] [--doctor-out <path>] [--proxy-base <url>] [--no-live-refs] [--json]   # inspection by default; --doctor-out requires --write; --no-write wins. When the packet's built _site/<route>/ exists and a public Campaigns API key resolves (packet, its local CampaignSpec, or the declared campaign-key env var), doctor makes one read-only GET of {proxy-base}/api/campaign under X-Campaign-Key to check each built page's shipping and package refs against the live campaign; --proxy-base overrides the canonical proxy (https, or a loopback host over http). --no-live-refs skips the read and records not_run with reason disabled. No key, no built page, or a failed read records derived.live_campaign_refs as not_run with its reason. Only doctor and qa run make this read; other commands that run doctor record not_read
   campaigns-os doctor --built <page-kit-target-repo> --family <family> [--slug <slug>] [--base-url <url>] [--emit-packet [path]] [--json]   # L7: doctor a built _site/ with no Build Packet
   campaigns-os bundle check --packet <campaign-runtime.build.json> [--require-qa] [--json]   # validate the canonical migration/readback JSON bundle; never substitutes markdown

package/src/content-residue.mjs

@@ -1,23 +1,22 @@
 // Rendered-output content-residue scan + proof-attestation gate.
 //
 // Scans BUILT campaign output (_site HTML), not frontmatter: layout- or
-// script-rendered proof/urgency chrome only exists after the build, which is
-// why frontmatter-level checks missed the hardcoded rating/countdown chrome.
+// script-rendered chrome only exists after the build, which is why
+// frontmatter-level checks missed the hardcoded starter countdown chrome.
 //
-// Pattern provenance: the generic anti-pattern classes distilled from the
-// 2026-07 winning-campaign content audit (invented counts, fabricated
-// verified-buyer chrome, fictional bylines, borrowed authority, science
-// theater, scarcity theater, fake comparisons, unlinked press marquees).
-// Only GENERIC patterns and the public starter-template demo strings live
-// here; merchant-specific residue fingerprints are deliberately not carried
-// in this public package.
+// What it looks for is template residue, never the merchant's own copy: the
+// public starter-template demo strings, bracket-style demo stubs, and the
+// literal needs-merchant-input marker. Proof and urgency content the merchant
+// supplies (reviews, ratings, "Verified Purchase" labels, stock counters,
+// countdowns) is the merchant's responsibility and is not scanned. No
+// merchant-specific fingerprints are carried in this public package.
 //
-// Posture (fail closed, two tiers):
-// - hard: the literal needs-merchant-input marker, and urgency chrome
-//   rendered without verified offer urgency — blockers (collect-inputs).
-// - review: anti-pattern hits and demo/placeholder residue — warnings that
-//   feed the review/attestation queue; a hit means "remove or demand
-//   brief/source evidence", never "make it more plausible".
+// Posture (two tiers):
+// - hard: the literal needs-merchant-input marker, and starter countdown
+//   chrome on a brief-backed build whose brief does not verify the offer
+//   urgency — blockers (collect-inputs).
+// - review: demo/placeholder residue — warnings; a hit means an unreplaced
+//   demo slot or a stale template.
 import { existsSync, readFileSync, readdirSync, statSync } from "node:fs";
 import { join, relative } from "node:path";
 
@@ -55,63 +54,6 @@ export const DEMO_RESIDUE_TERMS = Object.freeze([
   "Sell-Out Risk: High",
 ]);
 
-// Generic anti-pattern classes (review tier). Each id is stable so the
-// attestation/review UX can key on it.
-export const CONTENT_ANTI_PATTERNS = Object.freeze([
-  {
-    id: "invented_counts",
-    antiPattern: 1,
-    rule: "Counts/ratings/percent-recommend claims require a real, brief-sourced basis.",
-    // Count branch requires a proof-scaled number (comma groups, 4+ digits, or
-    // a trailing +) so ordinary commerce quantities ("Choose 3 pairs and
-    // save") never enter the review queue; "pairs"/"sold" dropped as nouns
-    // for the same reason. Small invented counts are a knowingly accepted gap.
-    regex: /\b(?:\d{1,3}(?:,\d{3})+|\d{4,}|\d+\+)\s+(?:reviews?|ratings?|customers?|users?|famil(?:y|ies)|wearers?|people)\b|\b(?:4\.[5-9]|5\.0)\s*(?:\/\s*5|stars?)|\b(?:9[0-9]|100)%\b[^<]{0,60}\b(?:recommend|reported|said|would)\b/i,
-  },
-  {
-    id: "verified_buyer_chrome",
-    antiPattern: 2,
-    rule: "'Verified' labels must resolve to a real approved review source.",
-    regex: /Verified\s+(?:Buyer|Customer|Purchase)|What\s+(?:Our\s+)?Customers\s+(?:Think|Say)|Real\s+(?:People|Customers)[^<]{0,20}Real\s+(?:Results|Relief)|5[- ]Star\s+Review/i,
-  },
-  {
-    id: "byline_persona",
-    antiPattern: 3,
-    rule: "Advertorial identities must be real, brief-supplied, and authorized.",
-    regex: /Mom\s+of\s+Two|Consumer\s+Report|Review\s+Team|Wellness\s+Educator|Licensed\s+(?:Physiotherapist|Professional)/i,
-  },
-  {
-    id: "borrowed_authority",
-    antiPattern: 4,
-    rule: "Expert/clinician/institution references require name, credential, permission, and source.",
-    regex: /\bDr\.\s+[A-Z]|\bM\.?D\.?\b|doctor[- ]recommended|clinically\s+(?:recognized|recommended)|expert\s+(?:says|recommends)/i,
-  },
-  {
-    id: "press_marquee",
-    antiPattern: 8,
-    rule: "Press mentions require a brief-supplied working URL for the exact merchant and product.",
-    regex: /As\s+Seen\s+(?:On|In)|Featured\s+(?:On|In)/i,
-  },
-  {
-    id: "science_theater",
-    antiPattern: 9,
-    rule: "Study/clinical/certification claims require citation metadata and approved wording.",
-    regex: /peer[- ]reviewed|science[- ]backed|backed\s+by\s+science|stud(?:y|ies)\s+(?:show|prove|confirm)|researchers\s+found|clinically\s+(?:proven|shown|tested)|NASA[- ]developed/i,
-  },
-  {
-    id: "scarcity_theater",
-    antiPattern: 10,
-    rule: "Urgency renders only from a real, approved promotion window or live inventory source.",
-    regex: /ENDS\s+AT\s+MIDNIGHT|Offer\s+Expires|Deal\s+Ending|Only\s+\d+\s+(?:Units\s+)?Left|Stock\s+(?:Levels?\s+)?Low|\d+%\s+Sold|Sell[- ]?Out\s+Risk|supplies\s+are\s+limited/i,
-  },
-  {
-    id: "fake_comparison",
-    antiPattern: 11,
-    rule: "Tested-N/showdown framing requires a brief-supplied comparison matrix and test record.",
-    regex: /(?:we\s+)?tested\s+\d+\s+(?:contenders|products|devices|gloves|combinations|brands)|only\s+one\s+(?:survived|worked|stood)|Competitor\s+[12]\b/i,
-  },
-]);
-
 const ENTITIES = new Map([
   ["&amp;", "&"], ["&lt;", "<"], ["&gt;", ">"], ["&quot;", '"'],
   ["&#39;", "'"], ["&apos;", "'"], ["&nbsp;", " "], ["&#8217;", "’"], ["&#8212;", "—"],
@@ -168,13 +110,12 @@ function excerptAt(html, index, span = 80) {
 }
 
 // Pure scan of one rendered HTML document. Returns { hard: [], review: [] };
-// each finding: { id, tier, rule?, excerpt }. Hard checks run on the markup
-// view (attributes count, comments/scripts do not); review checks run on the
-// visible-text view for precision, except exact-string demo terms and bracket
-// stubs which run on markup so attribute residue is still caught.
+// each finding: { id, tier, rule?, excerpt }. The hard checks and the demo
+// terms run on the markup view (attributes count, comments and script/style
+// bodies do not), so attribute residue is still caught; bracket stubs run on
+// the same view with tags stripped, so CSS attribute selectors never match.
 export function scanRenderedHtml(html, { urgencyVerified = false } = {}) {
   const markup = markupView(typeof html === "string" ? html : "");
-  const text = visibleText(typeof html === "string" ? html : "");
   const hard = [];
   const review = [];
 
@@ -205,19 +146,6 @@ export function scanRenderedHtml(html, { urgencyVerified = false } = {}) {
     }
   }
 
-  for (const pattern of CONTENT_ANTI_PATTERNS) {
-    if (pattern.id === "scarcity_theater" && urgencyVerified) continue;
-    const match = pattern.regex.exec(text);
-    if (match) {
-      review.push({
-        id: pattern.id,
-        tier: "review",
-        antiPattern: pattern.antiPattern,
-        rule: pattern.rule,
-        excerpt: excerptAt(text, match.index),
-      });
-    }
-  }
   return { hard, review };
 }