@wix/agent-skills 1.33.1 → 1.35.0

package/skills/wix-replatform/resources/rp-target-wix/domains/ecom/entities/shipping-option.json

@@ -0,0 +1,98 @@
+{
+  "schemaVersion": 1,
+  "domain": "ecom",
+  "entity": "shipping-option",
+  "displayName": "Wix Shipping Option",
+  "capability": "commerce.shipping-rate",
+  "target": {
+    "classification": "native",
+    "nativeEntity": "ShippingOption",
+    "verifiedFqdn": null,
+    "idPolicy": "server-assigned",
+    "crosswalkRequired": true
+  },
+  "dependsOn": [
+    "ecom/delivery-profile"
+  ],
+  "sourceAliases": [
+    {
+      "sourceSystem": "woocommerce",
+      "sourceEntity": "shipping-zone.method",
+      "routes": [
+        "/wc/v3/shipping/zones/{id}/methods"
+      ],
+      "confidence": "high",
+      "note": "Same source data shipping-build.js's classifyMethod already classifies for delivery-profile.json's deliveryCarrier.backupRate -- but ONLY a kind:'carrier' classification produces BOTH a DeliveryCarrier.backupRate AND a ShippingOption from the same classified method; for that kind they are not alternatives. The other kinds produce no shipping option at all: 'pickup' becomes a PickupLocation (see ecom/pickup-location), 'threshold' folds onto a sibling paid option as a conditional rate, and 'coupon-domain' produces nothing here."
+    }
+  ],
+  "preferredWrite": {
+    "surface": "Shipping Options",
+    "endpoint": "POST /ecom/v1/shipping-options",
+    "writerId": "createShippingOptionVerified",
+    "verification": "verified-live",
+    "importSafe": true,
+    "bulk": false,
+    "decision": "Verified live: creating a ShippingOption that matches a region's DeliveryCarrier.backupRate populates the dashboard rate table where the carrier write alone does not. The write counts only when its read-back matches (createShippingOptionVerified); createShippingOption stays as the raw call."
+  },
+  "reliability": {
+    "status": "reliable",
+    "flags": []
+  },
+  "pitfalls": [
+    {
+      "code": "not-derived-from-backup-rate-a-separate-required-write",
+      "severity": "blocker",
+      "summary": "DeliveryCarrier.backupRate does not create a ShippingOption and does not clear Wix's missing-rates dashboard warning. Live verification showed that a carrier-only region can write and read back successfully while remaining non-functional at checkout. Always create a matching ShippingOption for every imported DeliveryRegion from the same classified method used for DeliveryCarrier.backupRate; see shipping-build.js's buildShippingOptionInput."
+    },
+    {
+      "code": "delivery-region-ids-plural-is-the-live-field",
+      "severity": "warning",
+      "summary": "CORRECTED. An earlier reading of this API said to use the singular `deliveryRegionId` and treat the plural as decoration; that is inverted. Per the service contract, the singular `deliveryRegionId` is DEPRECATED and replaced by `deliveryRegionIds`, with a removal target already in the past -- the plural is the live field, which is also why the singular-only observation showed an empty plural array on read-back. Write BOTH: the plural is what is honoured going forward, the singular keeps older reads and tooling working until it is actually removed. The original observation was real; the conclusion drawn from a doc page that predated the deprecation was not."
+    },
+    {
+      "code": "estimated-delivery-time-is-the-field-not-the-translatable-name",
+      "severity": "blocker",
+      "summary": "CORRECTED; the earlier rule had the two names exactly reversed. The request field is `estimatedDeliveryTime` (proto field 12, `estimated_delivery_time`, max 500 characters; wix-private/ecom shipping_option.proto at ed73ff24). `estimate_delivery_time` is only the `translatable` annotation's `name` -- a key in the translation system, not something a request can set -- which is why it looks like a second spelling. Wix accepts the misspelled `estimateDeliveryTime` in a create body with a 200 and silently drops it, so every option created with it read back with no delivery time. Live 2026-10-08: POST with `estimateDeliveryTime` returned 200 and GET showed no estimate; PATCH with `{shippingOption:{id, revision, estimatedDeliveryTime}}` stored it and it read back. shipping-build.js's buildShippingOptionInput emits only `estimatedDeliveryTime`, throws above 500 characters (never truncates), and has no default; createShippingOptionVerified reads every create back and repairs only a blank estimate with one estimate-only PATCH."
+    },
+    {
+      "code": "rates-support-conditions-and-the-lowest-valid-one-wins",
+      "severity": "warning",
+      "summary": "`rates[]` is the ConditionalRates type: each entry is {conditions[0..10], amount (decimal string), multiplyByQuantity}, and each Condition is {type: BY_TOTAL_WEIGHT|BY_TOTAL_PRICE|BY_TOTAL_QUANTITY, value, operator: EQ|GT|GTE|LT|LTE}. Conditions AND together; an empty conditions[] means always-applies. The runtime rule, verbatim from the service contract: 'at runtime for a given shipment input, up to one rate (price) should be returned in an option. If more than one rate is valid then we return the lowest one.' A source minimum-order free-shipping threshold is therefore fully expressible and is NOT a gap. What the contract does NOT settle is whether BY_TOTAL_PRICE is measured before or after cart discounts -- WooCommerce has an explicit ignore_discounts setting for exactly this, so the two can disagree. Ship the threshold as written, flag it, confirm at the first live checkout, and never report such a rate as verified until then."
+    },
+    {
+      "code": "explicit-two-band-partition-breaks-the-dashboard-editor",
+      "severity": "blocker",
+      "summary": "LIVE-VERIFIED 2026-09-16: a paid-flat-rate-plus-threshold fold has TWO API-valid encodings, and only one of them is dashboard-editable. Writing it as an explicit two-way partition -- one rate LT the threshold at the paid amount, one rate GTE the threshold at 0 (shipping-build.js's priceThresholdRates) -- is accepted by Create Shipping Option (200, correct read-back, verifyShippingEconomics reports zero violations) but the Wix dashboard's own rate editor renders it as 'Rate by price' mode with invalid, unfillable 'From'/'Up to' boundary fields -- a merchant opening this rate sees validation errors on a rate that works fine at checkout. LEANING ON the service's own lowest-wins tiebreak instead -- one UNCONDITIONAL rate at the paid amount plus one separate GTE-threshold rate at 0 (unconditionalRate + freeAboveThresholdRates, both already in shipping-build.js) -- renders correctly as the dashboard's simpler 'Flat rate' mode with its 'Offer free shipping when customers purchase a certain amount' checkbox, confirmed live against the actual dashboard editor. resolveZoneMethods now builds this combination by default; do not switch it back to the explicit-partition shape without re-verifying the dashboard editor first, and do not reach for priceThresholdRates directly for anything a merchant will open in the dashboard."
+    },
+    {
+      "code": "one-option-per-buyer-choice-not-per-source-method",
+      "severity": "blocker",
+      "summary": "CORRECTED, and the correction matters more than the original. An earlier version of this rule said each carrier-classified method becomes its own ShippingOption and to never collapse several methods into one. That produces a store where the same delivery is listed two or three times, because a source zone lists every shipping BEHAVIOUR as its own method row -- a minimum-order threshold and a coupon-gated free shipping are both rows, and neither is something a buyer picks. Observed live: one source zone with five methods produced four options, two of them byte-identical unconditional zeroes. Resolve the zone's methods to buyer-facing choices first (shipping-build.js's resolveZoneMethods: fold thresholds onto paid options, drop coupon-gated rows, route pickup to its own entity, then collapse identical survivors) and create one option per surviving choice. Every collapse is reported as a resolved source defect -- a silent collapse is indistinguishable from never having noticed."
+    }
+  ],
+  "mappingGuidance": [
+    "For every WooCommerce shipping-zone method that shipping-build.js's classifyMethod resolves to kind:'carrier', create BOTH a DeliveryCarrier (backupRate, on the delivery profile) AND a ShippingOption (rates[], standalone resource keyed by deliveryRegionId) from the same classified result -- shipping-build.js's buildDeliveryCarrierInput and buildShippingOptionInput. Creating only the former leaves the region looking fully configured via the API (and even via a plain Query Delivery Profiles read-back) while Wix's own checkout and dashboard still treat it as missing rates.",
+    "amount is a plain decimal string ('8', '0'), same convention as backupRate.amount -- no separate currency/format handling needed.",
+    "A source minimum-order free-shipping threshold is CARRIED, not dropped: write the paid option with two rates -- an UNCONDITIONAL rate at the source price plus a separate GTE band at 0 on BY_TOTAL_PRICE at the source's minimum (shipping-build.js's unconditionalRate + freeAboveThresholdRates), relying on the service's own lowest-valid-rate tiebreak. Do NOT use the explicit LT/GTE two-way partition (priceThresholdRates) for this -- see the explicit-two-band-partition-breaks-the-dashboard-editor pitfall below: it is schema-valid but renders as a broken, unfillable 'Rate by price' mode in the Wix dashboard's own rate editor. priceThresholdRates still exists and is schema-valid; it is discouraged specifically for anything a merchant will open in the dashboard, which is the normal case here.",
+    "An unconditional 0-amount rate is correct in exactly one case: a source free-shipping method with NO condition attached at all. Anywhere else it means a condition was dropped, which does not half-migrate the rule -- it inverts it, makes every paid option unreachable, and costs the merchant its shipping revenue. shipping-build.js's verifyShippingEconomics fails a region that has an unconditional free option alongside a paid one, for exactly this reason.",
+    "Delivery estimate: resolve it per option with shipping-build.js's resolveDeliveryEstimate -- a merchant-confirmed `shipping-delivery-estimate:<zoneId>` decision (`source: \"user\"` only) wins, then a delivery time the source states, then the reviewed '5-7 business days' default in the DESTINATION site's language (DEFAULT_ESTIMATE_BY_LANGUAGE; Hebrew gets '5–7 ימי עסקים'). A language with no reviewed row gets NO estimate and a `shipping-estimate-missing` merchant item; English is never written on a non-English site. Every default is flagged `shipping-estimate-default` for the merchant to confirm. A non-empty estimate the migration did not write is the merchant's and is never overwritten. Options created by earlier (pre-fix) migrations are reported (`shipping-estimate-legacy-blank`), never edited."
+  ],
+  "setupRequirements": [],
+  "objectPageException": "The standard API reference menu (dev.wix.com/docs/api-reference/business-solutions/e-commerce/shipping-delivery, checked 2026-08-15) has exactly one subsection, 'Delivery Profiles' -- no 'Shipping Options' subsection and no dedicated ShippingOption '…-object' page exist anywhere in that tree. The entire resource is undocumented there; the only place it's described at all is the 'Shipping: API Reference' skills article (a distilled, AI-agent-oriented reference in a completely separate doc tree, business-solutions/e-commerce/skills/) plus its sibling 'Fix Shipping Coverage Gaps' article. The full field shape is sourced from those two pages' request/response examples instead.",
+  "evidence": [
+    {
+      "type": "wix-docs",
+      "url": "https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/shipping-fix-coverage-gaps",
+      "note": "the article that surfaced ShippingOption's existence and its role in clearing a checkout coverage gap; not linked from or mentioned on any shipping-delivery/delivery-profiles/* page"
+    },
+    {
+      "type": "wix-docs",
+      "url": "https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/shipping-api-reference",
+      "note": "full Query/Create/Get/Update/Delete Shipping Option + Add/Remove Delivery Region (on a shipping option) schema and the singular-vs-plural deliveryRegionId gotcha, confirmed 2026-08-15"
+    },
+    {
+      "type": "live-verification",
+      "path": "anonymized-live-verification"
+    }
+  ]
+}

