@wix/agent-skills 1.36.0 → 1.36.1

package/skills/wix-replatform/resources/rp-source-wordpress/plugins/no-migration-needed.json

@@ -1,286 +0,0 @@
-{
-  "schemaVersion": 1,
-  "description": "Nothing-to-move verdicts, in two tiers.\n\n`hints[]` — a flat slug lookup for plugins that need no data migration at all, where a full profile would be dead weight. A hit here is strong evidence the agent confirms at classification, never the answer by itself. Without this list, a caching or SMTP plugin whose data we cannot read is reported as potential data loss — which is both wrong and alarming. Keyed by plugin directory slug; a slug with a full profile may not appear here.\n\n`capabilities[]` — the human-signed per-capability register, for PROFILED plugins the slug list cannot reach. This is the only way a profiled capability reaches the no-need-to-migrate status (basis: decision); without it a decided capability re-lands as pending on every run. It is not an impossibility verdict (that is requires-development.json) — it says the outcome exists in Wix or was never data — but it is still a decision about what the customer does not get, so it carries decidedBy + decidedOn and validation rejects an unsigned entry. Mutually exclusive with requires-development.json and capabilities-pending-decision.json, and rejected once a Wix target entity claims the capability.",
-  "reasons": {
-    "platform-does-it": "Wix provides this capability natively; drop the plugin and keep the behaviour.",
-    "not-needed": "Development, hosting or licensing tooling with no role after migration; it was never data.",
-    "reconfigure-in-wix": "A setting or rule you set up once in Wix rather than data to move."
-  },
-  "capabilities": [],
-  "hints": [
-    {
-      "slug": "nextend-facebook-connect",
-      "reason": "reconfigure-in-wix",
-      "does": "Social login buttons (Nextend Social Login): Facebook, Google, X/Twitter free; more providers in Pro",
-      "replacedBy": "Wix native member social login: enable the matching Google/Facebook toggles in dashboard Signup & Login settings (default form only). No settings API exists (members docs-survey 2026-08-16) — manual setup step. Fidelity: enable only the providers the source actually had enabled (detect from wp-login.php button render, not stylesheet class names). Providers beyond Google/Facebook are reportable loss; an org-restricted OAuth client is a different capability — see members.domain-restricted-login in capabilities-pending-decision.json.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "akismet",
-      "reason": "platform-does-it",
-      "does": "Comment and form spam protection",
-      "replacedBy": "Wix Forms and comments include spam protection.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "wp-rocket",
-      "reason": "platform-does-it",
-      "does": "Page caching and performance tuning",
-      "replacedBy": "Wix handles caching and delivery for you.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "redis-cache-pro",
-      "reason": "platform-does-it",
-      "does": "Redis object caching",
-      "replacedBy": "Managed by Wix infrastructure.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "cloudflare-helper",
-      "reason": "platform-does-it",
-      "does": "Purges the Cloudflare cache",
-      "replacedBy": "Wix serves through its own CDN.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "webp-express",
-      "reason": "platform-does-it",
-      "does": "Serves images in WebP format",
-      "replacedBy": "Wix converts and serves optimised images automatically.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "imagify",
-      "reason": "platform-does-it",
-      "does": "Compresses images",
-      "replacedBy": "Image optimisation is part of Wix media.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "ssl-insecure-content-fixer",
-      "reason": "platform-does-it",
-      "does": "Fixes mixed HTTP and HTTPS content",
-      "replacedBy": "Wix is HTTPS end to end, so the problem disappears.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "wp-mail-smtp",
-      "reason": "platform-does-it",
-      "does": "Sends site email through an SMTP provider",
-      "replacedBy": "Wix sends transactional email itself.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "post-smtp",
-      "reason": "platform-does-it",
-      "does": "Sends site email through an SMTP provider",
-      "replacedBy": "Wix sends transactional email itself.",
-      "provenance": "expected:not-yet-observed"
-    },
-    {
-      "slug": "invisible-recaptcha",
-      "reason": "platform-does-it",
-      "does": "Blocks form spam",
-      "replacedBy": "Wix Forms includes spam protection.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "equalweb",
-      "reason": "platform-does-it",
-      "does": "Accessibility overlay",
-      "replacedBy": "Wix has a built-in accessibility wizard — compare coverage before dropping it.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "chaty",
-      "reason": "platform-does-it",
-      "does": "Floating WhatsApp and social contact buttons",
-      "replacedBy": "Wix Chat plus social icons cover this.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "woocommerce-products-filter",
-      "reason": "platform-does-it",
-      "does": "Storefront product filtering",
-      "replacedBy": "Wix Stores has category, price and option filters.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "disclaimer-popup",
-      "reason": "platform-does-it",
-      "does": "Shows a site popup",
-      "replacedBy": "Wix lightboxes do this.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "jetpack",
-      "reason": "platform-does-it",
-      "does": "Stats, security and CDN bundle",
-      "replacedBy": "Its parts are all native to Wix.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "wp-super-cache",
-      "reason": "platform-does-it",
-      "does": "Page caching",
-      "replacedBy": "Wix handles caching for you.",
-      "provenance": "expected:not-yet-observed"
-    },
-    {
-      "slug": "w3-total-cache",
-      "reason": "platform-does-it",
-      "does": "Page and object caching",
-      "replacedBy": "Wix handles caching for you.",
-      "provenance": "expected:not-yet-observed"
-    },
-    {
-      "slug": "wordfence",
-      "reason": "platform-does-it",
-      "does": "Firewall and malware scanning",
-      "replacedBy": "Wix operates platform-level security.",
-      "provenance": "expected:not-yet-observed"
-    },
-    {
-      "slug": "really-simple-ssl",
-      "reason": "platform-does-it",
-      "does": "Forces HTTPS",
-      "replacedBy": "Wix is HTTPS end to end.",
-      "provenance": "expected:not-yet-observed"
-    },
-    {
-      "slug": "all-in-one-wp-migration",
-      "reason": "not-needed",
-      "does": "Backs up and exports the whole site",
-      "replacedBy": "Wix keeps site history itself. Useful during migration though: it can produce a full export including data the REST API does not expose.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "woocommerce-legacy-rest-api",
-      "reason": "not-needed",
-      "does": "Re-enables the older WooCommerce API versions",
-      "replacedBy": "This is why the old API versions appear on the site; we read the current one.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "woo-update-manager",
-      "reason": "not-needed",
-      "does": "Manages licences and plugin updates",
-      "replacedBy": "No role after the move.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "health-check",
-      "reason": "not-needed",
-      "does": "WordPress diagnostics",
-      "replacedBy": "No role after the move.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "wp-rollback",
-      "reason": "not-needed",
-      "does": "Rolls plugins back to an earlier version",
-      "replacedBy": "No role after the move.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "heartbeat-control",
-      "reason": "not-needed",
-      "does": "Throttles WordPress admin polling",
-      "replacedBy": "A WordPress-specific performance workaround.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "regenerate-thumbnails",
-      "reason": "not-needed",
-      "does": "Rebuilds image thumbnail sizes",
-      "replacedBy": "Wix generates its own image renditions.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "loco-translate",
-      "reason": "not-needed",
-      "does": "Translates plugin and theme interface strings",
-      "replacedBy": "Interface strings, not your content.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "user-role-editor",
-      "reason": "not-needed",
-      "does": "Edits WordPress user roles and permissions",
-      "replacedBy": "WordPress roles do not map to Wix permissions; set those up fresh.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "log-emails",
-      "reason": "not-needed",
-      "does": "Logs outgoing email",
-      "replacedBy": "An operational log rather than business data.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "so-css",
-      "reason": "not-needed",
-      "does": "Custom CSS editor",
-      "replacedBy": "Theme styling; the storefront is rebuilt in Wix regardless.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "easy-woocommerce-auto-sku-generator",
-      "reason": "not-needed",
-      "does": "Auto-fills product SKUs",
-      "replacedBy": "The SKUs it generated live on the products and migrate with them.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "sku-for-woocommerce",
-      "reason": "not-needed",
-      "does": "Generates product SKUs",
-      "replacedBy": "The SKUs it generated live on the products and migrate with them.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "woo-order-note-templates-old",
-      "reason": "not-needed",
-      "does": "Canned order note templates",
-      "replacedBy": "Staff convenience text, not customer data.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "woocommerce-email-test",
-      "reason": "not-needed",
-      "does": "Sends test emails",
-      "replacedBy": "A testing tool.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "wp-theme-plugin-download",
-      "reason": "not-needed",
-      "does": "Downloads theme and plugin files",
-      "replacedBy": "A developer utility.",
-      "provenance": "observed"
-    },
-    {
-      "slug": "query-monitor",
-      "reason": "not-needed",
-      "does": "Developer debugging panel",
-      "replacedBy": "A development tool.",
-      "provenance": "expected:not-yet-observed"
-    },
-    {
-      "slug": "duplicate-post",
-      "reason": "not-needed",
-      "does": "Duplicates posts and products",
-      "replacedBy": "An authoring convenience.",
-      "provenance": "expected:not-yet-observed"
-    },
-    {
-      "slug": "woo-cart-abandonment-recovery",
-      "reason": "platform-does-it",
-      "does": "Cart Abandonment Recovery for WooCommerce: records abandoned checkouts in its own table (cartflows_ca_cart_abandonment) and sends recovery email sequences",
-      "replacedBy": "Wix eCommerce captures abandoned checkouts natively from launch onward, and Wix Automations sends the recovery mail — so the capability is not lost going forward. What cannot move is the HISTORY: there is no way to write a historical AbandonedCheckout (see requires-development commerce.abandoned-carts). Do not attempt to backfill it by recreating carts; that produces no historical abandoned checkouts. If the owner wants the abandoned-cart PEOPLE as contacts, that is a separate, explicitly-approved crm/contact import, email only and never a marketing subscription.",
-      "provenance": "observed"
-    }
-  ],
-  "policy": "Grow from real runs: add a hint when a real migration surfaces the plugin as unresolved. `provenance` records whether we have actually seen the plugin or added it by expectation, so the unobserved entries stay visible and reviewable rather than accumulating silently."
-}

