@wix/agent-skills 1.33.0 → 1.34.0

package/skills/wix-replatform/resources/rp-source-wordpress/plugins/requires-development.json

@@ -0,0 +1,88 @@
+{
+  "schemaVersion": 1,
+  "description": "The Requires development register: capabilities a NAMED HUMAN has determined Wix has no surface for. This is the only place that verdict may live, and the only source of the requires-development status — automation is limited to migration-planned, no-need-to-migrate, or pending.\n\nWhy the restriction: an agent concluded twice that Wix had no target (gift cards, events) and was wrong both times, because Wix splits capabilities across doc trees and a service plugin reads like an absent write API. A wrong 'impossible' is the most expensive error in this system: it tells a customer to abandon data that could have moved.\n\nEvery entry needs `decidedBy` and `decidedOn` alongside the recorded search. Entries are reviewable and reversible: if a target later appears, validation rejects the entry.",
+  "capabilities": [
+    {
+      "capability": "commerce.product-bundles",
+      "reason": "Fixed product bundles (one purchasable product composed of specific child products with quantities at a set price — WPC Product Bundles' woosb_ids, and the official WooCommerce Product Bundles / Composite Products extensions alike) have no native Wix Stores target: Catalog V3 productType is PHYSICAL | DIGITAL only, with no composed-product entity or child-product references, and order history's parent/child line-item linkage (_woosb_ids / _woosb_parent_id) has no eCom order field to receive it. Interim migration path: the bundle product migrates as a plain stores/product with its derived price frozen at migration-time value, and the composition lands in a CMS collection keyed by the product crosswalk — the same shape Wix's own Velo 'Bundle Products' package uses.",
+      "searched": "bundle, composite product, product kit, product set, child products — dev.wix.com and support.wix.com (2026-08-16, WebSearch/WebFetch): Catalog V3 product-object.md (productType PHYSICAL|DIGITAL only); dev.wix.com/docs/velo/articles/velo-package-readmes/wix-stores-bundle-products (Velo site-code pattern: plain product + CMS Bundles collection, not a write API); support.wix.com/en/article/wix-stores-selling-mix-and-match-product-bundles — evaluated 2026-08-16: mix-and-match is a category + automatic-discount pattern for customer-assembled combos (no fixed-bundle SKU, no composed-product entity, no API) and does NOT receive fixed bundles.",
+      "decidedBy": "Product Owner",
+      "decidedOn": "2026-08-16",
+      "note": "The missing Wix capability is a bundle/composite product type writable at creation (Stores/Catalog). A gap with a working workaround (CMS composition) needs no standalone operator task. Reversible: if Catalog V3 gains a bundle primitive, validation rejects this entry once a target entity claims the capability."
+    },
+    {
+      "capability": "unknown-plugin:dropshipping-xml-for-woocommerce/dropshipping-xml-for-woocommerce",
+      "plugin": "dropshipping-xml-for-woocommerce/dropshipping-xml-for-woocommerce",
+      "project": "reference-migration",
+      "reason": "Dropshipping supplier-linkage: no general-merchant-facing Wix write API represents linking a store's products to an external dropshipping supplier's catalog/fulfillment feed.",
+      "evidence": [
+        {
+          "searched": "dropshipping supplier catalog sync; supplier fulfillment linkage; dropship product import API",
+          "method": "WebSearch + WebFetch against dev.wix.com, 2026-08-12",
+          "urls": [
+            "https://dev.wix.com/docs/api-reference/business-solutions/suppliers-hub/suppliers/introduction",
+            "https://dev.wix.com/docs/build-apps/get-started/tutorials/common-use-cases/extensions-and-apis-for-dropshipping-apps",
+            "https://dev.wix.com/docs/api-reference/business-solutions/stores/catalog-v3/introduction"
+          ],
+          "found": "The business-solutions tree does have a Marketplace Suppliers API (suppliers-hub) whose Supplier object carries a DROPSHIPPING/WHOLESALE type -- but per its own docs, quoted verbatim: \"This API is available only to approved Wix business partners and requires a signed business agreement with Wix. To apply for partnership, contact Wix.\" Its `Supplier` models the marketplace-provider relationship (an entity that supplies a Wix *marketplace provider*, who then resells to end users), not a per-product external-supplier link an ordinary merchant's own store can create on its own products. The other hits (\"Extensions and APIs for Dropshipping Apps\", Catalog V3) are for *building* a dropshipping-supplier app that provides products TO other Wix stores (an SPI direction), or for generic inventory/stock management -- neither is a write path for importing an existing store's own supplier-linkage configuration.",
+          "conclusion": "SPI / partner-gated surface, not a general write API reachable by a normal site migration. No import path exists today for this capability."
+        }
+      ],
+      "decidedBy": "user",
+      "decidedOn": "2026-08-12",
+      "decisionContext": "the mapping review gate, resolving a previously open question (left as a genuine open question in mapping-gaps.json rather than silently resolved).",
+      "searched": "dropshipping supplier catalog sync, supplier fulfillment linkage, dropship product import API — searched against dev.wix.com business-solutions tree (WebSearch/WebFetch, 2026-08-12). Found the Marketplace Suppliers API (suppliers-hub), but it is restricted to approved Wix business partners with a signed business agreement and models the marketplace-provider relationship, not a per-product external-supplier link on an existing store. No general write API found."
+    },
+    {
+      "capability": "unknown-plugin:woo-alidropship/woo-alidropship",
+      "plugin": "woo-alidropship/woo-alidropship",
+      "project": "reference-migration",
+      "reason": "Dropshipping supplier-linkage: same finding as dropshipping-xml-for-woocommerce -- no general-merchant-facing Wix write API for supplier catalog/fulfillment linkage.",
+      "evidence": [
+        {
+          "searched": "dropshipping supplier catalog sync; supplier fulfillment linkage; dropship product import API",
+          "method": "WebSearch + WebFetch against dev.wix.com, 2026-08-12",
+          "urls": [
+            "https://dev.wix.com/docs/api-reference/business-solutions/suppliers-hub/suppliers/introduction",
+            "https://dev.wix.com/docs/build-apps/get-started/tutorials/common-use-cases/extensions-and-apis-for-dropshipping-apps"
+          ],
+          "found": "Same Marketplace Suppliers API finding as dropshipping-xml-for-woocommerce: partner-gated (signed business agreement required), and its Supplier object models the marketplace-provider relationship, not a per-product external-supplier link on an existing store.",
+          "conclusion": "SPI / partner-gated surface, not a general write API reachable by a normal site migration. No import path exists today for this capability."
+        }
+      ],
+      "decidedBy": "user",
+      "decidedOn": "2026-08-12",
+      "decisionContext": "the mapping review gate, resolving a previously open question (left as a genuine open question in mapping-gaps.json rather than silently resolved).",
+      "searched": "dropshipping supplier catalog sync, supplier fulfillment linkage, dropship product import API — searched against dev.wix.com business-solutions tree (WebSearch/WebFetch, 2026-08-12). Same Marketplace Suppliers API finding as dropshipping-xml-for-woocommerce: partner-gated, not a general write surface."
+    },
+    {
+      "capability": "unknown-plugin:syncee-global-dropshipping/plugin",
+      "plugin": "syncee-global-dropshipping/plugin",
+      "project": "reference-migration",
+      "reason": "Dropshipping supplier-linkage: same finding as dropshipping-xml-for-woocommerce -- no general-merchant-facing Wix write API for supplier catalog/fulfillment linkage.",
+      "evidence": [
+        {
+          "searched": "dropshipping supplier catalog sync; supplier fulfillment linkage; dropship product import API",
+          "method": "WebSearch + WebFetch against dev.wix.com, 2026-08-12",
+          "urls": [
+            "https://dev.wix.com/docs/api-reference/business-solutions/suppliers-hub/suppliers/introduction",
+            "https://dev.wix.com/docs/build-apps/get-started/tutorials/common-use-cases/extensions-and-apis-for-dropshipping-apps"
+          ],
+          "found": "Same Marketplace Suppliers API finding as dropshipping-xml-for-woocommerce: partner-gated (signed business agreement required), and its Supplier object models the marketplace-provider relationship, not a per-product external-supplier link on an existing store. Note: Syncee is also independently available as a Wix App Market app for merchants, which is a separate reconfigure-in-wix path a merchant could adopt fresh in Wix -- but that is not a migration of this plugin's existing WooCommerce-side linkage/data, which is what this capability tracks.",
+          "conclusion": "SPI / partner-gated surface, not a general write API reachable by a normal site migration. No import path exists today for this capability's existing source-side configuration."
+        }
+      ],
+      "decidedBy": "user",
+      "decidedOn": "2026-08-12",
+      "decisionContext": "the mapping review gate, resolving a previously open question (left as a genuine open question in mapping-gaps.json rather than silently resolved).",
+      "searched": "dropshipping supplier catalog sync, supplier fulfillment linkage, dropship product import API — searched against dev.wix.com business-solutions tree (WebSearch/WebFetch, 2026-08-12). Same Marketplace Suppliers API finding: partner-gated, not a general write surface for migrating this plugin's existing source-side linkage/data (Syncee's own Wix App Market app is a separate reconfigure-in-wix path, not a migration of this data)."
+    },
+    {
+      "capability": "commerce.abandoned-carts",
+      "reason": "Historical abandoned carts cannot be imported into Wix. The eCommerce AbandonedCheckout entity has NO create, import or upsert method at any level — the whole public AbandonedCheckoutService is Get / Delete / BulkDelete / Query / Search / RedirectToCheckout — and the entity is only ever derived by the platform from a live shopper session that went incomplete. The documented workaround (recreate the antecedent cart and let the pipeline detect it) was piloted live and does not work: carts created live, including one carrying a genuine platform-assigned visitorId plus a Wix-resolved contactId, produced ZERO AbandonedCheckout records, however long they sat. Even had it worked, Cart.createdDate is readOnly, so every backfilled cart is stamped with the import date rather than the real abandonment date: a year of history would read as abandoned today and would trigger recovery mail about carts people left months ago. Do NOT attempt this path. The PEOPLE behind abandoned carts are a separate matter and remain migratable as crm/contact (email only, never a subscription status — an abandoned cart is not consent).",
+      "searched": "2026-09-07/08. (1) SearchWixRESTDocumentation 'create abandoned checkouts / import historical abandoned cart records' -> only Get/Query/Search/Delete/BulkDelete plus created/updated/recovered/deleted webhooks; the API introduction states the platform creates the entity itself when a customer starts a checkout or a member abandons a cart. (2) Full method enumeration of the AbandonedCheckout resource via the API spec (resourceId 078d1b42-5b92-4ad4-8160-01247260582e): 6 methods, no create at any level. (3) Cart schema inspection: buyerInfo.visitorId / memberId / userId are all readOnly (platform-assigned from the calling session) and Cart.createdDate is readOnly. buyerInfo.contactId is writable in the schema but REFUSED in practice on the admin path — sent at CreateCart and again at UpdateCart, read back null both times. (4) Live pilot: admin-token carts (no identity) and a visitor-token cart (contactId auto-resolved by Wix from the buyer email) — none classified. The Stores catalog gate passed, so the catalog was never the blocker. (5) The Wix Stores AbandonedCarts CMS collection is a read-only Wix App system collection, not an authorable target.",
+      "decidedBy": "user",
+      "decidedOn": "2026-09-08"
+    }
+  ]
+}