package/skills/wix-replatform/resources/rp-target-wix/domains/ecom/entities/wishlist-item.json

@@ -0,0 +1,86 @@
+{
+  "schemaVersion": 1,
+  "domain": "ecom",
+  "entity": "wishlist-item",
+  "displayName": "Wishlist Item",
+  "capability": "commerce.wishlists",
+  "target": {
+    "classification": "native",
+    "nativeEntity": "Wishlist",
+    "verifiedFqdn": "wix.platform.v1.wishlist",
+    "idPolicy": "server-assigned",
+    "crosswalkRequired": true
+  },
+  "dependsOn": ["stores/product"],
+  "blockedSourceDependencies": [
+    {
+      "sourceEntityRef": "plugin.ti-woocommerce-wishlist.wishlist-definition",
+      "degradedField": "items",
+      "pitfallCode": "no-backend-write-path-for-migration",
+      "degradation": "warning"
+    },
+    {
+      "sourceEntityRef": "plugin.ti-woocommerce-wishlist.wishlist-item",
+      "degradedField": "items",
+      "pitfallCode": "no-backend-write-path-for-migration",
+      "degradation": "warning"
+    }
+  ],
+  "objectPageException": "This API is internal-only (proto exposure: INTERNAL for its mutating RPCs, ALPHA maturity) -- it has no public dev.wix.com docs object page. Confirmed by two ranked SearchWixRESTDocumentation queries and a full raw API-spec index substring scan for 'wishlist', all returning zero results; the authoritative source is the internal proto itself (see evidence[]).",
+  "sourceAliases": [
+    {
+      "sourceSystem": "wordpress",
+      "sourceEntity": "ti_woocommerce_wishlist",
+      "routes": [
+        "tinvwl_lists (structure-bridge-plugin)",
+        "tinvwl_items (structure-bridge-plugin)",
+        "/wc/v3/wishlist/get_by_user/{user_id} (plugin-rest-child, per-member chain)"
+      ],
+      "confidence": "high"
+    }
+  ],
+  "preferredWrite": {
+    "surface": "com.wixpress.wishlist.Wishlist (internal proto, package com.wixpress.wishlist)",
+    "endpoint": "POST /v1/wishlists/my",
+    "writerId": null,
+    "verification": "unverified",
+    "importSafe": false,
+    "bulk": false
+  },
+  "fallbacks": [
+    {
+      "classification": "cms",
+      "when": "Always, for a bulk migration import. The native AddToWishlist/RemoveFromWishlist RPCs only operate on 'the default wishlist by context's member' (member-session-scoped, exposure: INTERNAL) -- there is no service-account/backend RPC to write items to an arbitrary existing member's wishlist on their behalf. GetWishlistById/GetWishlists accept a site-level WISHLIST.MANAGE-SITE-WISHLISTS permission but are read-only. A migration script has no member session for historical WooCommerce customers who have never logged into the new Wix site, so the native write path is unusable for import regardless of Alpha status."
+    }
+  ],
+  "reliability": {
+    "status": "unreliable",
+    "flags": ["IMPORT_UNRELIABLE"]
+  },
+  "pitfalls": [
+    {
+      "code": "no-backend-write-path-for-migration",
+      "severity": "blocker",
+      "summary": "Verified against the authoritative internal proto: the fqdn is wix.platform.v1.wishlist (service com.wixpress.wishlist.Wishlist). Its three mutating RPCs (GetWishlist/AddToWishlist/RemoveFromWishlist) are ALPHA maturity, exposure: INTERNAL, and scoped to 'the default wishlist by context's member' -- the caller's own session, not an arbitrary member named by a backend script. The only RPCs open to a site-level manage permission (GetWishlistById, GetWishlists) are read-only. There is no proto-level path for a migration script to write wishlist items on behalf of pre-existing customers who have never authenticated to the new site."
+    },
+    {
+      "code": "native-target-exists-do-not-conclude-requires-development",
+      "severity": "info",
+      "summary": "This is NOT a 'Wix has no surface' gap -- a real native Wishlist entity and proto exist, confirmed live from source. The limitation is specifically the migration-import use case (no backend bulk-write RPC), not an absent feature. Do not record this capability in requires-development.json; it is a documented reliability/fallback case (see fallbacks[] and reliability.flags above), revisitable if Wix adds a service-account write path or a different integration surface (e.g. Velo backend code running with elevated permissions, not yet investigated)."
+    }
+  ],
+  "mappingGuidance": [
+    "Land wishlist data in a Wix CMS collection (cms/collection) for migration imports today -- see fallbacks[]. Revisit this entity if a backend/service-account write RPC is ever added to the Wishlist API."
+  ],
+  "setupRequirements": [
+    "Wix Data (CMS) app, for the fallback collection",
+    "Wix Stores, so wishlist items can reference real migrated product ids"
+  ],
+  "evidence": [
+    {
+      "type": "source-proto",
+      "path": "wix-private/monorepo@391685f038538afc4a84ac7f9fa6e38a3642783a:comp/ecom/platform/wishlist/wishlist-api/src/main/proto/com/wixpress/wishlist/wishlist.proto",
+      "note": "Authoritative internal proto for com.wixpress.wishlist.Wishlist."
+    }
+  ]
+}

