@wix/agent-skills 1.35.1 → 1.36.1

package/skills/wix-replatform/resources/rp-source-wordpress/plugins/ti-woocommerce-wishlist.json

@@ -1,81 +0,0 @@
-{
-  "schemaVersion": 1,
-  "plugin": "ti-woocommerce-wishlist",
-  "displayName": "TI WooCommerce Wishlist",
-  "profileVersion": "2026-08",
-  "sourceOfTruth": "https://wordpress.org/plugins/ti-woocommerce-wishlist/",
-  "distribution": "wordpress-org",
-  "capabilities": [
-    "commerce.wishlists"
-  ],
-  "detect": {
-    "pluginFileIds": [
-      "ti-woocommerce-wishlist/ti-woocommerce-wishlist.php"
-    ],
-    "assetPathSlugs": [
-      "ti-woocommerce-wishlist"
-    ]
-  },
-  "entities": [
-    {
-      "entity": "wishlist-definition",
-      "capability": "commerce.wishlists",
-      "channel": "db-only",
-      "candidateTargetRefs": [],
-      "pitfalls": [
-        {
-          "code": "no-rest-collection-route",
-          "severity": "info",
-          "summary": "The plugin's own REST API (wc/v3/wishlist/*) only offers a per-user get_by_user/{user_id} route, no bulk collection endpoint. structure-bridge-plugin reads the dedicated tinvwl_lists table directly instead. VERIFIED LIVE 2026-08-29: discover-structure returned tinvwl_lists's real 7-column schema and query-structure returned real rows."
-        },
-        {
-          "code": "no-native-wix-target-verified",
-          "severity": "warning",
-          "summary": "Wix has a real native Wishlist API (com.wixpress.wishlist.Wishlist, fqdn wix.platform.v1.wishlist -- confirmed 2026-08-29 from its internal proto, NOT wix.ecom.v1.wishlist as an earlier orphaned attempt assumed), but its write RPCs are member-session-scoped only with no backend bulk-write path -- unusable for a migration import. See rp-target-wix/domains/ecom/entities/wishlist-item.json for the full writeup. DECIDED 2026-08-29: land in a Wix CMS collection instead for now (see this entity's blocked[].fulfillment below); revisit the native target if a backend write path is ever added."
-        }
-      ],
-      "blocked": [
-        {
-          "kind": "structure-bridge-plugin",
-          "resolution": "wix-wp-plugin-v2's discover-structure/query-structure routes read the tinvwl_lists table directly -- VERIFIED LIVE 2026-08-29: discover-structure returned tinvwl_lists's real 7-column schema and query-structure returned real rows. Native Wix Wishlist write has no backend path (see no-native-wix-target-verified pitfall) -- lands in a Wix CMS collection instead, decided 2026-08-29.",
-          "declined": false,
-          "fulfillment": {
-            "kind": "structure-bridge-plugin",
-            "handlerId": "wix-wp-plugin-v2",
-            "table": "tinvwl_lists"
-          }
-        }
-      ]
-    },
-    {
-      "entity": "wishlist-item",
-      "capability": "commerce.wishlists",
-      "channel": "db-only",
-      "candidateTargetRefs": [],
-      "pitfalls": [
-        {
-          "code": "references-product-by-source-id",
-          "severity": "warning",
-          "summary": "product_id/variation_id reference WooCommerce products by source id -- must be crosswalked to Wix catalog ids, not carried as-is."
-        }
-      ],
-      "blocked": [
-        {
-          "kind": "structure-bridge-plugin",
-          "resolution": "VERIFIED LIVE 2026-08-29: discover-structure returned tinvwl_items's real 10-column schema and query-structure returned real rows. Native Wix Wishlist write has no backend path (see wishlist-definition's no-native-wix-target-verified pitfall) -- lands in a Wix CMS collection instead, decided 2026-08-29.",
-          "declined": false,
-          "fulfillment": {
-            "kind": "structure-bridge-plugin",
-            "handlerId": "wix-wp-plugin-v2",
-            "table": "tinvwl_items"
-          }
-        }
-      ]
-    }
-  ],
-  "quirks": [
-    "wishlist_id in tinvwl_items joins to tinvwl_lists.ID; author=0 rows are guest wishlists (no user reference).",
-    "Live-verified 2026-08-29: wishlists (tinvwl_lists) and wishlist items (tinvwl_items) are readable through the structure routes.",
-    "Target decided 2026-08-29: Wix CMS collection, not the native Wishlist API -- see rp-target-wix/domains/ecom/entities/wishlist-item.json for the full gap writeup (real native API exists, but has no backend/service-account write path usable for a migration import)."
-  ]
-}

package/skills/wix-replatform/resources/rp-source-wordpress/plugins/woo-checkout-field-editor-pro.json