package/skills/wix-replatform/resources/rp-source-wordpress/plugins/seo-by-rank-math.json

@@ -0,0 +1,80 @@
+{
+  "schemaVersion": 1,
+  "plugin": "seo-by-rank-math",
+  "displayName": "Rank Math SEO",
+  "profileVersion": "2026-08",
+  "sourceOfTruth": "https://wordpress.org/plugins/seo-by-rank-math/",
+  "distribution": "wordpress-org",
+  "capabilities": [
+    "content.seo-meta"
+  ],
+  "detect": {
+    "pluginFileIds": [
+      "seo-by-rank-math/rank-math"
+    ],
+    "restNamespaces": [
+      "rankmath/v1"
+    ],
+    "recordProperties": [
+      "rank_math_title",
+      "rank_math_description",
+      "rank_math_canonical_url",
+      "rank_math_focus_keyword",
+      "rank_math_robots",
+      "rankMath"
+    ],
+    "assetPathSlugs": [
+      "seo-by-rank-math"
+    ]
+  },
+  "entities": [
+    {
+      "entity": "post-seo-meta",
+      "channel": "export-file",
+      "candidateTargetRefs": [
+        "seo/item-seo-tags",
+        "blog/post",
+        "stores/product"
+      ],
+      "pitfalls": [
+        {
+          "code": "unregistered-postmeta-invisible-to-rest",
+          "severity": "blocker",
+          "summary": "Rank Math calls register_meta ZERO times. [VERIFIED IN PLUGIN SOURCE v1.0.276 (wordpress.org, the exact version installed), grep -rn 'register_meta' across includes/ returns nothing, 2026-08-16.] Its per-post SEO therefore lives entirely in unregistered wp_postmeta rows and never appears in the REST `meta` object, in any context, with any credential. The only register_rest_field it declares is `rankMath` on the `page` post type, and only when Helper::is_site_editor() is true and the caller can `read` (includes/rest/class-post.php:53) - an editor-screen convenience, not a data surface. So there is NO REST read path for Rank Math SEO data; it is postmeta, which means a WXR export carries it, hence channel export-file rather than db-only."
+        },
+        {
+          "code": "capability-shared-with-yoast",
+          "severity": "info",
+          "summary": "This profile claims content.seo-meta, the same capability as wordpress-seo (Yoast), because it is the same business capability: per-item SEO title, meta description, canonical, Open Graph/Twitter overrides, robots directives and focus keyphrase. The Wix decision is identical for both, which is the point of keying knowledge on capability rather than plugin. Only the read channel differs - Yoast is REST-readable, Rank Math is not."
+        },
+        {
+          "code": "meta-keys-source-verified-not-live",
+          "severity": "warning",
+          "summary": "The per-record keys are rank_math_title, rank_math_description, rank_math_canonical_url, rank_math_focus_keyword, rank_math_robots (plus rank_math_advanced_robots), rank_math_facebook_title / _description / _image, rank_math_twitter_title / _description / _image, rank_math_permalink, rank_math_breadcrumb_title, rank_math_pillar_content, rank_math_rich_snippet / rank_math_schema_*, rank_math_seo_score and rank_math_exclude_sitemap. [VERIFIED IN PLUGIN SOURCE v1.0.276, string-frequency scan over includes/, 2026-08-16.] [NEEDS-VERIFICATION on a live site with Rank Math ACTIVE: an installed but INACTIVE plugin offers no payload, no route and no asset path could be observed - every claim here is source-derived.]"
+        },
+        {
+          "code": "detection-must-not-depend-on-being-active",
+          "severity": "warning",
+          "summary": "An inactive plugin registers no REST namespace, enqueues no asset and writes no record property, so restNamespaces / recordProperties / assetPathSlugs all fail. [VERIFIED LIVE 2026-08-16: no rankmath/v1 namespace in the REST index of a site where the plugin is installed at version 1.0.276, and no seo-by-rank-math asset path in the homepage HTML.] Detection here rests on pluginFileIds against the admin-gated /wp/v2/plugins list, which is exactly the 'strongest signal first' principle - without the Application Password an installed-but-inactive Rank Math is invisible. That is correct behaviour: an inactive SEO plugin's stale postmeta is not what the live site renders, and a run that cannot see it should say the plugin list was incomplete rather than guess."
+        },
+        {
+          "code": "both-seo-plugins-installed-is-ambiguous",
+          "severity": "warning",
+          "summary": "A site can have Yoast ACTIVE and Rank Math INACTIVE simultaneously - a common state, because Rank Math ships an importer for Yoast data and users trial one against the other. When both are detected, the ACTIVE one is the source of truth for what the site currently renders; the inactive one's postmeta may be stale, partial, or an abandoned import. Never merge the two into one SEO record. Surface the conflict at the mapping review rather than picking silently."
+        },
+        {
+          "code": "no-import-without-a-user-supplied-file",
+          "severity": "warning",
+          "summary": "channel export-file means this entity is Blocked - recoverable (kind: user-file) until the user supplies a WXR export, and never a limitation of Wix: seo/item-seo-tags is a verified write surface waiting for the data. Application Passwords authenticate REST and XML-RPC only, never wp-admin, so the WXR is something the user PRODUCES and supplies - we cannot fetch it. Rank Math's own Status & Tools > Import & Export exports plugin SETTINGS, not per-post meta, so it is not an alternative."
+        }
+      ]
+    }
+  ],
+  "quirks": [
+    "Plugin file id is `seo-by-rank-math/rank-math` - the main-file basename differs from the directory and the /wp/v2/plugins id carries no .php suffix [VERIFIED LIVE 2026-08-16: status INACTIVE, version 1.0.276, textdomain seo-by-rank-math]. Never construct dir/dir.php. The directory exists and is served (GET /wp-content/plugins/seo-by-rank-math/rank-math.php returns HTTP 200 with an empty body), which confirms the directory slug but is not a detection signal.",
+    "Storage model: unregistered post meta. Decisive for this profile - it is the reason the channel is export-file and not core-meta, and it is the single fact that separates Rank Math from Yoast for migration purposes even though the two hold the same capability.",
+    "REST namespace is `rankmath/v1` when active [VERIFIED IN PLUGIN SOURCE v1.0.276, includes/rest/class-rest-helper.php:29 `const BASE = 'rankmath/v1'`]. Its routes are admin/editor actions and dashboards - /updateMetaBulk (POST, capability-gated write), /getHead (read-only URL-to-head helper, registered only when the headless_support setting is on), /getFeaturedImageId, /disconnectSite, /setupWizard/*. None is a readable collection of SEO records, so an active Rank Math would still not yield a plugin-rest data route; the same conclusion the live /yoast/v1 walk reached for Yoast.",
+    "Rank Math also owns custom tables (rank_math_redirections, rank_math_internal_links, rank_math_analytics_*) [VERIFIED IN PLUGIN SOURCE v1.0.276]. Redirections are durable content.url-redirects data not claimed by this profile. Wix has a public SEO Redirects API in Developer Preview, but RePlatform application and verification remain pending; see the seo domain url-redirect-api-not-yet-integrated pitfall. Internal-links and analytics tables are derived indexes and reports, not data to move.",
+    "Do not confuse the free plugin (this one, wordpress.org slug seo-by-rank-math) with Rank Math PRO (seo-by-rank-math-pro), which is a separate premium add-on directory and would appear as its own row in /wp/v2/plugins."
+  ]
+}