package/skills/wix-replatform/resources/rp-target-wix/domains/events/docs-survey.json

@@ -0,0 +1,128 @@
+{
+  "schemaVersion": 1,
+  "domain": "events",
+  "fetchedAt": "2026-08-11",
+  "roots": [
+    "api-reference/business-solutions/events"
+  ],
+  "surfaces": [
+    {
+      "id": "api-reference/business-solutions/events/event-management/categories",
+      "title": "Categories",
+      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/categories",
+      "group": "Event Management",
+      "verdict": "claimed",
+      "refs": [
+        "events/category"
+      ],
+      "reviewedOn": "2026-08-11"
+    },
+    {
+      "id": "api-reference/business-solutions/events/event-management/events-settings",
+      "title": "Events Settings",
+      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/events-settings",
+      "group": "Event Management",
+      "verdict": "not-relevant",
+      "reason": "Site-level settings singleton (get/update only, no create); app configuration, not migratable records. Revisit only if a setup-config entity for Events defaults is ever needed.",
+      "reviewedOn": "2026-08-11"
+    },
+    {
+      "id": "api-reference/business-solutions/events/event-management/events-v3",
+      "title": "Events V3",
+      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/events-v3",
+      "group": "Event Management",
+      "verdict": "claimed",
+      "refs": [
+        "events/event"
+      ],
+      "reviewedOn": "2026-08-11"
+    },
+    {
+      "id": "api-reference/business-solutions/events/event-management/form",
+      "title": "Form",
+      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/form",
+      "group": "Event Management",
+      "verdict": "claimed",
+      "reviewedOn": "2026-08-11",
+      "refs": [
+        "events/registration-form"
+      ]
+    },
+    {
+      "id": "api-reference/business-solutions/events/event-management/policies-v2",
+      "title": "Policies V2",
+      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/policies-v2",
+      "group": "Event Management",
+      "verdict": "not-relevant",
+      "reason": "Checkout policy text attached to events (full CRUD exists), but no observed WP event source models policies as data. Revisit if a source carries per-event terms/refund policies.",
+      "reviewedOn": "2026-08-11"
+    },
+    {
+      "id": "api-reference/business-solutions/events/event-management/schedule-items",
+      "title": "Schedule Items",
+      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/schedule-items",
+      "group": "Event Management",
+      "verdict": "not-relevant",
+      "reason": "Multi-session agenda model (full CRUD exists), but observed WP event sources (TEC) model a single start/end carried on events/event. Revisit if a conference-schedule source capability appears.",
+      "reviewedOn": "2026-08-11"
+    },
+    {
+      "id": "api-reference/business-solutions/events/event-management/staff-members",
+      "title": "Staff Members",
+      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/staff-members",
+      "group": "Event Management",
+      "verdict": "not-relevant",
+      "reason": "Event staff records (full CRUD exists), but observed WP event sources model organizers as event fields, not standalone staff. Revisit if a source carries a staff/organizer directory worth importing.",
+      "reviewedOn": "2026-08-11"
+    },
+    {
+      "id": "api-reference/business-solutions/events/event-management/ticket-definitions-v3",
+      "title": "Ticket Definitions V3",
+      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/ticket-definitions-v3",
+      "group": "Event Management",
+      "verdict": "claimed",
+      "reviewedOn": "2026-08-11",
+      "refs": [
+        "events/ticket-definition"
+      ]
+    },
+    {
+      "id": "api-reference/business-solutions/events/registration/event-guests",
+      "title": "Event Guests",
+      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/registration/event-guests",
+      "group": "Registration",
+      "verdict": "not-importable",
+      "reason": "Read-only derived records (query + webhooks, no write API); guest rows are produced by RSVP/ticket-order writes, so imports land there, never here.",
+      "reviewedOn": "2026-08-11"
+    },
+    {
+      "id": "api-reference/business-solutions/events/registration/rsvp-v2",
+      "title": "RSVP V2",
+      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/registration/rsvp-v2",
+      "group": "Registration",
+      "verdict": "claimed",
+      "reviewedOn": "2026-08-11",
+      "refs": [
+        "events/rsvp"
+      ]
+    },
+    {
+      "id": "api-reference/business-solutions/events/registration/ticketing",
+      "title": "Ticketing",
+      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/registration/ticketing",
+      "group": "Registration",
+      "verdict": "not-importable",
+      "reason": "Ticket orders/reservations are only created through the live checkout flow — the domain's ticket-order-history-not-importable blocker. Past ticket sales cannot be migrated.",
+      "reviewedOn": "2026-08-11"
+    },
+    {
+      "id": "api-reference/business-solutions/events/skills",
+      "title": "Skills",
+      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/skills",
+      "group": null,
+      "verdict": "not-relevant",
+      "reason": "AI-skill documentation page (agent walkthrough of Create Event), not a data surface.",
+      "reviewedOn": "2026-08-11"
+    }
+  ]
+}

