@wix/agent-skills 1.36.0 → 1.36.1

package/skills/wix-replatform/resources/rp-execute-import/scripts/shipping-estimate-audit.js

@@ -1,70 +0,0 @@
-#!/usr/bin/env node
-'use strict';
-
-// The finished-project shipping-estimate audit. Read-only against Wix: it GETs
-// crosswalked shipping options and never POSTs or PATCHes. Locally it may upsert ONE crosswalk row
-// per adopted `recreated:<id>` decision, then rewrites execution/shipping-estimates.json, the
-// completion report's shipping operatorActions, and the post-execution handoff.
-//
-//   node skills/wix-replatform/resources/rp-execute-import/scripts/shipping-estimate-audit.js --project-dir <dir>
-//   node skills/wix-replatform/resources/rp-execute-import/scripts/shipping-estimate-audit.js --project-dir <dir> --list <code>
-//
-// `--list <code>` makes no Wix call: it prints every option recorded under that operatorActions
-// code in execution/shipping-estimates.json, for relaying a long list to the Cutover Operator.
-
-const path = require('node:path');
-const { readEnvFile } = require('../../../lib/config-env.js');
-const { createWixClient } = require('../../rp-target-wix/lib/wix-writers.js');
-const { runShippingEstimateAudit, listShippingEstimateItems } = require('../../rp-target-wix/lib/shipping-option-stage.js');
-
-function parseArgs(argv) {
-  const args = {};
-  for (let i = 0; i < argv.length; i += 1) {
-    const arg = argv[i];
-    if (arg === '--project-dir') args.projectDir = argv[++i];
-    else if (arg === '--list') args.list = argv[++i];
-    else if (arg === '--help' || arg === '-h') args.help = true;
-    else throw new Error(`unknown argument: ${arg}`);
-  }
-  return args;
-}
-
-async function wixFromProject(projectDir) {
-  const env = await readEnvFile(path.join(projectDir, 'config', 'wix.env'));
-  const authToken = env.WIX_AUTH_TOKEN || env.WIX_API_KEY;
-  if (!authToken || !env.WIX_SITE_ID) throw new Error('config/wix.env must provide WIX_AUTH_TOKEN (or WIX_API_KEY) and WIX_SITE_ID');
-  return createWixClient({ authToken, siteId: env.WIX_SITE_ID });
-}
-
-async function main(argv = process.argv.slice(2), { wix = null, log = console.log } = {}) {
-  const args = parseArgs(argv);
-  if (args.help || !args.projectDir) {
-    log('Usage: shipping-estimate-audit.js --project-dir <dir> [--list <code>]');
-    return { ok: Boolean(args.help) };
-  }
-  const projectDir = path.resolve(args.projectDir);
-  if (args.list) {
-    const items = await listShippingEstimateItems(projectDir, args.list);
-    log(JSON.stringify({ ok: true, code: args.list, count: items.length, items }, null, 2));
-    return { ok: true, items };
-  }
-  const client = wix || await wixFromProject(projectDir);
-  const result = await runShippingEstimateAudit(client, { projectDir });
-  log(JSON.stringify({
-    ok: true,
-    operatorActions: result.fragment.operatorActions.map((row) => ({ code: row.code, affectedCount: row.affectedCount })),
-    crosswalkUpserts: result.audit.crosswalkUpserts.length,
-    completionReportUpdated: Boolean(result.completionReport),
-    handoff: result.handoff ? { ok: result.handoff.ok, reason: result.handoff.reason || null } : null,
-  }, null, 2));
-  return { ok: true, result };
-}
-
-if (require.main === module) {
-  main().catch((error) => {
-    console.error(error && error.message ? error.message : error);
-    process.exit(1);
-  });
-}
-
-module.exports = { main, parseArgs };

package/skills/wix-replatform/resources/rp-execute-setup/SKILL.md