package/skills/wix-replatform/resources/rp-source-wordpress/plugins/seriously-simple-podcasting.json

@@ -0,0 +1,46 @@
+{
+  "schemaVersion": 1,
+  "plugin": "seriously-simple-podcasting",
+  "displayName": "Seriously Simple Podcasting",
+  "profileVersion": "2026-08",
+  "sourceOfTruth": "https://wordpress.org/plugins/seriously-simple-podcasting/",
+  "distribution": "wordpress-org",
+  "capabilities": ["content.podcast"],
+  "detect": {
+    "pluginFileIds": ["seriously-simple-podcasting/seriously-simple-podcasting.php"],
+    "routes": ["/ssp/v1/episodes"],
+    "restNamespaces": ["ssp/v1"],
+    "restBases": ["podcast"],
+    "assetPathSlugs": ["seriously-simple-podcasting"]
+  },
+  "entities": [
+    {
+      "entity": "episode",
+      "channel": "plugin-rest",
+      "route": "/ssp/v1/episodes",
+      "recordKeyField": "id",
+      "candidateTargetRefs": [],
+      "pitfalls": [
+        {
+          "code": "no-native-podcast-target",
+          "severity": "warning",
+          "summary": "Wix has no native podcast entity. CMS archival is a signed eligible fallback for content.podcast (plugins/cms-fallback-eligible.json): each migration keeps the capability pending until the merchant approves or declines archiving the episodes in CMS at the mapping review. If approved, episodes arrive as CMS data and audio files as media; no podcast player or RSS feed reappears automatically on Wix."
+        },
+        {
+          "code": "podcast-route-is-settings-not-records",
+          "severity": "info",
+          "summary": "/ssp/v1/podcast (singular) is the show's settings/feed object, not a record collection; the durable records are the episodes (verified live 2026-08-10 on SSP 3.16.3 — the previously declared /ssp/v1/podcasts route does not exist)."
+        }
+      ]
+    }
+  ],
+  "dataRoutePatterns": [
+    {
+      "pattern": "/ssp/v1/*",
+      "reason": "Seriously Simple Podcasting routes expose durable podcast records"
+    }
+  ],
+  "quirks": [
+    "Episode audio is referenced by URL in record fields; media reachability rules apply as for any external media URL."
+  ]
+}