package/skills/wix-replatform/resources/rp-target-wix/domains/events/domain.json

@@ -0,0 +1,38 @@
+{
+  "schemaVersion": 1,
+  "domain": "events",
+  "dependsOnRequired": true,
+  "displayName": "Wix Events",
+  "ownerHint": "Events, registration, RSVP, and ticketing domain owners",
+  "wixAppsRequired": [
+    "Wix Events"
+  ],
+  "docsRoots": [
+    "api-reference/business-solutions/events"
+  ],
+  "defaultImportOrder": [
+    "category",
+    "event",
+    "registration-form",
+    "ticket-definition",
+    "rsvp"
+  ],
+  "sharedPitfalls": [
+    {
+      "code": "ticket-order-history-not-importable",
+      "severity": "blocker",
+      "summary": "Ticketed registration history has no import path: ticket orders are only created through the live checkout flow. Past ticket sales cannot be migrated even though the events themselves can."
+    },
+    {
+      "code": "registration-notifications-default-on",
+      "severity": "warning",
+      "summary": "Registration side effects are on by default across this domain. RSVP creation sends a confirmation email unless disableNotifications is set."
+    }
+  ],
+  "evidence": [
+    {
+      "type": "wix-docs",
+      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/events-v3/create-event"
+    }
+  ]
+}