package/skills/wix-replatform/resources/rp-source-wordpress/plugins/pricing-deals-for-woocommerce.json

@@ -1,79 +0,0 @@
-{
-  "schemaVersion": 1,
-  "plugin": "pricing-deals-for-woocommerce",
-  "displayName": "VarkTech Pricing Deals for WooCommerce",
-  "profileVersion": "2026-08",
-  "sourceOfTruth": "https://wordpress.org/plugins/pricing-deals-for-woocommerce/",
-  "distribution": "wordpress-org",
-  "capabilities": [
-    "commerce.discount-rules",
-    "commerce.applied-discounts"
-  ],
-  "detect": {
-    "pluginFileIds": [
-      "pricing-deals-for-woocommerce/vt-pricing-deals.php"
-    ],
-    "assetPathSlugs": [
-      "pricing-deals-for-woocommerce"
-    ]
-  },
-  "entities": [
-    {
-      "entity": "discount-rule-definition",
-      "channel": "admin-page-only",
-      "candidateTargetRefs": ["ecom/discount-rule"],
-      "pitfalls": [
-        {
-          "code": "cpt-backed-not-settings-page-but-same-access-limit",
-          "severity": "warning",
-          "summary": "Unlike woo-discount-rules' settings page, rule definitions here are a custom post type (`vtprd-rule`, taxonomy `vtprd_rule_category`) — VERIFIED IN SOURCE 2026-08 (`core/vtprd-backbone.php`, github.com/common-repository/pricing-deals-for-woocommerce). The CPT is not registered `show_in_rest`, so it never appears on `/wp/v2/`, and — same WordPress-core boundary already established for woo-discount-rules (plugins/README.md's admin-page-only note) — the CPT list/edit screens render only inside an authenticated wp-admin session that Application Passwords do not authenticate. classified admin-page-only for that reason even though the underlying storage is a CPT, not a settings page."
-        },
-        {
-          "code": "no-export-tool-unlike-woo-discount-rules",
-          "severity": "warning",
-          "summary": "VERIFIED IN SOURCE 2026-08: grepped the full plugin tree for csv/export/import controllers — none exist. woo-discount-rules' built-in Import/Export CSV tab (the escape hatch that unblocked that plugin's rule-definition capability) has no equivalent here; the only path to a rule's trigger/effect shape is a human transcribing/screenshotting the `vtprd-rule` list in wp-admin."
-        },
-        {
-          "code": "admin-page-not-reachable-with-application-password",
-          "severity": "blocker",
-          "summary": "Same WordPress-core boundary verified live against woo-discount-rules' settings page (plugins/README.md): Application Passwords authenticate REST requests only, never wp-admin page renders. No `register_rest_route` call exists anywhere in this plugin's source (VERIFIED IN SOURCE 2026-08, full-tree grep) — there is no automated read path at all, not even a degraded one.",
-          "blocked": [
-            {
-              "kind": "user-file",
-              "resolution": "Ask the site owner (real wp-admin login session) to open WooCommerce > Pricing Deals (or Tools > Pricing Deals if `register_under_tools_menu` is enabled) and transcribe or screenshot each rule's deal type (Dynamic/Cart pricing, Catalog/wholesale pricing, BOGO, tiered quantity, category/role-based) and its trigger/effect values. Do not ask for the owner's actual WordPress account password.",
-              "declined": false
-            }
-          ]
-        }
-      ]
-    },
-    {
-      "entity": "applied-discount",
-      "channel": "db-only",
-      "candidateTargetRefs": ["ecom/order-applied-discount"],
-      "pitfalls": [
-        {
-          "code": "full-ledger-is-private-tables-not-order-meta",
-          "severity": "blocker",
-          "summary": "VERIFIED IN SOURCE 2026-08 (`woo-integration/vtprd-parent-cart-validation.php` + `vtprd-parent-definitions.php`): on `woocommerce_checkout_order_processed`, `vtprd_save_discount_purchase_log()` writes the entire applied-discount ledger into three custom tables (`{prefix}vtprd_purchase_log`, `..._purchase_log_product`, `..._purchase_log_product_rule`), keyed by order id, holding the serialized ruleset/cart object plus per-product/per-rule discount amounts. Unlike woo-discount-rules (whose per-order-meta `_wdr_discounts` summary is real even though a fuller ledger also lives in a private table), THIS plugin puts the entire ledger in the private tables with no order-meta or order-item-meta trace at all — grepped the full tree for `update_post_meta`/`add_meta_data`/`update_meta_data` near order objects, zero hits."
-        },
-        {
-          "code": "default-mode-bakes-discount-into-unit-price-no-marker",
-          "severity": "blocker",
-          "summary": "The plugin's default discount-application mode (`discount_taken_where` option, default `discountUnitPrice` per `admin/vtprd-setup-options.php`) overwrites the cart line item's unit price directly — a discounted line looks IDENTICAL to a merchant-set lower price, with no meta key, no note, nothing distinguishing it. In this (most common) mode there is no signal anywhere in `/wc/v3/orders` that a discount was ever applied to a given line, so even the historical fact of a discount is unrecoverable from REST — only the private tables above have it."
-        },
-        {
-          "code": "coupon-mode-surfaces-a-lump-sum-only",
-          "severity": "warning",
-          "summary": "An alternate setting (`discount_taken_where = discountCoupon`) applies a synthetic WooCommerce coupon via `WC_Cart::add_discount()` (`vtprd_woo_maybe_add_remove_discount_cart_coupon()`, hooked on `woocommerce_after_calculate_totals`) — VERIFIED IN SOURCE 2026-08, not live-confirmed against a real order. In this mode the discount would surface as a normal `coupon_lines[]` entry on `/wc/v3/orders` (title from option `coupon_discount_coupon_name`), reachable through the existing generic WooCommerce-coupon path (ecom/order-applied-discount's `coupon` one-of variant, via stores/coupon) — but it carries only the lump total, never the per-rule breakdown the private tables hold, and this mode is not the plugin default."
-        }
-      ]
-    }
-  ],
-  "quirks": [
-    "Rule model overlaps woo-discount-rules (both are general-purpose conditional-pricing engines: percentage/fixed/BOGO/tiered-quantity/category-or-role-based), so a site running both is worth flagging for consolidation at the mapping review rather than migrating two parallel discount-definition transcriptions.",
-    "Main plugin file VERIFIED IN SOURCE 2026-08 via the github.com/common-repository/pricing-deals-for-woocommerce mirror (readme.txt Stable tag 2.0.3.2, `vt-pricing-deals.php` header Version: 2.0.3.2) — this mirror is used the same way the WordPressPluginDirectory mirror was used to verify woo-discount-rules; `WordPressPluginDirectory/pricing-deals-for-woocommerce` itself returns 404, `common-repository` is the equivalent-purpose org for this plugin.",
-    "Options `vtprd_setup_options` (settings incl. `discount_taken_where`) and `vtprd_rules` are additional low-value detection candidates if a future run needs a second signal — not declared in `detect` here because neither was checked for `show_in_rest`/autoload exposure live.",
-    "This profile's detect signals and entity behavior are source-code-verified (see the pitfalls' citations) but have not been live-verified against a running installation."
-  ]
-}