package/skills/wix-replatform/resources/rp-source-wordpress/plugins/strong-testimonials.json

@@ -0,0 +1,55 @@
+{
+  "schemaVersion": 1,
+  "plugin": "strong-testimonials",
+  "displayName": "Strong Testimonials",
+  "profileVersion": "2026-08",
+  "sourceOfTruth": "https://wordpress.org/plugins/strong-testimonials/",
+  "distribution": "wordpress-org",
+  "capabilities": [
+    "content.testimonials"
+  ],
+  "detect": {
+    "pluginFileIds": [
+      "strong-testimonials/strong-testimonials.php"
+    ],
+    "assetPathSlugs": [
+      "strong-testimonials"
+    ]
+  },
+  "entities": [
+    {
+      "entity": "testimonial",
+      "capability": "content.testimonials",
+      "channel": "db-only",
+      "candidateTargetRefs": [],
+      "pitfalls": [
+        {
+          "code": "shared-posts-table-requires-filter",
+          "severity": "warning",
+          "summary": "Testimonials are wp_posts rows (post_type=wpm-testimonial) with no dedicated table and no show_in_rest -- reading the posts table WITHOUT this entity's declared where-filter would return every post type on the site (products, pages, attachments, etc.), not just testimonials. sampleStructureRequest.where is mandatory here, not optional -- enforced by plugin-knowledge.js's SHARED_CORE_TABLES_REQUIRING_WHERE check."
+        },
+        {
+          "code": "extra-fields-in-key-scoped-postmeta",
+          "severity": "warning",
+          "summary": "Rating, category, and other structured fields (if used) live in postmeta keys. These are READABLE through wix-wp-plugin-v2, key-scoped: list the distinct meta_key values for these testimonials' post ids, then read the keys that matter with a scoped request (max 50 keys). Postmeta is not refused -- do not accept a metadata gap here without running the two-step read first. post_title/post_content/post_status/dates remain directly readable from wp_posts."
+        },
+        {
+          "code": "empty-on-real-test-site",
+          "severity": "info",
+          "summary": "VERIFIED LIVE 2026-08-29: a filtered query against the posts table (where post_type = wpm-testimonial) executes correctly and may return zero rows when the plugin is active but unused -- the mechanism is real and reachable; an empty result means there is nothing to migrate."
+        }
+      ],
+      "blocked": [
+        {
+          "kind": "structure-bridge-plugin",
+          "resolution": "wix-wp-plugin-v2 can read the shared posts table filtered to this plugin's post_type -- VERIFIED LIVE 2026-08-29: a filtered query (where post_type = wpm-testimonial) executes correctly and returns pagingMetadata.total (0 when no testimonials are configured). Reachability is confirmed; fulfillment wiring is deferred until a Wix target is researched and approved at the mapping review. The working filtered query, for reference once a target is approved: select ID/post_title/post_content/post_excerpt/post_status/post_date where post_type=wpm-testimonial, orderBy ID asc.",
+          "declined": false
+        }
+      ]
+    }
+  ],
+  "quirks": [
+    "Registers custom post type wpm-testimonial: author (post_title), body (post_content). Confirmed via the plugin's own source (shortcode-form.php).",
+    "No native Wix target researched or approved yet -- do not assume a generic CMS collection is the right landing spot without that approval (see e.g. Wix Stores' native wishlist feature, which was nearly mis-defaulted to CMS the same way for a different plugin). Do not wire the testimonial entity's blocked[] fulfillment on your own judgment before that target decision is made."
+  ]
+}

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