package/skills/wix-replatform/resources/rp-target-wix/domains/events/entities/category.json

@@ -0,0 +1,73 @@
+{
+  "schemaVersion": 1,
+  "domain": "events",
+  "entity": "category",
+  "displayName": "Events Category",
+  "capability": "content.event-categories",
+  "target": {
+    "classification": "native",
+    "nativeEntity": "Wix Events Category",
+    "verifiedFqdn": "wix.events.v1.category",
+    "idPolicy": "server-assigned",
+    "crosswalkRequired": true
+  },
+  "dependsOn": [],
+  "sourceAliases": [
+    {
+      "sourceSystem": "wordpress",
+      "sourceEntity": "tribe_events_cat",
+      "routes": [
+        "/wp/v2/tribe_events_cat"
+      ],
+      "confidence": "high"
+    }
+  ],
+  "preferredWrite": {
+    "surface": "Events Categories",
+    "endpoint": "POST /events/v1/categories",
+    "writerId": null,
+    "verification": "verified-live",
+    "importSafe": true,
+    "bulk": false
+  },
+  "fallbacks": [
+    {
+      "classification": "cms",
+      "when": "Only if category metadata beyond name/assignment must survive (Wix category carries name + assigned events)."
+    }
+  ],
+  "reliability": {
+    "status": "unknown",
+    "flags": []
+  },
+  "mappingGuidance": [
+    "Create categories first, then assign events to them by ID — assignment happens on the category, not the event.",
+    "Wix Events categories are flat: flatten hierarchical source taxonomies and record the faithfulness-ledger entry."
+  ],
+  "setupRequirements": [
+    "Wix Events app"
+  ],
+  "pitfalls": [
+    {
+      "code": "flat-categories",
+      "severity": "warning",
+      "summary": "Wix Events categories are flat; a hierarchical source event taxonomy (tribe_events_cat is hierarchical) flattens on import — faithfulness-ledger entry required."
+    }
+  ],
+  "notes": "Event categories have a native Categories API (dev.wix.com Events > Event Management > Categories); do not map them to CMS. Docs-verified only; exercise live before confirming.",
+  "evidence": [
+    {
+      "type": "wix-docs",
+      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/categories/category-object"
+    },
+    {
+      "type": "review-decision",
+      "path": "anonymized-live-verification"
+    },
+    {
+      "type": "live-run",
+      "path": "anonymized-live-verification",
+      "note": "Verified live: create + query-back readback, safe mode on — 3/3 categories created via POST /events/v1/categories, server IDs crosswalked; assignment-to-events not exercised (events stayed drafts)"
+    }
+  ]
+}