@@ -1,60 +0,0 @@
-{
-  "schemaVersion": 1,
-  "plugin": "woo-checkout-field-editor-pro",
-  "displayName": "Checkout Field Editor for WooCommerce",
-  "profileVersion": "2026-08",
-  "sourceOfTruth": "https://www.themehigh.com/product/woocommerce-checkout-field-editor-pro/",
-  "distribution": "premium-or-unlisted",
-  "capabilities": [
-    "commerce.checkout-custom-fields"
-  ],
-  "detect": {
-    "pluginFileIds": [
-      "woo-checkout-field-editor-pro/checkout-form-designer"
-    ]
-  },
-  "entities": [
-    {
-      "entity": "checkout-field-definition",
-      "channel": "admin-page-only",
-      "candidateTargetRefs": [
-        "ecom/order"
-      ],
-      "blocked": [
-        {
-          "kind": "user-file",
-          "resolution": "Ask the site owner to open WooCommerce > Checkout Fields (their own login session) and transcribe each configured field into the canonical CSV (meta_key,label,type,section,required,options,enabled,sort_order). The plugin's own Export/Import feature (Actions dropdown per section) may produce a usable file directly once its format is verified live -- not yet done.",
-          "declined": false,
-          "fulfillment": {
-            "kind": "csv-upload",
-            "handlerId": "checkout-field-csv",
-            "expectedInputPath": "data/user-supplied/woo-checkout-field-editor-pro.csv",
-            "freshnessWindowHours": 720
-          }
-        }
-      ],
-      "pitfalls": [
-        {
-          "code": "no-rest-route",
-          "severity": "blocker",
-          "summary": "[VERIFIED LIVE 2026-08-19] Queried the full REST index directly (every registered namespace and route) and found none belonging to this plugin (checked for `checkout`, `cfe`, `field-editor`, `wcfe`, and the plugin's own basename). The `checkout`-named routes present belonged to other plugins/WooCommerce's own ephemeral session-checkout routes, not this plugin."
-        },
-        {
-          "code": "vendor-export-shape-unverified",
-          "severity": "info",
-          "summary": "[NEEDS-VERIFICATION] The plugin ships its own Export/Import feature (Actions dropdown per checkout section -> Export -> file saved to the Media Library, per themehigh.com/docs/how-to-import-export-checkout-fields/), but its file format (JSON vs CSV, exact schema) has not been triggered or inspected live. This profile's `blocked[].fulfillment` depends only on the `checkout-field-csv` handler's canonical, plugin-agnostic CSV contract (lib/checkout-field-csv-parser.js), not on that vendor format."
-        },
-        {
-          "code": "values-have-no-fallback-envelope-key",
-          "severity": "warning",
-          "summary": "[VERIFIED LIVE 2026-08-11] Captured values land as unregistered order postmeta, one meta key per field, keyed by the merchant's own field name verbatim (a \"Gift message\" field saves as `gift_message`) -- no fixed prefix, no wrapper/envelope key (contrast woocommerce-product-addon.json's `_ppom_fields`, which gives an unambiguous fallback signal even without its field-group definitions). A postmeta key is only recognizable as this plugin's once it appears in the fulfilled CSV's `meta_key` column."
-        }
-      ]
-    }
-  ],
-  "quirks": [
-    "Exact plugin file id `woo-checkout-field-editor-pro/checkout-form-designer`, v2.1.9, active [VERIFIED LIVE 2026-08-19 via GET /wp/v2/plugins].",
-    "Values (captured order postmeta) are NOT a second profile entity here -- core-meta requires a static propertyPath, and this plugin's meta keys are only known per-site, after the CSV in checkout-field-definition's blocked[].fulfillment is fulfilled. NOT YET IMPLEMENTED: the INTENDED consumption path, once fulfilled, is for rp-import-codegen to read the parsed field list's metaKey column and look those exact keys up via the same generic meta_data[] scan any other plugin's unregistered order meta already goes through (fixed 2026-08-11 for Meta for WooCommerce / Discount Rules) -- but no such runtime consumer exists yet, for this plugin or for any other Data Extension Schema-backed capability in this repo. A fulfilled CSV snapshot means the field definitions were captured; it does not by itself mean any value has been written to ecom/order.extendedFields -- these are two distinct notions of success, and completion reporting must never conflate them.",
-    "The `checkout-field-csv` handler (lib/checkout-field-csv-parser.js) is plugin-agnostic by design -- it validates only this pipeline's own canonical CSV shape, never a vendor-specific export format. A different checkout-field-editor-style WooCommerce plugin found on another site gets its own profile file, but can reuse this exact handlerId rather than registering a near-duplicate parser."
-  ]
-}

package/skills/wix-replatform/resources/rp-source-wordpress/plugins/woo-discount-rules.json