@@ -0,0 +1,99 @@
+{
+  "schemaVersion": 1,
+  "plugin": "subscriptions-for-woocommerce",
+  "displayName": "Subscriptions For WooCommerce",
+  "profileVersion": "2026-08",
+  "sourceOfTruth": "https://wordpress.org/plugins/subscriptions-for-woocommerce/",
+  "distribution": "wordpress-org",
+  "capabilities": [
+    "commerce.subscription-products",
+    "commerce.subscription-contracts"
+  ],
+  "detect": {
+    "pluginFileIds": [
+      "subscriptions-for-woocommerce/subscriptions-for-woocommerce"
+    ],
+    "routes": [
+      "/wsp-route/v1/wsp-view-subscription"
+    ],
+    "restNamespaces": [
+      "wsp-route/v1"
+    ],
+    "recordProperties": [
+      "_wps_sfw_product"
+    ],
+    "assetPathSlugs": [
+      "subscriptions-for-woocommerce"
+    ]
+  },
+  "credentials": [
+    {
+      "key": "wsp_api_secret_key",
+      "description": "Plugin-specific API secret for /wsp-route/v1/wsp-view-subscription, passed as the consumer_secret query parameter. Generated in the plugin's own settings (WP Swings > Subscriptions > API settings) and stored in the wsp_api_secret_key option; the API must also be switched on there (wsp_enable_api_features option = 'on'). The admin Application Password does NOT authorize this route — [VERIFIED LIVE 2026-08-16] a GET with a valid admin Application Password returned 403 rest_forbidden; [DOCUMENTED] permission callback validates only consumer_secret (plugin source 2.0.1, package/rest-api/class-subscriptions-for-woocommerce-rest-api.php, plugins.svn.wordpress.org, read 2026-08-16)."
+    }
+  ],
+  "entities": [
+    {
+      "entity": "subscription-product-settings",
+      "channel": "core-meta",
+      "embeddedIn": ["/wc/v3/products"],
+      "propertyPath": "_wps_sfw_product",
+      "candidateTargetRefs": ["stores/subscription-product"],
+      "pitfalls": [
+        {
+          "code": "flag-plus-sibling-meta-keys",
+          "severity": "warning",
+          "summary": "_wps_sfw_product ('yes'/'no') only marks the product; the actual recurring-offer settings are sibling unregistered postmeta keys on the same product: wps_sfw_subscription_number (cadence count), wps_sfw_subscription_interval (day|week|month|year), wps_sfw_subscription_expiry_number + wps_sfw_subscription_expiry_interval (subscription length), wps_sfw_subscription_initial_signup_price, wps_sfw_subscription_free_trial_number + wps_sfw_subscription_free_trial_interval. [DOCUMENTED] plugin source 2.0.1 admin save handler (admin/class-subscriptions-for-woocommerce-admin.php lines 1046-1064, plugins.svn.wordpress.org, read 2026-08-16). All of them ride inside the product's meta_data[] array on /wc/v3/products, the same way this KB's other core-meta profiles read theirs. [NEEDS-VERIFICATION] live appearance in meta_data: no subscription product has been read live (a product scan on 2026-08-16 found no wps_sfw_* / _wps_sfw_* key), so the read has not been exercised against a real record."
+        },
+        {
+          "code": "cadence-maps-fields-do-not-all-fit",
+          "severity": "warning",
+          "summary": "The cadence pair maps cleanly to the verified Wix home: wps_sfw_subscription_interval (day|week|month|year) -> product.subscriptionDetails.subscriptions[].frequency (DAY|WEEK|MONTH|YEAR) and wps_sfw_subscription_number -> .interval (stores/product fieldContract, live-verified 2026-07-26; capability claimed by stores/subscription-product, confirmed 2026-08-16). Subscription length/expiry, initial signup price, and free trial have no subscriptionDetails field - DECIDED 2026-08-16: reported loss, ledgered as fidelity_loss per record, NOT CMS-carried."
+        },
+        {
+          "code": "one-time-purchase-toggle-semantics",
+          "severity": "info",
+          "summary": "The plugin makes a product either a subscription or a one-time purchase per product (checkbox), while Wix models both on one product via subscriptionDetails.allowOneTimePurchases; a migrated subscription product should set allowOneTimePurchases=false unless the source sells both forms."
+        }
+      ]
+    },
+    {
+      "entity": "subscription-record",
+      "channel": "plugin-rest",
+      "route": "/wsp-route/v1/wsp-view-subscription",
+      "recordKeyField": "subscription_id",
+      "responseEnvelope": {
+        "itemsPath": "data"
+      },
+      "candidateTargetRefs": ["pricing-plans/plan-order"],
+      "pitfalls": [
+        {
+          "code": "pricing-plans-recreation-semantics",
+          "severity": "warning",
+          "summary": "CONFIRMED DIRECTION (accepted 2026-08-16): active recurring-subscription contracts are RECREATED as Pricing Plans memberships via Create Offline Order (POST /pricing-plans/v2/checkout/orders/offline - planId + memberId + startDate, paid:true for contracts already collected) - target pricing-plans/plan-order. The Stores-product linkage is severed by design: product_name survives only as plan title/description, an accepted trade. stores/product.subscriptionDetails still covers the product OFFER only. Recurring BILLING never carries over (payment tokens do not migrate) - collection restarts on Wix; members must exist first (memberId via crosswalk)."
+        },
+        {
+          "code": "plugin-secret-gated-route",
+          "severity": "warning",
+          "summary": "[VERIFIED LIVE 2026-08-16] the route is advertised in the REST index but returns 403 rest_forbidden to the admin Application Password; it accepts only the plugin's own consumer_secret query parameter, and only when the API toggle is enabled in the plugin settings (see credentials[]). Treat a 403 here as Blocked - recoverable (credential), not surface drift."
+        },
+        {
+          "code": "summary-projection-only",
+          "severity": "warning",
+          "summary": "[DOCUMENTED] the route returns a 10-field summary per subscription (subscription_id, parent_order_id, status, product_name, recurring_amount, interval_number, interval_type, user_name, next_payment_date, subscriptions_expiry_date - plugin source 2.0.1, package/rest-api/version1/class-subscriptions-for-woocommerce-api-process.php, read 2026-08-16). Fuller state (customer id vs display name, trial/signup detail, payment gateway, billing history) lives in the wps_subscriptions record's meta and is NOT exposed here; user_name is a display nicename, not a stable customer key - crosswalk via parent_order_id -> /wc/v3/orders customer instead."
+        },
+        {
+          "code": "unpaginated-full-dump",
+          "severity": "info",
+          "summary": "[DOCUMENTED] the callback queries with limit -1 / numberposts -1 and returns every subscription in one wrapped response ({code, status, data: [...]}, no X-WP-Total headers, no page/per_page args) - fine for sampling, but recordCount equals the full set and large stores pay the whole cost on the first GET."
+        }
+      ]
+    }
+  ],
+  "quirks": [
+    "STORAGE MODEL - (a) subscription product settings: unregistered postmeta on the product (no register_meta/show_in_rest anywhere in the plugin - [DOCUMENTED] 0 occurrences in source 2.0.1, read 2026-08-16), REST-visible only because WooCommerce surfaces non-internal postmeta in /wc/v3/products meta_data[]; (b) active subscription records: a WooCommerce custom ORDER TYPE 'wps_subscriptions' (wc_register_order_type in subscriptions-for-woocommerce.php, public:false, exclude_from_order_webhooks:true, status wc-wps_renewal; HPOS-aware - records live in WooCommerce's order tables when HPOS is on, in wp_posts otherwise) [DOCUMENTED source 2.0.1]. The type is NOT registered for REST: [VERIFIED LIVE 2026-08-16] wps_subscriptions is absent from the authed /wp/v2/types, and /wc/v3/orders serves shop_order only - so the plugin's own secret-gated route is the ONLY REST read for subscription records.",
+    "[VERIFIED LIVE 2026-08-16] with plugin 2.0.1 active: the REST index advertises namespace wsp-route/v1 with exactly one data route, /wsp-route/v1/wsp-view-subscription (GET, no args); note the namespace is 'wsp-route', not the 'wsfw-route' a reader might guess from the plugin's wps_sfw_* prefix.",
+    "The plugin is the former MakeWebBetter 'Subscriptions for WooCommerce'; mwb_-prefixed helpers survive in the 2.0.1 source. [NEEDS-VERIFICATION] whether long-lived source sites still carry legacy mwb_sfw_* postmeta alongside or instead of wps_sfw_* - if a site predates the WP Swings rename, check for mwb_sfw_* keys before concluding a product is not a subscription.",
+    "[VERIFIED LIVE 2026-08-16] no product was flagged _wps_sfw_product and no subscription records were reachable, so every read-shape claim above rests on the published 2.0.1 source rather than a live payload; re-verify against a store with real subscription data before promoting this profile's field list to a contract."
+  ]
+}