package/skills/wix-replatform/resources/rp-target-wix/domains/events/entities/event.json

@@ -0,0 +1,107 @@
+{
+  "schemaVersion": 1,
+  "domain": "events",
+  "entity": "event",
+  "displayName": "Event",
+  "capability": "content.events",
+  "target": {
+    "classification": "native",
+    "nativeEntity": "Event",
+    "verifiedFqdn": null,
+    "idPolicy": "server-assigned",
+    "crosswalkRequired": true
+  },
+  "dependsOn": [
+    "events/category",
+    "media/media-file"
+  ],
+  "sourceAliases": [
+    {
+      "sourceSystem": "wordpress",
+      "sourceEntity": "event",
+      "sourcePlugin": "the-events-calendar",
+      "routes": [
+        "/tribe/events/v1/events",
+        "/wp/v2/tribe_events"
+      ],
+      "confidence": "high"
+    },
+    {
+      "sourceSystem": "wix",
+      "sourceEntity": "event",
+      "routes": [
+        "Events V3"
+      ],
+      "confidence": "high"
+    }
+  ],
+  "preferredWrite": {
+    "surface": "Events V3",
+    "endpoint": "POST /events/v3/events",
+    "writerId": null,
+    "verification": "verified-live",
+    "importSafe": true,
+    "bulk": false
+  },
+  "fallbacks": [
+    {
+      "classification": "cms",
+      "when": "Only for source-only event metadata, or for recurring-series rules the Wix schedule cannot express."
+    }
+  ],
+  "reliability": {
+    "status": "partially-reliable",
+    "flags": []
+  },
+  "pitfalls": [
+    {
+      "code": "past-dates-unverified",
+      "severity": "warning",
+      "summary": "Backdating is not documented either way. Historical events are the common migration case, so confirm a past startDate is accepted before promising event history; if rejected, past events fall back to CMS."
+    },
+    {
+      "code": "daily-guest-summary-on-create",
+      "severity": "warning",
+      "summary": "A created event is automatically set up to email daily summaries of new guests to the business address, with no documented way to disable it. Creating past events as drafts is the likely mitigation but is unverified."
+    },
+    {
+      "code": "required-location-and-schedule",
+      "severity": "warning",
+      "summary": "title, location.name, dateAndTimeSettings and registration.initialType are all required. A source event with no venue needs an explicit placeholder rather than an omitted field."
+    },
+    {
+      "code": "rsvp-and-tickets-are-separate-work",
+      "severity": "blocker",
+      "summary": "Creating the event does not carry its attendees. RSVPs need a separate import with disableNotifications set; ticketed orders have no import path at all."
+    },
+    "Ordering `category` before `event` is necessary but NOT sufficient: attaching an event to a category is its own call, POST /events/v1/categories/{categoryId}/events, needing both ids. Creating the category first and the event second leaves an empty category and an uncategorised event unless a third step runs after both. `dependsOn` sequences creation; it cannot express a relationship write. Any plan that maps source categories must emit that assignment step explicitly."
+  ],
+  "mappingGuidance": [
+    "Create with draft: true for past or unpublished source events, then publish only what should be publicly listed.",
+    "Fold source venue and organizer records into the event's location and organizer fields — Wix does not model them as separate importable entities.",
+    "Deduplicate recurring-series expansions by parent event before writing, or one source series becomes many Wix events."
+  ],
+  "setupRequirements": [
+    "Wix Events app",
+    "SCOPE.DC-EVENTS.MANAGE-EVENTS"
+  ],
+  "evidence": [
+    {
+      "type": "wix-docs",
+      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/events-v3/event-object"
+    },
+    {
+      "type": "wix-docs",
+      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/events-v3/create-event"
+    },
+    {
+      "type": "wix-docs-search",
+      "path": "searched: event, calendar, RSVP, ticketing across business-solutions/events (2026-08-02)"
+    },
+    {
+      "type": "live-run",
+      "path": "anonymized-live-verification",
+      "note": "Verified live: create + query-back readback, safe mode on — events created as drafts and read back by crosswalk ID (initial payload-shape 400s fixed in-run)"
+    }
+  ]
+}