@@ -1,74 +0,0 @@
-{
-  "schemaVersion": 1,
-  "plugin": "woo-discount-rules",
-  "displayName": "Discount Rules for WooCommerce",
-  "profileVersion": "2026-08",
-  "sourceOfTruth": "https://woocommerce.com/products/discount-rules-for-woocommerce/",
-  "distribution": "wordpress-org",
-  "capabilities": [
-    "commerce.applied-discounts",
-    "commerce.discount-rules"
-  ],
-  "detect": {
-    "pluginFileIds": [
-      "woo-discount-rules/woo-discount-rules.php"
-    ],
-    "recordProperties": [
-      "_wdr_discounts"
-    ],
-    "assetPathSlugs": [
-      "woo-discount-rules"
-    ]
-  },
-  "entities": [
-    {
-      "entity": "applied-discount",
-      "capability": "commerce.applied-discounts",
-      "channel": "core-meta",
-      "embeddedIn": ["/wc/v3/orders"],
-      "propertyPath": "_wdr_discounts",
-      "candidateTargetRefs": ["ecom/order-applied-discount"],
-      "pitfalls": [
-        {
-          "code": "rule-definitions-reconfigure-in-wix",
-          "severity": "warning",
-          "summary": "Per-order applied-discount records ride inside wc/v3/orders order-item meta_data under _wdr_discounts — real historical transactional data with a CONFIRMED Wix target: Order.appliedDiscounts[] (merchantDiscount variant + lineItemDiscounts[]) via Import Order — mapping confirmed 2026-08-16, see ecom/order-applied-discount. Rule *definitions* (the discount configuration itself, not applied history) are a SEPARATE entity on this profile (discount-rule-definition, below) with its own candidate target (ecom/discount-rule) — CORRECTED 2026-08-28: this used to read \"no candidate target at all, reconfigure-in-wix\" back when the wp-admin rule-config page looked unreachable; the underlying wdr_rules table turned out to be readable through wix-wp-plugin-v2\u2019s structure-bridge regardless of the page."
-        },
-        {
-          "code": "partial-channel-db-only-remainder",
-          "severity": "warning",
-          "summary": "A fuller per-item discount ledger also lives in a custom table (wdr_order_item_discounts per vendor-side research, 2026-08-11) with no REST surface — unreachable by this profile's channel. The order-meta summary this entity reads is real but may be a subset of the full applied-discount history."
-        }
-      ]
-    },
-    {
-      "entity": "discount-rule-definition",
-      "capability": "commerce.discount-rules",
-      "channel": "db-only",
-      "candidateTargetRefs": ["ecom/discount-rule"],
-      "pitfalls": [
-        {
-          "code": "admin-page-not-reachable-with-application-password",
-          "severity": "warning",
-          "summary": "DOWNGRADED from blocker 2026-08-28 -- a working read path now exists (see this entity's blocked[].fulfillment below), so this note is background, not a dead end. The rule configuration itself (triggers, effects, scope — 'buy X get Y', 'N% off orders over $Y', tiered pricing) renders only at wp-admin/admin.php?page=woo_discount_rules, a settings page with no REST route. VERIFIED against a live WordPress installation: a Basic-Auth GET against that URL with a valid Application Password 302-redirects to wp-login.php?reauth=1 — identical to an anonymous request. WordPress core does not extend Application Password auth to wp-admin page rendering. See plugins/README.md's admin-page-only channel note for why the admin PAGE specifically stays unreachable even though the underlying table is not."
-        }
-      ],
-      "blocked": [
-        {
-          "kind": "structure-bridge-plugin",
-          "resolution": "wix-wp-plugin-v2's discover-structure/query-structure routes read the wdr_rules table directly -- no dependency on the unreachable wp-admin settings page. VERIFIED LIVE 2026-08-28 against a real WordPress/WooCommerce test site: discover-structure returned wdr_rules's real 30-column schema, and query-structure returned real sample rows (id/title/enabled/discount_type/priority) with correct pagingMetadata. Site owner must install wix-wp-plugin-v2 and provide its migration key or an Application Password with manage_woocommerce, same credential this profile's other entities already need.",
-          "declined": false,
-          "fulfillment": {
-            "kind": "structure-bridge-plugin",
-            "handlerId": "wix-wp-plugin-v2",
-            "table": "wdr_rules"
-          }
-        }
-      ]
-    }
-  ],
-  "quirks": [
-    "Rule definitions (percentage/BOGO/tiered logic) are plugin configuration reproducible by reconfiguring in Wix, not durable customer data — only the applied-discount record per order is a migration candidate.",
-    "_wdr_discounts VERIFIED 2026-08-11 against the plugin's own source (ManageDiscount.php, github.com/WordpressPluginDirectory/woo-discount-rules): it is written via setOrderMeta($order, '_wdr_discounts', ...) at the ORDER level AND via setOrderItemMeta($order_item, '_wdr_discounts', ...) at the per-LINE-ITEM level — the same key appears in both wc/v3/orders meta_data and in each entry of orders[].line_items[].meta_data. An older version used the key _advanced_woo_discount_item_total_discount as a read fallback; a source site running a pre-rename version could still carry data under that key."
-  ]
-}

package/skills/wix-replatform/resources/rp-source-wordpress/plugins/woo-product-bundle.json

