Rp Quick Woocommerce

rp-quick-woocommerce

Use only when the router selected this resource for managementImportMode=quick and the source probe identified woocommerce with high confidence. This adapter imports only the entity graph declared in quick-mode.json; it never uses WordPress/WooCommerce credentials, browser extraction, page scraping (beyond the one <html lang> read described below), plugin endpoints, or an LLM mapping step.

Run the adapter from the repository root:

node skills/wix-replatform/resources/rp-quick-woocommerce/scripts/quick-mode.js preflight <projectDir>
node skills/wix-replatform/resources/rp-quick-woocommerce/scripts/quick-mode.js plan <projectDir>
node skills/wix-replatform/resources/rp-quick-woocommerce/scripts/quick-mode.js setup-author <projectDir>
node skills/wix-replatform/resources/rp-quick-woocommerce/scripts/quick-mode.js extract <projectDir>
node skills/wix-replatform/resources/rp-quick-woocommerce/scripts/quick-mode.js import <projectDir> [--dry-run]

plan also writes discovery/source-coverage.json: one adapter-excluded row per excluded[] entry, each dispositioned as the adapter's declared exclusion and carrying the committed excludedCapabilities translation from quick-mode.json (a target capability, or source-scope.<name> when Wix has none). The plan refuses if that translation is missing, extra, duplicated or outside both namespaces, and stamps sourceCoverageContract: 1 in quick-mode/plan.json. import refuses to write its completion summary when the plan is missing or unstamped, or its coverage file is missing or does not reconcile (a declared exclusion must name an excluded[] entry of the committed contract, with its committed capability); re-run plan to fix any of these. The summary carries sourceCoverage[] and sourceCoverageStatus.

plan also writes discovery/source-locale.json through the shared locale writer (adapter quick-woocommerce) from two bounded public reads: the first Store API product's prices.currency_code and the storefront home page's <html lang>. Time zone and country are not public, so they are unknown; a read that fails is an explicit unknown, never a plan failure. The field names come from the Store API schema and HTML, not from a live read of any store.

Setup does block until all four locale values are known. Ask the merchant for each value the public reads do not expose, then edit that field in discovery/source-locale.json to {"state":"supplied","value":"<validated value>","evidence":"merchant input","suppliedBy":"<operator>"}. Re-run plan and setup. The shared writer preserves a valid supplied value while the corresponding public capture remains unknown; never fill it from the destination site or guess.

The first two commands create the authoritative quick-mode/preflight.json, quick-mode/plan.json, and execution/execution-manifest.json. Setup discovery consumes the quick plan; normal setup execution and execution approval are still mandatory before the extract/import run. Do not replace the deterministic entity list with data discovered from pages. If an endpoint preflight fails, persist the reported blocker and create a durable choice between stopping and standard mode. The standard-mode choice must carry this effect so the CLI applies the user's selection before it resumes:

{"kind":"decision","key":"managementImportMode","choices":{"switch_to_standard":"standard"}}

The setup-author command is a setup step: it idempotently creates the dedicated fallback Blog member and records only its ID as WIX_BLOG_FALLBACK_MEMBER_ID. It uses the shared rp-target-wix writer runtime and sends no email. The import entrypoint requires normal setup verification and that setup-provisioned value before creating posts.

A dry run (--dry-run) writes only execution/dry-run-completion-report.json and execution/dry-run-final-report.md (plus the shared client's dry-run request capture). It never creates or changes a live artifact: the live completion and final reports, the crosswalk, the limit-recovery log, the import-started marker, or the post audit log logs/quick-mode-audit.ndjson. The router therefore still sends the project to the live import after a dry run.