package/skills/wix-replatform/resources/rp-target-wix/domains/events/entities/registration-form.json

@@ -0,0 +1,89 @@
+{
+  "schemaVersion": 1,
+  "domain": "events",
+  "entity": "registration-form",
+  "displayName": "Event Registration Form",
+  "capability": "content.event-registration-form",
+  "target": {
+    "classification": "setup-config",
+    "nativeEntity": "Events Registration Form",
+    "verifiedFqdn": null,
+    "idPolicy": "not-applicable",
+    "crosswalkRequired": false
+  },
+  "sourceAliases": [],
+  "dependsOn": ["events/event"],
+  "preferredWrite": {
+    "surface": "Events Form (V1 form control API on a V3 event)",
+    "endpoint": "POST /events/v1/events/{eventId}/form/control",
+    "writerId": null,
+    "verification": "verified-live",
+    "importSafe": true,
+    "bulk": false,
+    "decision": "There is no form create. Add one control per call with a single-key oneof body — { text | phone | address | date | additionalGuests | dropdown | checkbox | radioButton: { … } } — against the event's existing form. Response returns the generated control id plus the whole modified form. Read back with GET /events/v3/events/{eventId}?fields=FORM. Verified live on a DRAFT event."
+  },
+  "reliability": {
+    "status": "reliable",
+    "flags": []
+  },
+  "pitfalls": [
+    {
+      "code": "per-event-config-not-records",
+      "severity": "warning",
+      "summary": "The form is per-event configuration (an ordered list of controls), not standalone records: there is no create — controls are added/updated on the event's existing form. Historical submissions do not live here; they arrive as RSVP/order data."
+    },
+    {
+      "code": "pinned-required-controls",
+      "severity": "warning",
+      "summary": "VERIFIED LIVE 2026-08-16: a freshly created event already has system controls `name` (type NAME, orderIndex 0) and `email` (type INPUT, orderIndex 1), both system:true and mandatory; added controls append from orderIndex 2. Source forms that made name/email optional or reordered them cannot be reproduced — faithfulness-ledger entry."
+    },
+    {
+      "code": "control-ids-are-not-guids",
+      "severity": "warning",
+      "summary": "CORRECTED 2026-08-16 (live): the docs call the returned control id a \"generated unique input control GUID\", but the first added custom control came back with id `custom` and the second with `custom-a5976fed804ff46f`. Treat the id as an opaque server string, capture it from the AddControl response, and never construct or assume it — RSVP form.inputValues are addressed by input NAME anyway."
+    },
+    {
+      "code": "add-control-publishes-the-form",
+      "severity": "warning",
+      "summary": "Per the docs, applying a control change triggers form publishing. Configure the form inside the notification-mute window and before the event itself is published, the way the 2026-08-16 probe did (draft event, muted site)."
+    },
+    {
+      "code": "control-body-is-a-single-key-oneof",
+      "severity": "warning",
+      "summary": "The AddControl body is the control payload itself at top level — no wrapper object, exactly one of phone/address/date/additionalGuests/dropdown/checkbox/text/radioButton. dropdown and radioButton need minItems 2 options; checkbox needs at least 1; unsupported source input types fall back to a text control with a ledger entry."
+    }
+  ],
+  "mappingGuidance": [
+    "Dependencies: events/event is required because each Add Control call addresses the created event's form by eventId.",
+    "Configure after the event is created (draft is fine): replay source custom registration fields (e.g. Event Tickets attendee fields) as one Add Control call each, in source order — controls append in call order.",
+    "Do not re-add name/email; they are system controls on every event. Only their labels can change.",
+    "Before importing RSVPs, read the finished form back with GET /events/v3/events/{eventId}?fields=FORM and build rsvp.form.inputValues from controls[].inputs[].name — unrecognized input names, missing mandatory values, or values outside predefined options fail the RSVP with INVALID_FORM_RESPONSE."
+  ],
+  "setupRequirements": [
+    "Wix Events app",
+    "SCOPE.DC-EVENTS.MANAGE-EVENTS"
+  ],
+  "evidence": [
+    {
+      "type": "wix-docs",
+      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/form/form-object",
+      "note": "object page: ordered controls with nested inputs; name/email pinned required"
+    },
+    {
+      "type": "wix-docs",
+      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/form/add-control",
+      "note": "POST /events/v1/events/{eventId}/form/control; body is a single-key oneof"
+    },
+    {
+      "type": "live-run",
+      "path": "anonymized-live-verification",
+      "note": "The docs survey identified the event registration-form surface."
+    },
+    {
+      "type": "live-run",
+      "path": "anonymized-live-verification",
+      "note": "Verified live: text and dropdown controls can be added to a draft event form and read back with GET /events/v3/events/{id}?fields=FORM. Probe records were deleted after verification."
+    }
+  ],
+  "notes": "Authored 2026-08-11 from the docs-survey gap (Form). Classified setup-config: per-event form layout applied via Add/Update Control after event creation, no importable records of its own. Promoted to verified-live 2026-08-16; the probe filled in the previously null endpoint (Events V1 form path on a V3 event) and corrected the docs' GUID claim for control ids."
+}