@@ -1,75 +0,0 @@
-{
-  "schemaVersion": 1,
-  "plugin": "woo-product-bundle",
-  "displayName": "WPC Product Bundles for WooCommerce",
-  "profileVersion": "2026-08",
-  "sourceOfTruth": "https://wpclever.net/downloads/product-bundles",
-  "distribution": "wordpress-org",
-  "capabilities": [
-    "commerce.product-bundles"
-  ],
-  "detect": {
-    "pluginFileIds": [
-      "woo-product-bundle/wpc-product-bundles"
-    ],
-    "recordProperties": [
-      "woosb_ids",
-      "_woosb_parent_id"
-    ],
-    "assetPathSlugs": [
-      "woo-product-bundle"
-    ]
-  },
-  "entities": [
-    {
-      "entity": "bundle-definition",
-      "channel": "core-meta",
-      "embeddedIn": ["/wc/v3/products"],
-      "propertyPath": "woosb_ids",
-      "candidateTargetRefs": [],
-      "pitfalls": [
-        {
-          "code": "no-wix-target-decided",
-          "severity": "warning",
-          "summary": "A WPC bundle is a normal WooCommerce product of custom type `woosb` whose composition rides in unregistered product meta `woosb_ids` inside the wc/v3/products meta_data array. The bundle product itself (name, price, media, SEO) migrates as a plain stores/product; the composition (which child products, at what quantity) has no native Wix Stores target — Catalog V3's productType enum is PHYSICAL | DIGITAL only, with no bundle/composite/child-product field (dev.wix.com product-object.md checked 2026-08-16). See capabilities-pending-decision.json: the suspected landing is bundle-as-product plus a CMS composition collection, mirroring Wix's own Velo 'Bundle Products' package model (bundleProductId + childProductIds in a CMS collection)."
-        },
-        {
-          "code": "children-referenced-by-source-id",
-          "severity": "warning",
-          "summary": "woosb_ids entries reference child products by WooCommerce product id (plus a cached sku): [VERIFIED IN PLUGIN SOURCE v8.6.4, class-backend.php process_product_meta_woosb, 2026-08-16] the value is an associative array keyed by a generated item key, each entry {id, sku, qty}. Any import must remap ids through the product crosswalk after the child products are created; sku is a secondary match key. Bundles created before WPC's v6-era format migration may still carry the legacy string form 'id1/qty1,id2/qty2' — the plugin ships its own admin-side migration routine for it, so an un-migrated source site can hold either shape [VERIFIED IN PLUGIN SOURCE v8.6.4, class-backend.php legacy-migration block, 2026-08-16]."
-        },
-        {
-          "code": "derived-bundle-price",
-          "severity": "warning",
-          "summary": "Unless woosb_disable_auto_price is 'on', the bundle's displayed price is derived from its children (sum, minus woosb_discount percentage or woosb_discount_amount) and the plugin keeps the WooCommerce _price/_regular_price meta in sync [VERIFIED IN PLUGIN SOURCE v8.6.4, class-woosb.php price-sync, 2026-08-16]. Migrating the bundle as a static product freezes that price: later child-price changes on Wix will not re-derive it. The wc/v3 price field carries the correct value at migration time."
-        }
-      ]
-    },
-    {
-      "entity": "order-item-bundle-linkage",
-      "channel": "core-meta",
-      "embeddedIn": ["/wc/v3/orders"],
-      "propertyPath": "_woosb_parent_id",
-      "candidateTargetRefs": [],
-      "pitfalls": [
-        {
-          "code": "no-wix-target-decided",
-          "severity": "warning",
-          "summary": "Historical orders record the bundle structure on their line items: the bundle's own line item carries _woosb_ids (minified composition string) and _woosb_price, and each bundled child line item carries _woosb_parent_id pointing at the bundle line [VERIFIED IN PLUGIN SOURCE v8.6.4, class-backend.php add_order_item_meta and class-woosb.php checkout_create_order_line_item, 2026-08-16]. Child items are real WooCommerce line items, so an order import that copies line items loses nothing sellable — only the parent/child grouping. No Wix eCom order-line-item field for that grouping has been verified; until one is, the linkage is candidate CMS/ledger data, not silently dropped."
-        },
-        {
-          "code": "sampling-may-miss-linkage",
-          "severity": "info",
-          "summary": "This meta appears only on orders that contain a bundle. A small order sample from a store with few bundle sales can legitimately lack the key, which detection then reports as property-absent (blocked: surface-changed) — that reads as profile drift but may simply mean no sampled order had a bundle. [NEEDS-VERIFICATION live: no order carrying this key has been observed yet.]"
-        }
-      ]
-    }
-  ],
-  "quirks": [
-    "Plugin file id is `woo-product-bundle/wpc-product-bundles` — the main-file basename differs from the directory and the /wp/v2/plugins id carries no .php suffix [VERIFIED LIVE 2026-08-16: plugin active, version 8.6.3, textdomain woo-product-bundle]. Never construct dir/dir.php.",
-    "Registers no REST namespace, no route, and no custom post type: /wp-json advertises no wpclever/woosb namespace and /wp/v2/types shows no bundle type [VERIFIED LIVE 2026-08-16]. The bundle is a WooCommerce product *type* (`woosb`, a product_type taxonomy term backed by class WC_Product_Woosb) — visible on wc/v3/products as type: 'woosb' and accepted by the ?type= filter, whose live 400 enum reads 'simple, grouped, external, variable, woosb, and pw-gift-card' [VERIFIED LIVE 2026-08-16].",
-    "Storage model: unregistered WooCommerce product meta — the plugin calls no register_post_meta/show_in_rest anywhere [VERIFIED IN PLUGIN SOURCE v8.6.4 (wordpress.org latest-stable), grep across includes/, 2026-08-16] — but WooCommerce product meta rides in the wc/v3/products meta_data array regardless of registration, so the composition is REST-visible via the authenticated Woo API, not via /wp/v2. [NEEDS-VERIFICATION on a live payload: no woosb product has been read live (?type=woosb returned none), so the meta_data shape is source-verified but not yet network-verified.]",
-    "Full per-bundle settings meta written by process_product_meta_woosb [VERIFIED IN PLUGIN SOURCE v8.6.4, class-backend.php, 2026-08-16]: woosb_ids, woosb_disable_auto_price (on/off), woosb_discount (percent), woosb_discount_amount, woosb_shipping_fee, woosb_manage_stock (on/off), woosb_limit_whole_min/max, woosb_total_limits (on/off) + woosb_total_limits_min/max, woosb_exclude_unpurchasable, woosb_layout, woosb_custom_price, woosb_before_text, woosb_after_text. Only woosb_ids is durable composition data; the rest are display/behaviour settings (reconfigure-or-drop, decided at mapping review).",
-    "Do not conflate with the official 'WooCommerce Product Bundles' (woocommerce-product-bundles), which is a different, premium plugin exposing bundled_items/bundled_by as TOP-LEVEL wc/v3 payload properties and a 'bundle' product type. This WPC plugin exposes nothing top-level; its signal is the woosb_ids meta_data key and the 'woosb' type value [DOCUMENTED — both plugins' models compared 2026-08-16]."
-  ]
-}

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