package/skills/wix-replatform/resources/rp-source-wordpress/plugins/tablepress.json

@@ -0,0 +1,55 @@
+{
+  "schemaVersion": 1,
+  "plugin": "tablepress",
+  "displayName": "TablePress",
+  "profileVersion": "2026-08",
+  "sourceOfTruth": "https://wordpress.org/plugins/tablepress/",
+  "distribution": "wordpress-org",
+  "capabilities": [
+    "content.data-tables"
+  ],
+  "detect": {
+    "pluginFileIds": [
+      "tablepress/tablepress.php"
+    ],
+    "assetPathSlugs": [
+      "tablepress"
+    ]
+  },
+  "entities": [
+    {
+      "entity": "table-definition",
+      "capability": "content.data-tables",
+      "channel": "db-only",
+      "candidateTargetRefs": [],
+      "pitfalls": [
+        {
+          "code": "shared-posts-table-requires-filter",
+          "severity": "warning",
+          "summary": "Tables are wp_posts rows (post_type=tablepress_table, public=false) with no dedicated table and no show_in_rest -- reading the posts table WITHOUT this entity's declared where-filter would return every post type on the site (products, pages, attachments, etc.), not just TablePress tables. sampleStructureRequest.where is mandatory here, not optional -- enforced by plugin-knowledge.js's SHARED_CORE_TABLES_REQUIRING_WHERE check."
+        },
+        {
+          "code": "table-data-is-json-blob",
+          "severity": "warning",
+          "summary": "post_content holds the whole table as a JSON blob (row/column array), not display-ready text -- must be parsed, not copied verbatim, before any target mapping can use individual cell values."
+        },
+        {
+          "code": "empty-on-real-test-site",
+          "severity": "info",
+          "summary": "VERIFIED LIVE 2026-08-29: a filtered query against the posts table (where post_type = tablepress_table) executes correctly and may return zero rows when the plugin is active but unused -- the mechanism is real and reachable; an empty result means there is nothing to migrate."
+        }
+      ],
+      "blocked": [
+        {
+          "kind": "structure-bridge-plugin",
+          "resolution": "wix-wp-plugin-v2 can read the shared posts table filtered to this plugin's post_type -- VERIFIED LIVE 2026-08-29: a filtered query (where post_type = tablepress_table) executes correctly and returns pagingMetadata.total (0 when no TablePress tables are configured). Reachability is confirmed; fulfillment wiring is deferred until a Wix target is researched and approved at the mapping review. The working filtered query, for reference once a target is approved: select ID/post_title/post_content/post_status/post_date where post_type=tablepress_table, orderBy ID asc.",
+          "declined": false
+        }
+      ]
+    }
+  ],
+  "quirks": [
+    "Registers custom post type tablepress_table (public=false): table JSON lives in post_content with post_mime_type application/json. Confirmed via the plugin's own source (model-post.php).",
+    "No native Wix target researched or approved yet -- do not assume a generic CMS collection is the right landing spot without that approval. Do not wire the table-definition entity's blocked[] fulfillment on your own judgment before that target decision is made."
+  ]
+}