package/skills/wix-replatform/resources/rp-source-wordpress/plugins/product-extras-for-woocommerce.json

@@ -1,120 +0,0 @@
-{
-  "schemaVersion": 1,
-  "plugin": "product-extras-for-woocommerce",
-  "displayName": "WooCommerce Product Add-Ons Ultimate",
-  "profileVersion": "2026-09",
-  "sourceOfTruth": "https://www.pluginrepublic.com/wordpress-plugins/woocommerce-product-add-ons-ultimate/",
-  "distribution": "premium-or-unlisted",
-  "capabilities": [
-    "commerce.product-addon-fields",
-    "commerce.order-addon-values"
-  ],
-  "detect": {
-    "pluginFileIds": [
-      "product-extras-for-woocommerce/product-extras-for-woocommerce"
-    ],
-    "recordProperties": [
-      "pewc_display_groups",
-      "pewc_global_groups_by_product",
-      "pewc_price_display",
-      "product_extras",
-      "_pewc_product_extra_id"
-    ],
-    "assetPathSlugs": [
-      "product-extras-for-woocommerce"
-    ]
-  },
-  "entities": [
-    {
-      "entity": "addon-field-group",
-      "capability": "commerce.product-addon-fields",
-      "channel": "db-only",
-      "candidateTargetRefs": [
-        "stores/product-customization"
-      ],
-      "pitfalls": [
-        {
-          "code": "definitions-are-cpt-rows-with-empty-post-content",
-          "severity": "warning",
-          "summary": "Groups and fields are custom post types (`pewc_group`, `pewc_field`, `pewc_product_extra`) with `post_content` of length 0 on every row -- reading the posts table proves the definitions exist and names them, and tells you nothing about what they contain. The configuration is entirely `postmeta`, which is reachable key-scoped (see blocked[]). VERIFIED LIVE 2026-09-08: every definition post carried empty post_content, and the configuration was recoverable only from postmeta. Expect tens of meta keys per group/field set; read the live count rather than assuming one."
-        },
-        {
-          "code": "one-global-group-scoped-by-category-not-per-product",
-          "severity": "warning",
-          "summary": "A group's reach is a rule, not a product list. VERIFIED LIVE 2026-09-08: a single `pewc_group` can carry `global_rules` matching several product categories, so a large number of products showed a pewc meta key while only ONE group definition existed. Do not infer one add-on group per product from the product-side meta count, and do not migrate N customizations where the source has one -- see stores/product-customization's inline-modifiers-mint-a-new-customization pitfall."
-        },
-        {
-          "code": "numeric-priced-field-has-no-wix-render-type",
-          "severity": "blocker",
-          "summary": "An add-on where the customer types a quantity and pays a per-unit price becomes a fixed list of choices on Wix instead of an open number box, so quantities nobody has ordered before are no longer offerable. Wix `customizationRenderType` is FREE_TEXT | TEXT_CHOICES | SWATCH_CHOICES only: there is no numeric input, and FREE_TEXT's `defaultAddedPrice` is a flat add rather than a multiplier, so a `field_type: number` field with `field_price` and `multiply: 1` has no faithful target. Map it as a bounded TEXT_CHOICES enumeration over the quantities real orders show and ledger the open-ended range as a loss."
-        },
-        {
-          "code": "field-conditions-have-no-counterpart",
-          "severity": "warning",
-          "summary": "Fields carry `condition_action`, `condition_match`, `field_visibility` and formula keys (`formula_action`, `formula_round`). Wix customizations have no conditional-visibility mechanism at all (stores/product-customization pitfall conditional-visibility-no-counterpart), so any conditional field needs a per-field decision at mapping review rather than a silent flatten."
-        }
-      ],
-      "blocked": [
-        {
-          "kind": "structure-bridge-plugin",
-          "resolution": "The definition config is `postmeta`, which wix-wp-plugin-v2 reads KEY-SCOPED -- it is not refused. VERIFIED LIVE 2026-09-08: `GET /structure?table=postmeta` returns 200 with `eavPair {meta_key, meta_value}`, and the two-step read works exactly as plugins/README.md row 2 describes. Step 1, key discovery (never names meta_value, so no pinning needed): select meta_key + count(meta_id), where post_id in <the pewc CPT post ids>, groupBy [meta_key] -> the live key list. Step 2, key-scoped read: select post_id/meta_key/meta_value, where meta_key in <=45 of those keys AND post_id in <ids>, orderBy meta_id asc -> the rows carrying the whole definition. Pin at most 50 keys per request (MAX_PINNED_KEYS) and batch beyond that; naming meta_value without pinning meta_key returns the ordinary 400 wmh2_invalid_structure_request. The keys that matter: field_label, field_type, field_price, multiply, field_minval, field_default, decimal_places, field_description, field_options, field_ids, global_rules, group_layout, condition_action, condition_match, field_visibility, price_visibility. No executable `fulfillment` is declared yet: that requires a matching blockedSourceDependencies entry on stores/product-customization, which is a target-side change worth reviewing on its own.",
-          "declined": false
-        }
-      ]
-    },
-    {
-      "entity": "product-addon-assignment",
-      "capability": "commerce.product-addon-fields",
-      "channel": "core-meta",
-      "embeddedIn": [
-        "/wc/v3/products"
-      ],
-      "propertyPath": "pewc_display_groups",
-      "candidateTargetRefs": [
-        "stores/product-customization"
-      ],
-      "pitfalls": [
-        {
-          "code": "product-side-meta-is-settings-not-assignment",
-          "severity": "warning",
-          "summary": "The six product-side keys (`pewc_display_groups`, `pewc_global_groups_by_product`, `pewc_force_minimum`, `pewc_price_label`, `pewc_price_display`, `pewc_minimum_price`) are per-product SETTINGS, and they commonly all carry identical default values -- `pewc_display_groups: \"standard\"` means 'show whatever the global groups match', not 'this product has its own group'. VERIFIED LIVE 2026-09-08 in both `view` and `edit` context, where the products carrying them held identical defaults. Which products actually receive a group comes from the group's own `global_rules`, not from here."
-        },
-        {
-          "code": "per-product-route-returns-no-definition",
-          "severity": "info",
-          "summary": "The plugin registers real REST routes under the `wc` namespace -- `/wc/pewc/{product_id}`, `/wc/pewc/{product_id}/{group_id}`, `/wc/pewc/{product_id}/{group_id}/{field_id}` -- which is why searching the REST index for a `pewc` NAMESPACE finds nothing and a guess at `/pewc/v1` 404s. They are not a definition read: VERIFIED LIVE 2026-09-08, the base route answered `{product_id, group_order: \"\"}` for every pewc product, and a global group id is rejected as `pewc_rest_group_invalid_id`. Do not spend probes here."
-        }
-      ]
-    },
-    {
-      "entity": "order-line-item-addon-values",
-      "capability": "commerce.order-addon-values",
-      "channel": "core-meta",
-      "embeddedIn": [
-        "/wc/v3/orders"
-      ],
-      "propertyPath": "product_extras",
-      "candidateTargetRefs": [
-        "ecom/order-line-item-options"
-      ],
-      "pitfalls": [
-        {
-          "code": "chosen-values-ride-as-label-keyed-line-item-meta",
-          "severity": "warning",
-          "summary": "What the customer actually chose is NOT inside `product_extras` -- that object is `{product_id, title, groups, price_with_extras, original_price, aelia_currency}` and its `groups` array was observed empty on line items. The selections arrive as SEPARATE line-item meta entries whose KEY is the field label (often `_`-prefixed) and whose value is the quantity and money, e.g. a key named for the field's own label, valued `1 &#8362;10` for one unit at 10. Read the label-keyed entries; `_pewc_product_extra_id` names the definition post. Money arrives HTML-entity encoded (`&#8362;` for the shekel sign) and needs decoding."
-        },
-        {
-          "code": "price-delta-is-derivable-per-line",
-          "severity": "info",
-          "summary": "`product_extras.price_with_extras` minus `original_price` gives the add-on charge for that line without parsing labels -- useful for reconciling an imported order's totals against the source. Equal values mean no add-on was used, which is typically the large majority of line items."
-        }
-      ]
-    }
-  ],
-  "quirks": [
-    "The plugin slug and its textdomain disagree: the folder is `product-extras-for-woocommerce` while every meta key, CPT and label uses the `pewc` prefix. Detect on the plugin file id, match data on `pewc`.",
-    "Its REST routes live under the shared `wc` namespace (`/wc/pewc/...`), not a namespace of its own, so a namespace-level search for the plugin finds nothing even though the surface exists. VERIFIED LIVE 2026-09-08.",
-    "Field option lists arrive URL-encoded in order meta and decode to a comma-separated option list; non-ASCII labels are percent-encoded. Decode before comparing to the definition's own `field_options`.",
-    "`field_type: number` with `multiply: 1` is a per-unit charge, and `decimal_places` may allow fractional quantities (a live order charged a fractional quantity). Do not assume integer quantities when enumerating choices for the Wix mapping."
-  ]
-}