@@ -1,60 +0,0 @@
-{
-  "schemaVersion": 1,
-  "plugin": "woocommerce-gift-cards",
-  "displayName": "WooCommerce Gift Cards",
-  "profileVersion": "2026-08",
-  "sourceOfTruth": "https://woocommerce.com/document/woocommerce-gift-cards/",
-  "distribution": "premium-or-unlisted",
-  "capabilities": [
-    "commerce.gift-cards"
-  ],
-  "detect": {
-    "pluginFileIds": [
-      "woocommerce-gift-cards/woocommerce-gift-cards.php"
-    ],
-    "routes": [
-      "/wc/v3/gift-cards"
-    ],
-    "assetPathSlugs": [
-      "woocommerce-gift-cards"
-    ]
-  },
-  "entities": [
-    {
-      "entity": "gift-card",
-      "channel": "plugin-rest",
-      "route": "/wc/v3/gift-cards",
-      "recordKeyField": "id",
-      "candidateTargetRefs": [
-        "gift-cards/gift-card"
-      ],
-      "pitfalls": [
-        {
-          "code": "outstanding-balance-is-a-liability",
-          "severity": "blocker",
-          "summary": "Unspent gift card 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-length-may-not-fit-wix",
-          "severity": "blocker",
-          "summary": "Wix gift card codes must be 8-20 characters. Report any source code outside that range before import instead of rewriting it, because customers already hold the printed or emailed code."
-        },
-        {
-          "code": "partial-balance-policy-required",
-          "severity": "warning",
-          "summary": "Wix derives balance from transactions and only accepts an initial value, so a partly-redeemed card needs an explicit policy: import at remaining balance, or at face value with the spend replayed."
-        }
-      ]
-    }
-  ],
-  "excludeRoutes": [
-    {
-      "route": "/wc/v3/gift-cards/settings",
-      "reason": "plugin configuration, not gift card records"
-    }
-  ],
-  "quirks": [
-    "The plugin exposes gift cards under wc/v3; the route was observed live on a production store (2026-07-30).",
-    "Redemption history is per-card activity on the source but has no public Wix write surface, so it is reportable loss rather than migratable data."
-  ]
-}

package/skills/wix-replatform/resources/rp-source-wordpress/plugins/woocommerce-other-payment-gateway.json