@@ -1,482 +0,0 @@
----
-name: rp-execute-setup
-description: >-
-  Verifies and provisions Wix-side setup required before import. Use after codegen when
-  machine-readable setup artifacts must be validated or executed against the target site.
----
-
-# rp-execute-setup
-
-Verify that required Wix-side setup exists and is ready for import.
-
-## Purpose
-
-This skill validates the prerequisites discovered by `rp-setup-discovery`. It can also drive the setup work when the environment and permissions allow it.
-
-## Required inputs
-
-- `migrations/<project>/setup/setup-plan.json`
-- `migrations/<project>/setup/setup-requirements.json`
-- `migrations/<project>/execution/execution-manifest.json`
-- `migrations/<project>/config/wix.env` or equivalent environment values
-- access to the target Wix environment or to exported evidence from that environment
-
-Prefer the machine-readable setup artifacts above. Markdown setup summaries are secondary
-renderings for humans, not the primary execution contract.
-
-## Config
-
-Prefer project-local config over ad hoc shell state. `config/wix.env` should exist before
-setup verification/provisioning and contain:
-
-```bash
-WIX_SITE_STRATEGY=
-WIX_SITE_ID=
-WIX_AUTH_TOKEN=
-```
-
-`WIX_SITE_STRATEGY` is always required. `WIX_SITE_ID` is required before setup
-verification/provisioning begins. If the strategy is `new` and no site has been created
-yet, halt to needs-user and route back to the site-creation step rather than asking for an
-existing site ID.
-
-**Studio/Harmony destinations.** A new Editor site is bound only after
-`orchestration/destination.json` is `verified` (actual editor and an `unpublished` readback).
-Setup treats it like any new site: mint `WIX_AUTH_TOKEN` for that `WIX_SITE_ID` through
-`mint-token.sh`, confirm it with a harmless target read before the first write, mute site
-notifications first (`WIX_SITE_STRATEGY=new` regardless of site type), and install/verify
-every required app — never infer installed apps, Catalog version or backend readiness from the
-editor type or template. Never publish the Editor site; its website and publication remain
-operator handoff items.
-
-**When `WIX_SITE_ID` names a site this run did not create, setup changes posture: verify
-and fill gaps, never provision from scratch.** The site is already in use, so treat
-everything in it as pre-existing state to work around rather than a blank slate:
-
-- **Expect apps, collections and fields to exist already.** Install only the delta the
-  mapping actually needs. An app that is already installed is a PASS, not a step to redo,
-  and re-provisioning is how a working site acquires duplicate collections.
-- **Never delete or recreate an entity to "fix" a mismatch.** A collection whose schema
-  differs from what the mapping expects is a `blocked` requirement with a remediation note
-  — the owner decides, not this skill.
-- **A `V1_CATALOG` verdict is terminal here.** The replacement-site recovery in
-  `resources/rp-destination/` applies only to a site this run scaffolded. Record the
-  blocker, write nothing to Stores, halt to needs-user.
-- **When the approved plan requests a CMS mirror, provision the on-site `ImportCrosswalk`
-  collection** (see "Import crosswalk CMS mirror" below). Whether a mirror is requested at all
-  is the owner's call and the mapper's setting — it is optional by design. Once it *has* been
-  requested, two things follow and neither one counts as the other: provisioning is a required
-  setup step **even on a destination the owner already had** (an existing site is not a reason
-  to treat it as already satisfied), and provisioning is **not the deliverable** — the run still
-  owes the post-execution snapshot pass that keeps the collection current.
-- Record which requirements were already satisfied versus newly provisioned in
-  `setup/setup-verification.json`. On a site the user owns, "we changed nothing here" is
-  itself a result worth reporting.
-
-`WIX_AUTH_TOKEN` is the canonical Wix credential key for this project
-flow; for CLI-scaffolded headless sites it holds the site write credential (a CLI token
-sent as a Bearer token). **Never print secret values.** Mint the token without printing it
-to the transcript by running `scripts/mint-token.sh` from the migration project root:
-
-```bash
-bash migrations/<project>/scripts/mint-token.sh
-```
-
-The canonical copy lives at
-`skills/wix-replatform/resources/rp-execute-setup/scripts/mint-token.sh`.
-`rp-import-codegen` copies it into `migrations/<project>/scripts/` at scaffolding time —
-do not write it from scratch. The script reads `WIX_SITE_ID` from `config/wix.env`, calls
-`npx @wix/cli@latest token --site "$WIX_SITE_ID"`, captures stdout (token shape:
-`OauthNG.JWS.<base64>.<base64>.<sig>`), writes it directly into `config/wix.env` as
-`WIX_AUTH_TOKEN`, and prints only a char-count confirmation. Do NOT run the token command
-raw in a Bash tool call — it prints the credential to transcript.
-
-If `WIX_SITE_ID` is missing for a RePlatform `new site` + `headless` flow, the recovery
-path is `resources/rp-destination/`, which scaffolds via
-`npm create @wix/new@latest headless`. The account-level Projects API is
-deprecated for this workflow. **Note:** the scaffold does not install Wix Stores — this
-skill (setup) is where Wix Stores and other required apps get installed (via the
-`wix-manage` skill / app-install path), then verified, before import.
-
-Treat `migrations/<project>/config/*.env` as secret-bearing once they may contain real
-values. Do not verify them with whole-file reads that echo contents into tool output.
-Only check existence plus `present` / `blank` / `missing` status for required keys.
-
-## Workflow
-
-1. Resolve the active project.
-2. Read the machine-readable setup artifacts.
-3. Verify each required app, collection, schema, field, and permission through the shared
-   setup runtime contract.
-   If setup requirements came from domain knowledge, preserve the originating `targetRef`
-   in verification output so later execution warnings can be traced back to the selected
-   entity guidance.
-4. Record pass, fail, or blocked status for each item.
-5. If execution is allowed, perform missing setup steps through the shared setup runtime
-   and re-verify.
-6. Save the verification results and setup execution artifacts.
-7. **Carry the source store's own configuration.** See the section below — this is a
-   required step, not an optional extra, and it is the one every run before it skipped.
-
-## Carry the source store's own configuration
-
-A migrated site that publishes with a blank business address is not a cosmetic miss: it is a
-whole class of source data that no run ever read, because two independent obstacles each made
-the route look like a dead end (the REST index advertises only the parameterized settings
-route, and the WooCommerce consumer key 401s on it while the WordPress application password
-succeeds). Nothing reported it missing, because no domain owned it.
-
-Three steps, in order:
-
-1. **Capture.** Run `rp-source-wordpress/scripts/capture-store-settings.js <projectDir>`.
-   Deterministic; writes `data/store-settings-general.json`. Do not hand-roll the fetch — the
-   script exists specifically because the credential and the route shape are both traps.
-2. **Write the business address.** Build the payload with
-   `rp-target-wix/lib/store-config-build.js`'s `buildBusinessContactInput`, write it with
-   `wix-writers.js`'s `updateBusinessContact`, then read it back with `getSiteProperties` and
-   compare. The read-back is not optional: the update returns an empty body, so a 200 proves
-   only that the request was accepted. See `domains/site/entities/business-contact.json`.
-   NEVER assemble the `fields.paths` mask by hand — a path listed but not sent is CLEARED, and
-   Wix's own documented example demonstrates that hazard rather than the safe pattern.
-3. **Report the rest at the gate.** `collectReportOnlySettings` returns currency, selling
-   countries, ship-to countries, tax on/off, coupons on/off and price format, each with its
-   source value and why it matters. These are NOT written by this pipeline — surfacing them
-   beside the destination's current values is what turns "we didn't migrate it" from an
-   invisible omission into a decision the merchant can make in one look.
-
-The captured address also feeds the shipping step: with it, a collection point whose source
-carries no address is proposed ("your store address is X — is that where customers collect?")
-instead of prompting blank. See `shipping-build.js`'s `resolvePickupAddressSource`.
-
-## Execute the setup artifacts — do not re-derive setup from prose
-
-Setup execution should follow the approved machine artifacts and the shared setup runtime.
-It should not rebuild setup decisions from markdown or ad hoc reasoning when
-`setup/setup-plan.json`, `setup/setup-requirements.json`, and `execution/execution-manifest.json`
-already exist.
-
-This skill owns execution of those artifacts. It does not own redefining the setup plan
-or creating a separate setup approval checkpoint.
-
-The shared executor uses `startSetupRun` and `bindSetupStep` to issue a capability bound to
-the current plan, destination and named step. It admits registered setup operations and
-writes for that step's `entityRefs`; it cannot import records or send arbitrary requests.
-Setup, import, quick and disposable-probe process marks are exclusive. Do not pass a
-caller-authored phase or substitute a general import/probe client for a setup client.
-
-For a step declaring `referenceKeys`, capture `referenceBindings` on its passed requirement
-in `setup/setup-verification.json` from the capability-bound executor's actual target
-read-back. Reuse a successful operation's read result when available; otherwise perform the
-bounded read for each distinct declared target. Bind the receipt to `siteId`, `planDigest`
-and the source keys/paths. Guessed IDs, copied source IDs, raw/unrelated reads and write-only
-responses are not verified bindings. Imports resolve these values through the gate only
-after every bound setup step passes; successful partial setup never unlocks a dependent.
-
-Dry-run setup uses the same setup plan and setup executor as live setup. When `DRY_RUN`
-is enabled by config or `--dry-run`, every setup step must first be reduced to a
-structured intent describing the REST request, SDK operation, MCP tool call, or CLI
-command that live setup would use. The shared setup runtime then captures that intent,
-marks the step `planned_dry_run`, and must not invoke Wix MCP tools, Wix CLI commands,
-SDK calls, or fetch calls that access or mutate Wix account/site state.
-
-Do not override `DRY_RUN=true` with `--no-dry-run` for setup verification or provisioning
-unless the user has explicitly approved leaving dry-run for setup. Prefer to avoid that
-override entirely when a dry-run or plan/report can answer the question. The one allowed
-live action while a project otherwise remains in dry-run mode is the separate new-site
-creation step handled upstream by `wix-replatform`; this skill must not treat that exception
-as permission to run live setup writes or live setup verification probes.
-
-Dry-run setup must not update `setup/setup-verification.json` in a way that claims a Wix
-capability, app installation, collection, or site exists. Write a separate dry-run setup
-report or clearly dry-run-scoped observations instead.
-
-## Provisioning — exhaust programmatic options before declaring anything "manual"
-
-Default to provisioning via API. Do **not** label a requirement "manual" or "owner
-action" until you have confirmed no API can do it.
-
-The preferred contract is a **shared setup runtime** owned by `rp-target-wix`, executed
-against the machine setup artifacts produced upstream. This skill may use available Wix
-API/MCP surfaces as the transport beneath that runtime, but the contract at the
-RePlatform level is:
-
-- setup execution consumes machine setup artifacts
-- setup execution follows shared runtime behavior
-- setup provisioning is not re-planned live by the agent
-
-The approval gate is unchanged: no setup write before the user accepts the execution
-plan.
-
-If a helpful Wix tool surface is available in the runtime, it may be used beneath the
-shared setup runtime for verification or transport. If no such surface is available, do
-not treat that alone as a blocker; continue with the shared setup/runtime contract and
-verified `rp-target-wix` behavior, marking unverified items where needed.
-
-Only proceed in a docs-only/read-only posture when the MCP is genuinely unavailable and
-the step can still produce useful non-destructive output.
-
-Concrete mechanisms:
-
-- **Mute site notifications FIRST.** When the setup artifacts carry the
-  `mute-site-notifications` requirement (always for `WIX_SITE_STRATEGY=new`; opt-in for
-  existing sites), execute it **before every other setup write** — immediately after the
-  target site is available and `WIX_AUTH_TOKEN` is minted, and before app installs,
-  collection creation, or any other provisioning — so setup writes themselves cannot
-  fire notifications. Use the `muteSiteNotifications` primitive from
-  `rp-target-wix/lib/wix-writers.js` (VERIFIED 2026-08-04) with a project-identifying
-  reason (`RePlatform migration — <project>`); verify via `getSiteMuteState` →
-  `muted: true` (verification method `status-read`; an idempotent re-mute is only a
-  documented fallback, method `idempotent-recall`). Record the result in
-  `setup/setup-verification.json` on the requirement at call time — status
-  (`pass`/`fail`/`blocked`), timestamp, and verification method — like any other
-  verified item; downstream reports read this recorded state, never infer it. **AUTH
-  TRAP:** the endpoints accept user tokens only — the CLI-minted `OauthNG` site token
-  works; an account API key gets an empty-body 403. **A failed mute is a blocker, not a
-  warning:** the run halts to needs-user and never proceeds to import writes — no
-  degraded mode, no continue-anyway. Never call `unmuteSiteNotifications` from this
-  skill — unmute is an explicit owner request handled at the orchestrator level.
-  Record the provision outcome through the standard `rp-telemetry` recorder like any
-  other notable boundary (an `error` event with `error_code` on failure; the
-  existing-site opt-in surfaces via the approval gate's `user_decision` event) — no new
-  telemetry surface.
-- **Installing / enabling Wix apps (Blog, Members, etc.) IS automatable.** Use the
-  App Installation API:
-  1. Pre-check with `POST /apps-installer-service/v1/app-instance/is-permitted-to-install`
-     (read-only) to see whether the identity may install the app.
-  2. If permitted, install with `POST /apps-installer-service/v1/app-instance/install`.
-     Body (all fields required — confirmed by live 400s): `{ appInstance: { appDefId,
-     enabled: true }, tenant: { tenantType: "SITE", id: <siteId> }, installType:
-     "INSTALL_TYPE_SITE", appsInstallOptions: {} }`. (The `is-permitted-to-install`
-     pre-check uses a *different*, oneof-based body and is informational only — if its
-     validation fights you, skip it and rely on `/install`.)
-  3. List current state with `GET /apps-installer-service/v1/app-instances`.
-  - **Ground `appDefId` from the official "Apps Created by Wix" table**
-    (`/docs/api-reference/articles/work-with-wix-apis/platform/about-apps-created-by-wix`),
-    NOT from a docs *example* — e.g. the install-app example uses
-    `1380b703-…`, which is **Wix eCommerce**, not Blog. Installing the wrong app on a
-    live site is a real hazard; verify the ID maps to the app you intend.
-  - **Installing Wix Stores on a site this run created provisions Catalog V3
-    unconditionally** — Catalog V3 is now guaranteed at provisioning regardless of
-    scaffold template, so there is no
-    verification step here for that case. This does not apply to an existing site this
-    run did not create — see "A `V1_CATALOG` verdict is terminal here" above for that
-    case, which is unchanged.
-- **Wix Data / CMS collections (the `WDE0110: Wix Code not enabled` case).** Enable Wix
-  Data by **installing the Wix Data app `appDefId e593b0bd-b783-45b8-97c2-873d42aacaf4`**
-  via the App Installation API (same `/install` body shape as any other app; it also
-  auto-installs a dependency app `1a711f05-2040-47df-a9f0-4f9cddb4c3c6`). Once installed,
-  plain REST `POST /wix-data/v2/collections` creates **NATIVE** collections with no
-  `WDE0110` — no code editor toggle, no custom app needed. **Verified live 2026-06-10**
-  on a fresh free site (install → 200; collection create → 200 `collectionType: NATIVE`).
-  - This is the preferred path. The older data-collections-extension app (authoring a
-    custom app that declares collections) is now a **fallback** — only needed if
-    you must declare collection schemas at install time, and it still can't express
-    `REFERENCE` fields (add those after install via `create-field`).
-  - Note: the standalone "Wix CMS" app (`appDefId 675bbcef-…`) is **not** installable
-    (`is-permitted-to-install` → `false`) — do **not** use it; use `e593b0bd-…`.
-- **Import crosswalk CMS mirror — OPTIONAL, provisioned only when a mirror mode is
-  requested.** Native Wix entities use local crosswalk state under
-  `migrations/<project>/state/crosswalk/` as the sole runtime authority for idempotency; a
-  CMS mirror is never a substitute for it and never required for correctness. Do not
-  provision `ImportCrosswalk` by default for every project — Wix CMS quotas are plan-based
-  and shared across every custom collection on the site, so an unconditional mirror can
-  spend a meaningful fraction of a lower-tier plan's total item quota on operational
-  migration state the site owner never asked to store. Provision it only when the mapper's
-  `cmsMirror` setting for the project is something other than `none` (typically an
-  existing-destination flow where the user opted into site-local reference data, so a later
-  re-import from another project or a different surface can see "what has already been
-  imported here" instead of duplicating it). When a mirror IS requested, provisioning alone
-  is not the deliverable: the mirror is a compact snapshot uploaded AFTER
-  execution, not written to inline during it. `rp-import-codegen` generates that snapshot as a
-  distinct post-execution step, gated on the same `cmsMirror` mode, which reads the finished
-  local crosswalk and uploads it through
-  `rp-target-wix/lib/wix-writers.js`'s `syncImportCrosswalk` (see `rp-execute-import`'s
-  "Import & idempotency"). LIVE-VERIFIED a project whose collection was provisioned early and
-  never written to again left every already-imported record with no on-site trace at all until
-  a one-time backfill caught it up, so provisioning must not be treated as satisfied by
-  itself — a provisioned collection is only trustworthy once that post-execution pass has run
-  over the local crosswalk. A mirror requested but never snapshotted is a reportable
-  shortfall, not a completed setup. After enabling
-  Wix Data, create it with `POST /wix-data/v2/collections` and fields such as
-  `entityType` (TEXT), `sourceId` (TEXT), `sourceStableKey` (TEXT), `targetId` (TEXT),
-  `targetType` (TEXT), and `updatedAt` (DATETIME/TEXT). Do not provision this collection
-  as the default native-entity idempotency mechanism. If upstream artifacts still call the
-  optional mirror `MigrationRefs`, normalize them here rather than creating both
-  collections.
-- **Genuinely manual (no API exists):** upgrading the storage plan, generating
-  external-system credentials (e.g. a WordPress Application Password), and
-  account-level billing. These are the only categories that may be reported as manual —
-  and only after confirming no API covers them.
-
-## Inventory prerequisites for product imports
-
-For planned variant inventory, resolve the intended Stores location with
-`rp-target-wix/lib/stores-inventory.js` → `resolveInventoryLocation(wix, locationId?)`.
-Do not create a location if the lookup is empty or ambiguous. Verify inventory-read access.
-Inventory create and update require their own write permissions in addition to product
-create; a token field or configured scope name is not proof that those permissions work.
-
-On an explicitly selected, already-muted disposable target, run:
-
-```bash
-node resources/rp-target-wix/scripts/verify-stores.js stores inventory-import --env <test-target-config> --artifact <verification-json>
-```
-
-This creates hidden synthetic products, verifies bulk stock create, tracked/untracked updates,
-inline stock, and a no-write rerun, then deletes only those probe products. It does not mute
-or unmute a site. Record actual target, token context, timestamp, assertions, and cleanup in
-the setup receipt; a failed probe cannot satisfy the inventory requirement. A disposable-site
-receipt verifies that token/site only: run the authorized canary under the real destination's
-own setup approval before its full import. Reuse current evidence rather than probing per product.
-
-## Artifact to create or update
-
-- `migrations/<project>/setup/setup-verification.json`
-- `migrations/<project>/setup/review/setup-verification.md`
-- audit/report artifacts emitted by the shared setup runtime
-- dry-run request captures in `migrations/<project>/state/attempts/wix-request-captures.ndjson`
-  when setup is run with dry-run enabled
-
-Stores live setup checks that require a probe record must use the shared rp-target-wix
-verification CLI, not ad hoc snippets. For subscription support, run:
-
-```bash
-node skills/wix-replatform/resources/rp-target-wix/scripts/verify-stores.js stores subscription-create \
-  --artifact migrations/<project>/setup/stores-subscription-verification.json \
-  --proposal-artifact migrations/<project>/setup/contract-ledger-proposal.json
-```
-
-Keep the JSON verification artifact and contract-ledger proposal alongside setup
-verification. The proposal is not itself shared product knowledge; the orchestrator must
-promote accepted proposal data into `rp-target-wix/domains/**/entities/*.json` in the same
-session or record a deferral reason. If cleanup fails, do not mark the probe as clean;
-preserve the warning and run the emitted `stores delete-probe` recovery command after
-permissions or target state are fixed.
-
-## Verification output format
-
-For each requirement capture:
-
-- requirement name
-- expected state
-- observed state
-- status: passed, failed, blocked
-- remediation needed
-
-The machine-readable verification artifact should also preserve:
-
-- stable requirement ID
-- checkpoint/provisioning step ID when applicable
-- verification evidence reference
-- automation mode: `automatable | manual | blocked | unverified`
-
-## Optional media reachability verification
-
-When the migration includes media import by source URL, check whether discovered media
-URLs are publicly reachable by Wix. If the source URL is `localhost`, `127.0.0.1`, or a
-private-only host, mark **media import** as `blocked` or `deferred`, but do not block
-unrelated non-media entities. This is optional setup and, as far as we know today, affects
-only Wix Media import.
-
-Record the user's chosen path in `setup/setup-verification.json` and render it into the
-review markdown:
-
-- **Tunnel media URLs:** ask the user to expose the source through a public HTTPS tunnel,
-  then use that URL for `WP_BASE_URL` / `SOURCE_URL` or rewrite media URLs to that base.
-- **Skip/defer media:** proceed only if the execution plan clearly says media and any
-  media-dependent references (hero images, galleries, downloads) will be skipped or
-  deferred.
-
-Ngrok quick setup for macOS:
-
-```bash
-brew install ngrok
-ngrok config add-authtoken "<YOUR_AUTHTOKEN>"
-ngrok http 8090
-export WP_BASE_URL=https://<id>.ngrok-free.app
-```
-
-## Runtime policy
-
-Split this skill's work by side effect:
-
-- **Verification is read-only** — checking what's installed, what's missing, and what's
-  genuinely manual. It runs **before** the execution-plan acceptance gate and feeds the
-  plan.
-- **Provisioning writes** — installing apps, enabling Wix Data (via the data-collections
-  enabler), creating collections, adding fields — happen **only after** the user accepts
-  the execution plan. **No site write before acceptance.** Once accepted, the "Migrate"
-  consent covers the individual writes, so don't re-prompt per app/collection. Halt to
-  needs-user only for genuinely manual items (storage-plan upgrade) or a
-  missing/invalid credential.
-
-The execution behavior itself should come from the shared setup runtime and approved
-setup artifacts, not from improvised per-run logic in this skill.
-
-## Guardrails
-
-- Never report setup as complete without evidence.
-- Prefer machine-readable setup verification artifacts over prose-only reporting.
-- Before marking an item blocked or manual, confirm no API can perform it (see
-  Provisioning above). Reserve "manual" for storage/billing/external-credential steps.
-- If credentials or permissions are genuinely missing, mark the item blocked and state
-  the exact API that was refused and why.
-- Do not start import execution from this skill.
-- Do not reinterpret setup requirements from markdown when machine artifacts exist.
-
-## Provisioning user-defined extended fields (Data Extension Schema)
-
-Never build a Data Extension Schema update by hand. Use
-`rp-target-wix/lib/data-extension-schema.js` and send the request it returns.
-
-The reason is a single API property: **Update Data Extension Schema is a `PUT` that overrides the
-stored schema**, and `jsonSchema` is required. Sending only the fields this migration needs
-therefore DELETES every field the merchant created, silently and permanently, on their own data.
-`planDataExtensionSchemaProvisioning()` reads the existing schema, merges into it, and refuses the
-update when it would drop, retype, narrow or re-classify anything already there.
-
-The order it enforces:
-
-1. List the existing schema with `fields=ARCHIVED` — archived fields are hidden by default, and an
-   archived key cannot be reused, so the collision check is blind without them.
-2. Select the schema by `namespace` (`_user_fields`). List returns global and app schemas
-   alongside the user-defined one; picking by position merges into somebody else's schema.
-3. Plan. The result is `create`, `update`, `noop` or `blocked` — `noop` is what a repeated run
-   returns, and `blocked` carries the reason.
-4. Send the returned request. An update carries the schema `id` and the **current** `revision`;
-   the API uses the revision to reject conflicting changes.
-5. Re-read and verify each field with `verifyDataExtensionSchemaFields()`, and persist the
-   evidence. A create or update can report success without producing the field.
-6. Generated import code writes an extended-field value only after verification passed for that
-   exact field — `validateExtendedFieldWriterReferences()` enforces it.
-
-Use `writers.provisionExtendedFieldRequirement()`; it routes each requirement by `schemaKind` and
-the `provision-extended-fields` step already calls it. Scope: orders, products
-and Contacts V5 through the Data Extension Schema; Contacts V4 through CRM Extended Fields only when
-the requirement says `contactWriteSurface: "contacts-v4"`. Everything else is refused before any
-network call. Types: `string` (DES) and `TEXT` (V4); the helpers refuse an unverified type.
-
-Named blockers and what they mean:
-
-- `CONTACTS_V5_DES_UNVERIFIED` — the gating List for `wix.contacts.*.contact` was refused. Setup
-  does **not** fall back to V4. Wait for the path to be verified, or re-route the mapping to
-  `contacts-v4` explicitly; that is a mapping decision, not a recovery step.
-- `EXTENDED_FIELD_SCHEMA_CONFLICT_EXHAUSTED` — three Update attempts in a row hit a revision
-  conflict. Each retry re-listed and re-merged, so the concurrent change was kept, not overwritten.
-  Re-run once the concurrent edits stop.
-- `schema-budget-exceeded` (under `EXTENDED_FIELD_SCHEMA_BLOCKED`) — the namespace byte budget cannot
-  hold the fields. Checked before create too, against the observed 10,000-byte limit. Route the
-  excess to CMS; never pick fields to drop.
-- `CONTACT_EXTENDED_FIELD_MISMATCH` — V4 Find Or Create matched a field by name with another type,
-  returned no or another namespace than `custom`, or returned a key different from the one an
-  earlier run verified. Keys cannot change and approving a migration action does not fix it;
-  decide with the owner rather than creating a second field.
-- `PRIOR_EXTENDED_FIELD_RECEIPT_UNREADABLE` — a contacts-v4 run found
-  `setup/extended-field-verification.json` but could not read it, so key continuity cannot be
-  proved. The file is kept; restore it, or remove it only if no earlier import wrote V4 values.
-
-Contacts V4 receipts record each `displayName`, the returned `key` and the write path
-`info.extendedFields.<key>`; V5 contact values go only under `extendedFields.namespaces._user_fields`.
-Live proof for products and both contact paths is still pending on a disposable site.
-
-The inventory verification token also needs Catalog read access to hidden products and variants. The canary must verify default-location availability in both Inventory and Catalog before the inventory path is marked verified.