package/skills/wix-replatform/resources/rp-source-wordpress/plugins/the-events-calendar.json

@@ -0,0 +1,160 @@
+{
+  "schemaVersion": 1,
+  "plugin": "the-events-calendar",
+  "displayName": "The Events Calendar",
+  "profileVersion": "2026-08",
+  "sourceOfTruth": "https://theeventscalendar.com/knowledgebase/introduction-to-the-events-calendar-rest-api/",
+  "distribution": "wordpress-org",
+  "capabilities": [
+    "content.events",
+    "content.event-categories",
+    "commerce.bookable-services"
+  ],
+  "classificationHeuristic": {
+    "decision": "event-vs-bookings-service",
+    "summary": "The Events Calendar's `event` entity can map to either Wix Events (events/event) or a Wix Bookings Service (bookings/service, type CLASS) — they are not interchangeable targets, and picking wrong loses real functionality (ticketing vs. per-attendee capacity/booking flow).",
+    "preferBookings": "Small-group, bookable workshops/classes/pop-ups: capped capacity implied by 'limited spots'/'booking required' language, a single or small recurring set of sessions, no ticket tiers, and priced (or free) per-attendee registration rather than a public RSVP/ticket sale.",
+    "preferEvents": "Large public ticketed or open-attendance happenings: galas, concerts, meetups, launches with no attendee cap, or anything the source models with ticket tiers/pricing rather than a single flat per-session price.",
+    "signals": [
+      "Description language: 'booking required', 'limited spots', 'sign up' -> Bookings. 'RSVP', 'doors open', ticket-tier pricing -> Events.",
+      "cost_details.values with a single flat value and no ticket 'tiers'/'types' concept -> Bookings-shaped pricing.",
+      "Recurring short sessions of the same class ('2 sessions') -> Bookings COURSE/CLASS, not a Wix Events recurring series.",
+      "The source plugin itself never distinguishes these — the heuristic is read off the CONTENT (title/description/cost shape), not a field the API exposes."
+    ],
+    "confirmWithHuman": "Always ambiguous-case: a human should confirm the classification before the first live write when signals conflict (e.g. a large recurring public series with per-session capacity language).",
+    "verifiedPrecedent": "Applied precedent, 2026-08-12: event records that were workshops/pop-ups with 'Limited spots, booking required' language and flat per-session pricing were classified Bookings Classes, not Wix Events."
+  },
+  "detect": {
+    "pluginFileIds": [
+      "the-events-calendar/the-events-calendar.php"
+    ],
+    "routes": [
+      "/tribe/events/v1/events"
+    ],
+    "restNamespaces": [
+      "tribe/events/v1",
+      "tec/v1"
+    ],
+    "restBases": [
+      "tribe_events",
+      "tribe_venue",
+      "tribe_organizer",
+      "tribe_events_cat"
+    ],
+    "assetPathSlugs": [
+      "the-events-calendar"
+    ]
+  },
+  "entities": [
+    {
+      "entity": "event",
+      "channel": "plugin-rest",
+      "route": "/tribe/events/v1/events",
+      "recordKeyField": "id",
+      "candidateTargetRefs": [
+        "events/event",
+        "bookings/service"
+      ],
+      "relations": [
+        {
+          "field": "venue",
+          "targetEntity": "venue",
+          "evidence": "tribe/events/v1 event payload embeds venue"
+        },
+        {
+          "field": "organizer",
+          "targetEntity": "organizer",
+          "evidence": "tribe/events/v1 event payload embeds organizer"
+        }
+      ],
+      "pitfalls": [
+        {
+          "code": "event-ticket-history-no-import-path",
+          "severity": "blocker",
+          "summary": "Wix has no import path for ticketed event order history; ticket sales cannot be migrated even once Events is native."
+        },
+        {
+          "code": "default-list-hides-events-without-date-filter",
+          "severity": "warning",
+          "summary": "GET /tribe/events/v1/events with no parameters can return total 0 while published events exist; always pass an explicit start_date filter (verified live 2026-08-10 on TEC 6.17.2: parameterless list returned 0, ?start_date=2026-01-01 returned all 3 published events)."
+        },
+        {
+          "code": "events-vs-bookings-classification-required",
+          "severity": "warning",
+          "summary": "This entity has TWO real Wix targets (events/event, bookings/service) that are not interchangeable — see the top-level `classificationHeuristic` field for the small-group-workshop-vs-public-happening heuristic and a human-confirmation requirement on ambiguous data. Do not default to events/event without checking it."
+        }
+      ]
+    },
+    {
+      "entity": "venue",
+      "channel": "plugin-rest",
+      "route": "/tribe/events/v1/venues",
+      "recordKeyField": "id",
+      "candidateTargetRefs": [],
+      "pitfalls": [
+        {
+          "code": "folds-into-event-record",
+          "severity": "info",
+          "summary": "Wix has no separate venue entity; this data folds into the event's location/organizer fields. Read it to enrich the event, not as its own collection."
+        }
+      ]
+    },
+    {
+      "entity": "organizer",
+      "channel": "plugin-rest",
+      "route": "/tribe/events/v1/organizers",
+      "recordKeyField": "id",
+      "candidateTargetRefs": [],
+      "pitfalls": [
+        {
+          "code": "folds-into-event-record",
+          "severity": "info",
+          "summary": "Wix has no separate organizer entity; this data folds into the event's location/organizer fields. Read it to enrich the event, not as its own collection."
+        }
+      ]
+    },
+    {
+      "entity": "event-category",
+      "channel": "core-cpt",
+      "route": "/wp/v2/tribe_events_cat",
+      "recordKeyField": "id",
+      "hierarchical": true,
+      "candidateTargetRefs": [
+        "events/category"
+      ],
+      "pitfalls": [
+        {
+          "code": "flat-wix-categories",
+          "severity": "warning",
+          "summary": "Source event categories are hierarchical; Wix Events categories are flat — flatten requires a faithfulness-ledger entry."
+        }
+      ]
+    },
+    {
+      "entity": "event-cpt",
+      "channel": "core-cpt",
+      "route": "/wp/v2/tribe_events",
+      "recordKeyField": "id",
+      "candidateTargetRefs": [
+        "events/event"
+      ],
+      "pitfalls": [
+        {
+          "code": "prefer-tribe-rest-over-cpt",
+          "severity": "info",
+          "summary": "When /tribe/events/v1/events is available prefer it: the CPT route omits venue/organizer/schedule fields the plugin API returns."
+        }
+      ]
+    }
+  ],
+  "excludeRoutes": [
+    {
+      "route": "/tribe/events/v1/doc",
+      "reason": "Swagger self-documentation endpoint, not durable data"
+    }
+  ],
+  "quirks": [
+    "The plugin publishes a Swagger 2.0 document at /wp-json/tribe/events/v1/doc that can be read to confirm the exact endpoint set on a given site.",
+    "Recurring events expand into multiple records; deduplicate by parent event before mapping."
+  ]
+}