@@ -1,44 +0,0 @@
-{
-  "schemaVersion": 1,
-  "plugin": "woocommerce-other-payment-gateway",
-  "displayName": "Custom Payment Gateway for WooCommerce",
-  "profileVersion": "2026-08",
-  "sourceOfTruth": "https://wordpress.org/plugins/woocommerce-other-payment-gateway/",
-  "distribution": "wordpress-org",
-  "capabilities": [
-    "commerce.payment-gateway-notes"
-  ],
-  "detect": {
-    "pluginFileIds": [
-      "woocommerce-other-payment-gateway/woocommerce-other-payment-gateway.php"
-    ],
-    "assetPathSlugs": [
-      "woocommerce-other-payment-gateway"
-    ]
-  },
-  "entities": [
-    {
-      "entity": "payment-note",
-      "channel": "plugin-rest-child",
-      "route": "/wc/v3/orders/{parentId}/notes",
-      "parentRoute": "/wc/v3/orders",
-      "candidateTargetRefs": ["ecom/order-merchant-note"],
-      "pitfalls": [
-        {
-          "code": "note-write-is-post-import-follow-up",
-          "severity": "warning",
-          "summary": "VERIFIED against the plugin's own source (class-woocommerce-other-payment-gateway.php, github.com/WordPressBugBounty/plugins-woocommerce-other-payment-gateway, 2026-08-11): the checkout-time admin note is saved via $order->add_order_note(...) — a genuine WooCommerce order note, reachable at GET /wc/v3/orders/{id}/notes (VERIFIED LIVE 2026-08-11: the site advertises /wc/v3/orders/(?P<order_id>[\\d]+)/notes). Wix target CONFIRMED 2026-08-16: ecom/order-merchant-note — Add Activities (MERCHANT_COMMENT, max 5000 chars) as a follow-up write AFTER Import Order; author/timestamp stamp at call time and cannot be backdated, so prefix source author/date into the message if provenance matters."
-        },
-        {
-          "code": "commingled-with-other-notes",
-          "severity": "warning",
-          "summary": "The /notes sub-resource returns ALL order notes (system-generated, other plugins', and this plugin's own), not a filtered subset — there is no dedicated meta key or note-type marker that isolates this plugin's payment note from the rest. Distinguishing it requires inspecting note content at import time, not just the read channel."
-        }
-      ]
-    }
-  ],
-  "quirks": [
-    "A generic/white-label offline payment gateway: the merchant defines the gateway's own title, instructions, and this optional admin-only note field at checkout. There is no per-gateway-instance identifier beyond the note text itself.",
-    "channel plugin-rest-child: this sub-resource cannot be listed on its own — it needs a real order id first. Discovery samples a representative few orders' /notes as a presence check, not a full-coverage read; the actual migration reader must iterate every order (see rp-import-codegen/SKILL.md)."
-  ]
-}

package/skills/wix-replatform/resources/rp-source-wordpress/plugins/woocommerce-pdf-invoices-packing-slips.json

@@ -1,57 +0,0 @@
-{
-  "schemaVersion": 1,
-  "plugin": "woocommerce-pdf-invoices-packing-slips",
-  "displayName": "PDF Invoices & Packing Slips for WooCommerce (WPO WCPDF)",
-  "profileVersion": "2026-09",
-  "sourceOfTruth": "https://wordpress.org/plugins/woocommerce-pdf-invoices-packing-slips/",
-  "distribution": "wordpress-org",
-  "capabilities": [
-    "commerce.order-invoice-documents"
-  ],
-  "detect": {
-    "pluginFileIds": [
-      "woocommerce-pdf-invoices-packing-slips/woocommerce-pdf-invoices-packingslips"
-    ]
-  },
-  "entities": [
-    {
-      "entity": "order-invoice-number",
-      "channel": "core-meta",
-      "recordKeyField": "id",
-      "propertyPath": "_wcpdf_invoice_number",
-      "candidateTargetRefs": [
-        "ecom/order-invoice-document"
-      ],
-      "metaKeys": [
-        "_wcpdf_invoice_number",
-        "_wcpdf_invoice_number_data",
-        "_wcpdf_invoice_date",
-        "_wcpdf_invoice_date_formatted"
-      ],
-      "pitfalls": [
-        {
-          "code": "installed-is-not-issued",
-          "severity": "blocker",
-          "summary": "Gate on ROW COUNT, never on plugin presence. This plugin can be installed and active on a store whose invoices are actually issued and numbered by the payment provider or an external accounting system, in which case its own tables and meta keys hold ZERO rows. This plugin's invoice-number key can sit at 0 rows while the provider has issued and numbered the documents. An installed invoicing plugin is not evidence that this plugin issued anything."
-        },
-        {
-          "code": "number-without-a-document",
-          "severity": "warning",
-          "summary": "An invoice NUMBER is not an invoice DOCUMENT. This plugin renders PDFs on demand rather than storing one file per order, so a store can carry numbers with no durable file anywhere. Where only a number exists, carry it as a reference on the imported order and create nothing: re-rendering a historical tax document produces a second body under the same legal identifier."
-        },
-        {
-          "code": "attachment-path-is-on-the-source-filesystem",
-          "severity": "warning",
-          "summary": "Where this plugin DOES keep files, they sit under the site's own uploads directory. Those bytes die with the source site, so they are the one case preserved without asking the merchant. Classify every discovered document URL by host before fetching it -- a discovered URL is untrusted input."
-        }
-      ]
-    }
-  ],
-  "quirks": [
-    {
-      "code": "key-names-vary-by-version-and-fork",
-      "severity": "warning",
-      "summary": "Invoice meta key names differ across versions, forks and the Professional extension, and other issuers use their own entirely (a provider key can differ from another version's only by a trailing capital letter). Discovery therefore matches key FAMILIES -- invoice-number, invoice-document, document-address, invoice-type -- rather than the exact names listed here, and reports families it finds but does not recognize."
-    }
-  ]
-}

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