package/skills/wix-replatform/resources/rp-source-wordpress/plugins/pw-woocommerce-gift-cards.json

@@ -1,128 +0,0 @@
-{
-  "schemaVersion": 1,
-  "plugin": "pw-woocommerce-gift-cards",
-  "displayName": "PW WooCommerce Gift Cards",
-  "profileVersion": "2026-08",
-  "sourceOfTruth": "https://wordpress.org/plugins/pw-woocommerce-gift-cards/",
-  "distribution": "wordpress-org",
-  "capabilities": [
-    "commerce.gift-card-products",
-    "commerce.gift-cards"
-  ],
-  "detect": {
-    "pluginFileIds": [
-      "pw-woocommerce-gift-cards/pw-gift-cards"
-    ],
-    "recordProperties": [
-      "pw_gift_card_number",
-      "pw_gift_card_amount",
-      "pw_gift_card_to",
-      "pw_gift_card_from",
-      "pw_gift_card_message"
-    ],
-    "assetPathSlugs": [
-      "pw-woocommerce-gift-cards"
-    ]
-  },
-  "entities": [
-    {
-      "entity": "gift-card-product",
-      "channel": "plugin-rest-child",
-      "route": "/wc/v3/products/{parentId}/variations",
-      "parentRoute": "/wc/v3/products",
-      "recordKeyField": "id",
-      "candidateTargetRefs": [
-        "gift-cards/gift-card-product"
-      ],
-      "pitfalls": [
-        {
-          "code": "type-discriminated-subset",
-          "severity": "blocker",
-          "summary": "Gift-card products are ordinary WooCommerce products discriminated ONLY by type == \"pw-gift-card\" — no PW-specific meta key or property exists on the record [VERIFIED LIVE 2026-08-16: meta_data carried only _created_via and third-party keys]. The core products import must NOT map these as plain store products; enumerate them authoritatively with GET /wc/v3/products?type=pw-gift-card (the type enum on wc/v3/products includes pw-gift-card [VERIFIED LIVE 2026-08-16]) and route them to gift-cards/gift-card-product instead."
-        },
-        {
-          "code": "denominations-are-variations",
-          "severity": "warning",
-          "summary": "Denominations live as product variations under a \"Gift Card Amount\" attribute — one variation per amount, each with its own price [VERIFIED LIVE 2026-08-16]. Map the variation prices to the Wix gift-card product's denomination options; a variant-filtering transform that drops unknown attribute terms would silently lose denominations."
-        }
-      ]
-    },
-    {
-      "entity": "gift-card",
-      "channel": "core-meta",
-      "embeddedIn": ["/wc/v3/orders"],
-      "propertyPath": "pw_gift_card_number",
-      "candidateTargetRefs": [
-        "gift-cards/gift-card"
-      ],
-      "pitfalls": [
-        {
-          "code": "issuance-is-core-meta-not-db-only",
-          "severity": "warning",
-          "summary": "CORRECTED 2026-08-17 (VERIFIED LIVE, resolving the 2026-08-16 quirk below): issued-card identity (code, amount, recipient email, sender name, message) is NOT db-only — it rides as line_item.meta_data (pw_gift_card_number/pw_gift_card_amount/pw_gift_card_to/pw_gift_card_from/pw_gift_card_message) on GET /wc/v3/orders once the order reaches processing or completed. The plugin's own PHP source (pw-gift-cards-purchasing.php, github.com/common-repository/pw-woocommerce-gift-cards mirror) calls PW_Gift_Card::create_card() from the woocommerce_order_status_processing/woocommerce_payment_complete (both gated on is_paid()) and woocommerce_order_status_completed hooks — a pending/on-hold order simply has no card yet, which is not the same as 'unreachable'. Only the ongoing BALANCE (post-issuance activity/redemption) remains genuinely db-only — see gift-card-activity's no-wix-write-surface-for-history pitfall, now also live-confirmed."
-        },
-        {
-          "code": "outstanding-balance-is-a-liability",
-          "severity": "blocker",
-          "summary": "Unspent balances are money owed to customers. Reconcile the total outstanding value before and after import and show it in the execution plan; a silently dropped card is a lost customer entitlement."
-        },
-        {
-          "code": "code-alphanumeric-only-not-just-length",
-          "severity": "blocker",
-          "summary": "CORRECTED 2026-08-17 (VERIFIED LIVE against the real Wix Create Gift Card endpoint): the 2026-08-16 note below that PW's dash-separated format 'fits' Wix's 8-20 character bound is INCOMPLETE and misleading. Wix's giftCard.code rejects ANY non-alphanumeric character outright (live 428 INVALID_CODE: 'Gift Card Code can only contain letters(A-z) and numbers(0-9)') — independent of length. PW's own default code format (four groups of four separated by hyphens, e.g. XXXX-XXXX-XXXX-XXXX) is REJECTED AS-IS by Wix, every single time, not just as an edge case. Stripping the hyphens produces a 16-character alphanumeric string Wix accepts (confirmed live: create + read-back succeeded), but that changes the code the customer already holds printed/emailed — the same 'do not silently rewrite' principle as the length pitfall, except this one is the DEFAULT case for this plugin, not an outlier."
-        },
-        {
-          "code": "balance-derived-from-activity",
-          "severity": "warning",
-          "summary": "PW derives a card's balance from its activity ledger (sum of credit/debit rows), and Wix likewise only accepts an initial value with balance derived from transactions. A partly-redeemed card needs an explicit policy: import at remaining balance, or at face value with the spend replayed. Decide it in the mapping plan; do not default silently. [DOCUMENTED]"
-        }
-      ]
-    },
-    {
-      "entity": "gift-card-activity",
-      "channel": "db-only",
-      "candidateTargetRefs": [],
-      "blocked": [
-        {
-          "kind": "structure-bridge-plugin",
-          "resolution": "wix-wp-plugin-v2's query-structure route reads pimwick_gift_card_activity directly. VERIFIED LIVE 2026-08-28: discover-structure returned this table's real schema (pimwick_gift_card_id, user_id, activity_date, action, amount, note, reference_activity_id). IMPORTANT -- this does NOT by itself resolve the masking/correlation contract: the consuming code (rp-import-codegen) MUST issue an AGGREGATE structureRequest (select pimwick_gift_card_id, SUM(amount) AS balance, groupBy pimwick_gift_card_id) rather than a raw row dump, so individual activity rows, user_id, and free-text note are never pulled at all -- only a per-card running balance. Correlating that balance back to an actual card's redeemable number/code is a SEPARATE step: the code is already captured via the gift-card entity's own order-embedded issuance data (see gift-card's issuance-is-core-meta-not-db-only pitfall), not from this table. The exact masking/correlation contract must still be decided before any of this is wired into a real import -- this fulfillment only establishes that the underlying data is technically reachable and how to reach it without over-fetching, not that the contract question is settled.",
-          "declined": false,
-          "fulfillment": {
-            "kind": "structure-bridge-plugin",
-            "handlerId": "wix-wp-plugin-v2",
-            "table": "pimwick_gift_card_activity",
-            "sampleStructureRequest": {
-              "select": [
-                { "column": "pimwick_gift_card_id" },
-                { "column": "amount", "aggregate": "sum", "as": "balance" }
-              ],
-              "groupBy": ["pimwick_gift_card_id"],
-              "orderBy": [{ "column": "pimwick_gift_card_id", "direction": "asc" }]
-            }
-          }
-        }
-      ],
-      "pitfalls": [
-        {
-          "code": "no-wix-write-surface-for-history",
-          "severity": "warning",
-          "summary": "Per-card activity history (issuance, redemptions, adjustments) is durable data in the same plugin-owned tables as the cards [DOCUMENTED], but Wix has no public method to write historical gift-card transactions (see gift-cards/gift-card pitfall no-transaction-history-import); the domain entity's documented fallback is a CMS archive. Unlike issued-card identity (see gift-card's issuance-is-core-meta-not-db-only pitfall — that data turned out to be reachable via order line-item meta), this activity ledger itself has no REST path at all; see this same entity's redemption-invisible-even-in-order-rest-data pitfall, and this entity's own blocked[].fulfillment (wix-wp-plugin-v2) for the actual unblock -- an aggregate query, not the raw ledger."
-        },
-        {
-          "code": "redemption-invisible-even-in-order-rest-data",
-          "severity": "blocker",
-          "summary": "VERIFIED LIVE 2026-08-17: this is a stronger claim than 'db-only plugin tables' — applying a gift card at checkout adds a custom WooCommerce order-item type ('pw_gift_card', class WC_Order_Item_PW_Gift_Card via $order->add_item()) that the stock /wc/v3/orders REST controller never serializes at all (it only knows line_items/fee_lines/shipping_lines/coupon_lines/tax_lines). A live redemption was generated end-to-end (headless storefront checkout via the WooCommerce Store API) and the resulting order's full REST payload has ZERO trace of it: order.total drops by the redeemed amount, but discount_total/fee_lines/coupon_lines are all unchanged, so nothing in the standard response explains why. There is no order-meta fallback here the way there is for gift-card-issuance — this genuinely has no REST path at all, only a DB export."
-        }
-      ]
-    }
-  ],
-  "quirks": [
-    "Storage model [VERIFIED LIVE 2026-08-16, v2.47]: gift-card PRODUCTS (catalog) are REST-visible as wc/v3 products of type pw-gift-card with denomination variations. UPDATED 2026-08-17 (VERIFIED LIVE): issued-card IDENTITY (code/amount/recipient) is reachable too, once positively observed on a completed order — see gift-card's issuance-is-core-meta-not-db-only pitfall. Only the ongoing balance/redemption ledger is genuinely db-only with no REST route at all.",
-    "The route /wc-pimwick/v1/pw-gift-cards previously recorded on the Wix-side sourceAliases (gift-cards/gift-card) does NOT exist: 404 rest_no_route, and no wc-pimwick namespace in the REST index [VERIFIED LIVE 2026-08-16 against free v2.47, re-confirmed 2026-08-17]. Whether the separate PW Gift Cards Pro plugin registers such a surface is [NEEDS-VERIFICATION].",
-    "Plugin id basename differs from the directory: pw-woocommerce-gift-cards/pw-gift-cards, no .php suffix on this host's plugin list [VERIFIED LIVE 2026-08-16]. Never construct dir/dir.php.",
-    "Unauthenticated fingerprint: the storefront homepage loads /wp-content/plugins/pw-woocommerce-gift-cards/assets/dist/blocks.js?ver=2.47, so the asset-path signal works with no credentials [VERIFIED LIVE 2026-08-16].",
-    "Enumerating gift-card products via the {parentId}/variations child route depends on the sampled parent page containing the pw-gift-card product; the authoritative enumeration is GET /wc/v3/products?type=pw-gift-card (returned the product with X-WP-Total [VERIFIED LIVE 2026-08-16]).",
-    "RESOLVED 2026-08-17 (was NEEDS-VERIFICATION as of 2026-08-16, below): a gift-card PURCHASE order DOES carry PW recipient/message line-item meta once it actually completes. VERIFIED LIVE by generating orders via the WooCommerce REST API directly (POST /wc/v3/orders with the same pw_gift_card_amount/to/from/message meta the plugin's own checkout hook sets, then PUT status:completed — a status transition fires the same woocommerce_order_status_completed hook regardless of whether the order originated from checkout or the REST API) and confirming pw_gift_card_number appeared on completion. Prior note, for context: an earlier scan of existing orders found no PW keys, but that store had never sold a gift card, so there was no positive case to observe.",
-    "Discovered 2026-08-17: the plugin's checkout redeem widget ('Have a gift card?') is wired only to classic Cart/Checkout template hooks (woocommerce_before_checkout_form, woocommerce_review_order_before_order_total, woocommerce_cart_totals_before_order_total). A site using WooCommerce's Cart/Checkout BLOCKS never renders it at all — confirmed by finding no classic form markup and no localized pwgc nonce anywhere on the block-rendered /cart/ or /checkout/ pages. The plugin's own AJAX action (admin-ajax.php?action=pw-gift-cards-redeem) and Store API cart 'extensions.pw-gift-cards' data still work if invoked directly (verified by doing exactly that, via a temporary [woocommerce_cart]-shortcode page created solely to obtain a real nonce, then deleted) — but a real end customer on an unmodified block-checkout site currently has no way to redeem a card through the storefront UI at all."
-  ]
-}