@@ -1,141 +0,0 @@
-{
-  "schemaVersion": 1,
-  "plugin": "woocommerce-product-addon",
-  "displayName": "PPOM for WooCommerce",
-  "profileVersion": "2026-08",
-  "sourceOfTruth": "https://wordpress.org/plugins/woocommerce-product-addon/",
-  "distribution": "wordpress-org",
-  "capabilities": [
-    "commerce.product-addon-fields",
-    "commerce.order-addon-values"
-  ],
-  "detect": {
-    "pluginFileIds": [
-      "woocommerce-product-addon/woocommerce-product-addon"
-    ],
-    "routes": [
-      "/ppom/v1/admin/field-groups/context",
-      "/ppom/v1/nonces/file"
-    ],
-    "restNamespaces": [
-      "ppom/v1"
-    ],
-    "recordProperties": [
-      "_ppom_fields",
-      "_product_meta_id"
-    ],
-    "assetPathSlugs": [
-      "woocommerce-product-addon"
-    ]
-  },
-  "entities": [
-    {
-      "entity": "addon-field-group",
-      "channel": "plugin-rest",
-      "route": "/ppom/v1/admin/field-groups/context",
-      "candidateTargetRefs": ["stores/product-customization"],
-      "pitfalls": [
-        {
-          "code": "configuration-not-durable-data",
-          "severity": "info",
-          "summary": "A field group is plugin CONFIGURATION (field types, titles, data_names, options with per-option add-on prices, conditional-visibility rules), not customer data — but it has a confirmed native home: stores/product-customization (Stores Customizations V3 modifiers/custom inputs; mapping confirmed 2026-08-16). Open fidelity questions (conditional visibility, per-option pricing overrides, file-upload fields) are recorded as pitfalls on the target entity — pair field-by-field at mapping time."
-        },
-        {
-          "code": "no-enumeration-route",
-          "severity": "warning",
-          "summary": "There is NO route that lists field groups. GET /ppom/v1/admin/field-groups/context?productmeta_id=N returns exactly one group per numeric id (group settings + full fields[] array — [VERIFIED LIVE 2026-08-16]); with no or an unknown id it returns an empty template with productmeta_id 0, so a sampler that GETs the bare route sees a degenerate single object, not a collection. Enumerate ids by harvesting _product_meta_id from sampled /wc/v3/products meta_data, falling back to sequential id probing (ids are small AUTO_INCREMENT integers in the plugin's own table)."
-        },
-        {
-          "code": "admin-role-gated",
-          "severity": "warning",
-          "summary": "The context route is permission-gated by PPOM's own role setting (ppom_permission_mfields, default administrator — [DOCUMENTED] src/Admin/FieldModal/FieldModalRestController.php + Helpers::security_role(), v34.0.8). Unauthenticated GET returns 403 ppom_forbidden ([VERIFIED LIVE 2026-08-16]); the admin Application Password reads it fine — no extra credential, but an unauthenticated run cannot read field groups at all."
-        }
-      ]
-    },
-    {
-      "entity": "product-addon-assignment",
-      "channel": "core-meta",
-      "embeddedIn": [
-        "/wc/v3/products"
-      ],
-      "propertyPath": "_product_meta_id",
-      "candidateTargetRefs": ["stores/product-customization"],
-      "pitfalls": [
-        {
-          "code": "assignment-becomes-modifier-reference",
-          "severity": "warning",
-          "summary": "Which field group applies to which product is stored as unregistered product post meta _product_meta_id ([DOCUMENTED] define('PPOM_PRODUCT_META_KEY','_product_meta_id'), woocommerce-product-addon.php v34.0.8; value is the field-group id, historically also an array of ids). It surfaces through /wc/v3/products meta_data like other plugins' post meta, but [NEEDS-VERIFICATION] live for this key: no field group was attached to any sampled product, and a scan of their meta_data (2026-08-16) found no _product_meta_id. CONFIRMED mapping (2026-08-16): the assignment becomes the product's customization references — product.modifiers[] entries citing the crosswalked customization ids (see stores/product-customization)."
-        },
-        {
-          "code": "variation-rules-separate-key",
-          "severity": "info",
-          "summary": "Per-variation visibility rules live in a second unregistered product meta key, _ppom_variation_meta_rules ([DOCUMENTED] PPOM_VARIATION_META_KEY, v34.0.8) — read it alongside _product_meta_id when a variable product restricts add-on fields to specific variations."
-        }
-      ]
-    },
-    {
-      "entity": "order-line-item-addon-values",
-      "channel": "core-meta",
-      "embeddedIn": [
-        "/wc/v3/orders"
-      ],
-      "propertyPath": "_ppom_fields",
-      "candidateTargetRefs": ["ecom/order-line-item-options"],
-      "pitfalls": [
-        {
-          "code": "description-lines-carry-values",
-          "severity": "warning",
-          "summary": "DURABLE customer data: the add-on values a buyer entered at purchase time are saved on each order line item — one visible meta entry per field keyed by its data_name (display value), plus the whole raw payload under hidden meta _ppom_fields since v15.2 ([DOCUMENTED] OrderHandler::order_item_meta(), src/WooCommerce/Order/OrderHandler.php v34.0.8: $item->update_meta_data($key, $meta_value) per field, then $item->update_meta_data('_ppom_fields', $values['ppom'])). Both ride in /wc/v3/orders line_items[].meta_data. CONFIRMED direction (2026-08-16): Import Order lineItems[].descriptionLines[] (writable, max 20 lines, name.original <=100 chars, plainText.original <=600 chars), optionally mirroring machine-readable selections into lineItems[].catalogReference.options — target ecom/order-line-item-options; lineItems[].modifierGroups stays read-only on import ([DOCUMENTED] dev.wix.com import-order.md, fetched 2026-08-16)."
-        },
-        {
-          "code": "not-observed-on-reference-site",
-          "severity": "info",
-          "summary": "[NEEDS-VERIFICATION] live record shape: the sampled orders (scanned 2026-08-16) carry no PPOM line-item meta (no field group was attached to any product, so no order could capture values). The write path is verified against the plugin's own source, and the read channel (line_items[].meta_data via /wc/v3/orders) is the same one verified live for woo-discount-rules; the first source site with real PPOM orders should confirm the payload shape."
-        },
-        {
-          "code": "file-upload-values-reference-site-files",
-          "severity": "warning",
-          "summary": "File-upload and image-cropper field values reference files hosted on the WordPress site (PPOM renames uploads per order — [DOCUMENTED] OrderHandler::rename_files() / PPOM\\Files\\Handler, v34.0.8; cropper base64 payloads are stripped from _ppom_fields since v24.5). Migrating these values needs a media copy step, not just the meta value; the bare filename in the meta is not a working URL on Wix."
-        },
-        {
-          "code": "unprefixed-visible-meta-keys",
-          "severity": "info",
-          "summary": "The per-field visible meta keys are the merchant-chosen data_names (e.g. 'engraving_text') with no ppom_ prefix, so they cannot be recognized as PPOM's by key shape alone — resolve them through the field group's data_name list, or prefer the _ppom_fields envelope which is unambiguous."
-        }
-      ]
-    }
-  ],
-  "excludeRoutes": [
-    {
-      "route": "/ppom/v1/nonces/file",
-      "reason": "Runtime helper: returns fresh nonces for frontend file uploads (public, always registered). Useful as a detection signal, never data."
-    },
-    {
-      "route": "/ppom/v1/admin/field-groups/schema/*",
-      "reason": "Field-type JSON schema for the admin React modal (UI metadata, per field type), not site data."
-    },
-    {
-      "route": "/ppom/v1/set/product",
-      "reason": "Write route of the optional PPOM API (registered only when the API setting is enabled) — mutation, never read."
-    },
-    {
-      "route": "/ppom/v1/delete/product",
-      "reason": "Write route of the optional PPOM API — mutation, never read."
-    },
-    {
-      "route": "/ppom/v1/set/order",
-      "reason": "Write route of the optional PPOM API — mutation, never read."
-    },
-    {
-      "route": "/ppom/v1/delete/order",
-      "reason": "Write route of the optional PPOM API — mutation, never read."
-    }
-  ],
-  "quirks": [
-    "Exact plugin file id woocommerce-product-addon/woocommerce-product-addon, active, v34.0.8 [VERIFIED LIVE 2026-08-16 via GET /wp/v2/plugins]. Formerly 'NM Personalized Order Meta' — which is why the custom table is named nm_personalized.",
-    "STORAGE MODEL: field-group definitions live in the plugin's OWN TABLE {prefix}nm_personalized ([DOCUMENTED] define('PPOM_TABLE_META','nm_personalized') + PPOM_Meta_Repository, v34.0.8), rows keyed productmeta_id — no CPT, nothing in /wp/v2/types ([VERIFIED LIVE 2026-08-16]). The only REST window into it is the always-registered admin route /ppom/v1/admin/field-groups/context (per-id). Product attachment is unregistered post meta _product_meta_id; captured order values are order-item meta (_ppom_fields + per-data_name entries) — REST-visible through /wc/v3 payloads, not through registered meta.",
-    "The ppom/v1 data/write API (/get/product, /get/id/{id}, /get/order, /set/*, /delete/*) is registered ONLY when the merchant enables the API setting AND sets a secret key (ppom_api_enable + ppom_rest_secret_key — [DOCUMENTED] Helpers::is_api_enable() + Rest\\Routes, v34.0.8). Off by default and absent from the live REST index [VERIFIED LIVE 2026-08-16]; the always-on routes are /ppom/v1/nonces/file (public) and /ppom/v1/admin/field-groups/{context,schema} (role-gated). Do not treat the optional routes' absence as the plugin being inactive.",
-    "Field-group configuration vs durable data: the group (field definitions, option prices, conditional logic) is reconfigurable state whose Wix home is Stores Customizations V3 modifiers/custom inputs (stores/product-customization); the values captured on historical orders are durable customer data whose Wix home is Import Order descriptionLines (ecom/order-line-item-options). Both mappings confirmed 2026-08-16.",
-    "Frontend assets (asset-path fingerprint) are enqueued only on product pages whose product has a field group attached — the homepage of a site with an unattached group shows no woocommerce-product-addon asset path [VERIFIED LIVE 2026-08-16]. Treat assetPathSlugs as a weak, page-dependent signal; the public /ppom/v1 namespace in the REST index is the reliable no-auth signal."
-  ]
-}