@wix/agent-skills 1.35.1 → 1.36.1

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

@@ -1,107 +0,0 @@
-{
-  "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

@@ -1,89 +0,0 @@
-{
-  "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."
-}

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

@@ -1,118 +0,0 @@
-{
-  "schemaVersion": 1,
-  "domain": "events",
-  "entity": "rsvp",
-  "displayName": "Event RSVP",
-  "capability": "content.event-rsvps",
-  "target": {
-    "classification": "native",
-    "nativeEntity": "Events RSVP",
-    "verifiedFqdn": null,
-    "idPolicy": "server-assigned",
-    "crosswalkRequired": true
-  },
-  "sourceAliases": [],
-  "dependsOn": ["crm/contact", "events/event", "events/registration-form"],
-  "preferredWrite": {
-    "surface": "Events RSVP V2",
-    "endpoint": "POST /events/v2/rsvps",
-    "writerId": null,
-    "verification": "verified-live",
-    "importSafe": false,
-    "bulk": false,
-    "decision": "The request shape is verified live (create + readback + delete, 2026-08-16), but importSafe stays FALSE: nothing observable proves that disableNotifications actually suppresses the guest confirmation email. The flag is accepted and echoed, and the site-wide mute was on, yet neither is a proof of non-delivery — see pitfall notification-suppression-unproven for exactly what was probed and what would settle it. Any run that needs RSVPs must surface this at the approval gate."
-  },
-  "reliability": {
-    "status": "partially-reliable",
-    "flags": []
-  },
-  "safeModeContactFields": [
-    {
-      "kind": "email",
-      "targetPath": "rsvp.email",
-      "source": "target-schema",
-      "notes": "Guest email on the RSVP create body — required, format-validated, and the key Wix uses to create/match a CRM contact."
-    }
-  ],
-  "pitfalls": [
-    {
-      "code": "notifications-default-on",
-      "severity": "blocker",
-      "summary": "RSVP creation emails the guest a confirmation unless disableNotifications is set — the domain's registration-notifications-default-on pitfall. An import that forgets the flag mass-mails migrated guests. importSafe is false until the generated script provably sets it on every call AND the suppression itself is proven."
-    },
-    {
-      "code": "notification-suppression-unproven",
-      "severity": "blocker",
-      "summary": "PROBED 2026-08-16, STILL UNPROVEN. What was established: `disableNotifications: true` is accepted on create, is persisted, and is echoed back on both the create response and a later GET (a response flag, not a delivery flag); the site was verified muted (getSiteMuteState → muted:true) before and during the probe; the guest address used a .invalid domain, so nothing could have been delivered anyway. What was NOT established: the create-rsvp docs describe the field only as \"Whether notifications are disabled\" — no statement that it covers the guest-facing confirmation email; there is no public API that lists sent emails, so non-delivery cannot be observed from the API; and the site-wide mute cannot be credited either, because its documented scope is site notifications, not proof about guest transactional mail. WHAT WOULD SETTLE IT: (a) an explicit statement from the Events team/docs that disableNotifications suppresses the guest confirmation email — ask Wix, or (b) a controlled probe on a throwaway site with a real monitored mailbox, comparing disableNotifications true vs false on an UNMUTED site (the true-vs-false pair is what makes the negative observable). Until one of those exists, keep importSafe false."
-    },
-    {
-      "code": "draft-events-reject-rsvps",
-      "severity": "blocker",
-      "summary": "DISCOVERED 2026-08-16 (live): creating an RSVP against a DRAFT event fails with 400 EVENT_NOT_FOUND — RSVP V2 does not see unpublished events. The same call succeeded immediately after POST /events/v3/events/{id}/publish. This breaks the tempting 'import events as drafts, load RSVPs quietly, publish later' plan: the event must be publicly published before its guest list can be imported, which widens the notification/visibility surface of an RSVP import."
-    },
-    {
-      "code": "rsvp-creates-a-crm-contact",
-      "severity": "blocker",
-      "summary": "CORRECTED 2026-08-16 (live): the earlier claim that RSVPs do not touch CRM is wrong. Creating one RSVP produced a new contact for the guest email with sourceType WIX_EVENTS. An RSVP import therefore writes into Contacts as a side effect — it can duplicate contacts imported by crm/contact, and it means RSVP volume is contact volume. Reconcile guest emails against the contact crosswalk before importing RSVPs, and count the contact writes in the plan. (Method note: a Contacts V4 query filtered on info.emails.email returned zero rows for a contact that plainly exists — filter fields are a closed list per endpoint, so verify by listing, not by an unsupported filter.)"
-    },
-    {
-      "code": "registration-state-blocks-create",
-      "severity": "warning",
-      "summary": "A freshly created event comes back with registration.status CLOSED_AUTOMATICALLY (no sale/RSVP window open), and create-rsvp defines RSVPS_CLOSED / RSVPS_NOT_STARTED / GUEST_LIMIT_EXCEEDED / RSVP_LIMIT_EXCEEDED failures. The 2026-08-16 probe passed options.ignoreResponseStatus:true and options.ignoreLimits:true and succeeded; which of the two was strictly required was not isolated. A historical-guest import should pass both deliberately and disclose it — they override the site's own registration rules."
-    },
-    {
-      "code": "form-response-must-match-the-event-form",
-      "severity": "warning",
-      "summary": "rsvp.form.inputValues must use the input names from the event's form (GET /events/v3/events/{id}?fields=FORM), honour mandatory inputs for YES responses, and stay inside predefined options, else INVALID_FORM_RESPONSE. The probe sent firstName/lastName/email and they round-tripped. options.ignoreFormValidation exists as an escape hatch for lossy source data. Additional guests require the event form to carry a GUEST_CONTROL control."
-    },
-    {
-      "code": "one-rsvp-per-email-per-event",
-      "severity": "warning",
-      "summary": "Duplicate guest emails on one event fail with 428 MEMBER_EMAIL_ALREADY_REGISTERED (and MEMBER_ALREADY_REGISTERED when memberId repeats) — dedupe the source guest list by email per event before writing, and make retries crosswalk-guarded."
-    },
-    {
-      "code": "rsvp-only-events",
-      "severity": "blocker",
-      "summary": "The event's registration.initialType must be RSVP and is immutable — a TICKETING event can never accept RSVPs (428 INVALID_EVENT_TYPE). Choose the registration type when creating the event from the source data."
-    },
-    {
-      "code": "past-event-rsvps-unverified",
-      "severity": "warning",
-      "summary": "Still unverified whether Create Rsvp accepts already-ended events; the 2026-08-16 probe used a far-future event. Historical RSVP import may be restricted to upcoming events — verify before planning full history."
-    }
-  ],
-  "mappingGuidance": [
-    "Dependencies: events/event must be published for the RSVP API; events/registration-form supplies accepted input names; crm/contact must exist when matching the RSVP attendee by email.",
-    "Create the event first with registration.initialType RSVP, PUBLISH it, and use its crosswalked ID in eventId — draft events are invisible to this API.",
-    "Set disableNotifications on every create call — this is the safe-import rule for the whole registration group — and still treat the write as guarded until the suppression is proven.",
-    "Map source attendee records (e.g. Event Tickets RSVPs) to firstName/lastName/email/status (YES | NO | WAITLIST) and additionalGuestDetails.guestCount/guestNames; build form.inputValues from the event's form controls.",
-    "Plan the CRM impact: each RSVP creates or matches a contact (sourceType WIX_EVENTS), so sequence RSVPs after crm/contact and reconcile by email."
-  ],
-  "setupRequirements": [
-    "Wix Events app",
-    "SCOPE.DC-EVENTS.MANAGE-GUEST-LIST"
-  ],
-  "evidence": [
-    {
-      "type": "wix-docs",
-      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/registration/rsvp-v2/rsvp-object",
-      "note": "object page: eventId, firstName/lastName/email, status, totalGuests"
-    },
-    {
-      "type": "wix-docs",
-      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/registration/rsvp-v2/create-rsvp",
-      "note": "disableNotifications is a field on the rsvp object (not a query param); described only as \"Whether notifications are disabled\" — no statement about the guest confirmation email"
-    },
-    {
-      "type": "live-run",
-      "path": "anonymized-live-verification",
-      "note": "The docs survey identified the RSVP import surface."
-    },
-    {
-      "type": "live-run",
-      "path": "anonymized-live-verification",
-      "note": "Verified live on a muted site: RSVP creation against a draft event returned EVENT_NOT_FOUND; after publication, creation with disableNotifications:true and ignoreResponseStatus/ignoreLimits succeeded. The flag persisted on readback and Wix created a contact with sourceType WIX_EVENTS. Notification delivery remains unverified because the site was muted and the test address was undeliverable. Probe records were deleted afterward."
-    }
-  ],
-  "notes": "Authored 2026-08-11 from the docs-survey gap (RSVP V2). The write shape was promoted to verified-live on 2026-08-16, but importSafe deliberately stays FALSE — the probe could not prove that no guest email fires (see notification-suppression-unproven for the settle-it conditions). The same probe found two contradictions in the original entry: draft events reject RSVPs, and RSVP creation does create a CRM contact."
-}

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

@@ -1,93 +0,0 @@
-{
-  "schemaVersion": 1,
-  "domain": "events",
-  "entity": "ticket-definition",
-  "displayName": "Event Ticket Definition",
-  "capability": "content.event-ticket-definitions",
-  "target": {
-    "classification": "native",
-    "nativeEntity": "Events Ticket Definition",
-    "verifiedFqdn": null,
-    "idPolicy": "server-assigned",
-    "crosswalkRequired": true
-  },
-  "sourceAliases": [],
-  "dependsOn": ["events/event"],
-  "preferredWrite": {
-    "surface": "Events Ticket Definitions V3",
-    "endpoint": "POST /events/v3/ticket-definitions",
-    "writerId": null,
-    "verification": "verified-live",
-    "importSafe": true,
-    "bulk": false,
-    "decision": "Create with { ticketDefinition: { eventId, name, pricingMethod, feeType, initialLimit?, hidden? } }. eventId, name, pricingMethod and feeType are all required. Verified live on a DRAFT event, so definitions can be staged before the event is published; hidden:true keeps a definition unpurchasable. DELETE /events/v3/ticket-definitions/{id} works. Max 100 definitions per event."
-  },
-  "reliability": {
-    "status": "reliable",
-    "flags": []
-  },
-  "pitfalls": [
-    {
-      "code": "definitions-not-sales",
-      "severity": "blocker",
-      "summary": "A ticket definition is the purchasable ticket type (name, price, limits) — importing it does not carry sold tickets. Past ticket sales remain not importable (domain pitfall ticket-order-history-not-importable)."
-    },
-    {
-      "code": "past-event-definitions-unverified",
-      "severity": "warning",
-      "summary": "Still unverified whether definitions attach to already-ended events (the 2026-08-16 probe used a far-future draft event). For past events the definition is likely pointless without its sales. Import definitions for upcoming events; ledger past ones."
-    },
-    {
-      "code": "ticketing-events-only",
-      "severity": "blocker",
-      "summary": "Create fails with 428 INVALID_EVENT_TYPE unless the event's registration.initialType is TICKETING, and initialType is IMMUTABLE (docs) — an event created for RSVP can never take ticket definitions. Decide RSVP vs TICKETING at event-create time from the source data; a source event with both attendee lists and ticket types cannot be represented as one Wix event."
-    },
-    {
-      "code": "name-capped-at-30-chars",
-      "severity": "warning",
-      "summary": "`name` is minLength 1 / maxLength 30 (description 500, policyText 1000). Source ticket-type names routinely exceed 30 characters — truncate deterministically and ledger it rather than letting the create 400."
-    },
-    {
-      "code": "free-ticket-fee-type",
-      "severity": "warning",
-      "summary": "VERIFIED LIVE 2026-08-16: a free ticket is pricingMethod.fixedPrice.value \"0\" plus feeType NO_FEE (the response echoes free:true, pricingType STANDARD, value normalised to \"0.00\"). NO_FEE is only accepted for free tickets and legacy users — paid tickets must pick FEE_INCLUDED or FEE_ADDED_AT_CHECKOUT, a merchant decision that belongs in the mapping review, not a default."
-    },
-    {
-      "code": "canonical-vs-alias-path",
-      "severity": "warning",
-      "summary": "The docs canonical host path is /events-ticket-definitions/v3/ticket-definitions; /events/v3/ticket-definitions is an accepted alias (both returned 200 on 2026-08-16, creating one definition each). They are the same resource — do not call both in one import or you double-create."
-    }
-  ],
-  "mappingGuidance": [
-    "Dependencies: events/event is required because ticketDefinition.eventId identifies the event that owns every ticket definition.",
-    "Create the event first with registration.initialType TICKETING and use its crosswalked ID in eventId; ticket definitions are per-event and initialType cannot be changed later.",
-    "Map source ticket types (e.g. Event Tickets ticket name/price/capacity) to name (≤30 chars), pricingMethod.fixedPrice (or pricingOptions for tiered prices, guestPrice for pay-what-you-want) and initialLimit; omit initialLimit for unlimited tickets.",
-    "Set salePeriod from the source sale window when present (startDate before endDate, else 428 INVALID_SALE_PERIOD); use hidden:true to stage definitions that should not go on sale at import time."
-  ],
-  "setupRequirements": [
-    "Wix Events app",
-    "SCOPE.DC-EVENTS.MANAGE-TICKET-DEF"
-  ],
-  "evidence": [
-    {
-      "type": "wix-docs",
-      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/ticket-definitions-v3/ticket-definition-object",
-      "note": "object page: eventId, name, pricingMethod, salePeriod, initialLimit, limitPerCheckout"
-    },
-    {
-      "type": "wix-docs",
-      "url": "https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/ticket-definitions-v3/create-ticket-definition"
-    },
-    {
-      "type": "live-run",
-      "path": "anonymized-live-verification",
-      "note": "The docs survey identified the ticket-definition surface."
-    },
-    {
-      "type": "live-run",
-      "path": "anonymized-live-verification",
-      "note": "Verified live: a free hidden ticket definition can be created on a future draft ticketing event through both the /events/v3 alias and the canonical /events-ticket-definitions/v3 path and read back successfully. Probe records were deleted afterward."
-    }
-  ],
-  "notes": "Authored 2026-08-11 from the docs-survey gap (Ticket Definitions V3). Promoted to verified-live 2026-08-16 by a create/read/delete probe on a draft ticketing event; the probe also pinned the required feeType, the 30-char name cap, and the TICKETING-only/immutable-initialType constraint."
-}

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

@@ -1,86 +0,0 @@
-{
-  "schemaVersion": 1,
-  "domain": "forms",
-  "fetchedAt": "2026-08-16",
-  "roots": [
-    "api-reference/crm/forms"
-  ],
-  "surfaces": [
-    {
-      "id": "api-reference/crm/forms/chat-settings",
-      "title": "Chat Settings",
-      "url": "https://dev.wix.com/docs/api-reference/crm/forms/chat-settings",
-      "group": null,
-      "verdict": "not-relevant",
-      "reason": "Configuration for the AI chat that helps a visitor fill a form: enable/disable AI chat, greeting message, summary message. The docs state it 'works alongside the Interactive Form Sessions API' and that each form can have exactly one settings entity keyed by the form's own id. It holds no source-side record — a WordPress form has no AI-chat configuration to carry over — so there is nothing to import here. A migrated form simply has no chat settings, which is the Wix default.",
-      "reviewedOn": "2026-08-16"
-    },
-    {
-      "id": "api-reference/crm/forms/form-schema-templates",
-      "title": "Form Schema Templates",
-      "url": "https://dev.wix.com/docs/api-reference/crm/forms/form-schema-templates",
-      "group": null,
-      "verdict": "not-importable",
-      "reason": "The API is explicitly read-only: 'App owners define templates in the app dashboard, and templates can't be created, updated, or deleted through the API.' A template is a starter definition an app publishes for its namespace, not site data — so an imported WordPress form can never become a template, and there is no write path to attempt. The page is still load-bearing for this domain as the authoritative namespace table (Wix Forms = wix.form_app.form), which forms/form depends on; it is cited in that entity's mapping guidance rather than claimed as an import target.",
-      "reviewedOn": "2026-08-16"
-    },
-    {
-      "id": "api-reference/crm/forms/form-schemas",
-      "title": "Form Schemas",
-      "url": "https://dev.wix.com/docs/api-reference/crm/forms/form-schemas",
-      "group": null,
-      "verdict": "claimed",
-      "refs": [
-        "forms/form"
-      ],
-      "reviewedOn": "2026-08-16"
-    },
-    {
-      "id": "api-reference/crm/forms/form-submissions",
-      "title": "Form Submissions",
-      "url": "https://dev.wix.com/docs/api-reference/crm/forms/form-submissions",
-      "group": null,
-      "verdict": "claimed",
-      "refs": [
-        "forms/form-submission"
-      ],
-      "reviewedOn": "2026-08-16"
-    },
-    {
-      "id": "api-reference/crm/forms/interactive-form-sessions",
-      "title": "Interactive Form Sessions",
-      "url": "https://dev.wix.com/docs/api-reference/crm/forms/interactive-form-sessions",
-      "group": null,
-      "verdict": "not-relevant",
-      "reason": "A runtime surface, not a storage surface: it drives an AI conversation that walks a live visitor through filling a form, streaming typed response chunks (TEXT, SINGLE_SELECT_INPUT, SUBMISSION, END_OF_RESPONSE, …) and ending in a normal submission. Sessions are per-conversation state created against an already-existing form schema; there is no historical session in a WordPress source to recreate, and any record it would produce arrives through forms/form-submission anyway. Nothing to import.",
-      "reviewedOn": "2026-08-16"
-    },
-    {
-      "id": "api-reference/crm/forms/other-services/intake-forms",
-      "title": "Intake Forms",
-      "url": "https://dev.wix.com/docs/api-reference/crm/forms/other-services/intake-forms",
-      "group": "Other Services",
-      "verdict": "not-relevant",
-      "reason": "A different business capability that happens to sit in the same doc tree: waivers, liability releases and consent forms with an expiration period, shareable submission links, and a submission lifecycle with extend/cancel operations. It is not the generic form-and-response capability the WordPress form plugins produce, and the docs are explicit that 'the Wix Forms app isn't required' — it is a parallel service, not a route into Wix Forms. Landing CF7/WPForms contact forms here would give every migrated enquiry an expiry clock it never had. If a source site is later found to run genuine waiver/consent forms with renewal periods, this becomes its own entity pair (intake-form + intake-form-submission); no such source exists in scope today.",
-      "reviewedOn": "2026-08-16"
-    },
-    {
-      "id": "api-reference/crm/forms/service-plugins/form-submissions-service-plugin",
-      "title": "Form Submissions Service Plugin",
-      "url": "https://dev.wix.com/docs/api-reference/crm/forms/service-plugins/form-submissions-service-plugin",
-      "group": "Service Plugins",
-      "verdict": "not-relevant",
-      "reason": "Service plugin (SPI) -- adds LIVE validation on new submissions. It accepts no historical records, so it cannot carry a source submission archive. (a form plugin's historical entries are typically unreachable for an unrelated reason anyway: the answers live in a denied *meta table.) See domains/SERVICE-PLUGINS.md for the escalation rule, the cost list, a worked example and the full 25-plugin catalog.",
-      "reviewedOn": "2026-08-31"
-    },
-    {
-      "id": "api-reference/crm/forms/skills",
-      "title": "Skills",
-      "url": "https://dev.wix.com/docs/api-reference/crm/forms/skills",
-      "group": null,
-      "verdict": "not-relevant",
-      "reason": "AI-agent walkthrough pages (Create Form, Forms Dashboard Navigation), not a data surface. Same verdict and rationale as pricing-plans/skills.",
-      "reviewedOn": "2026-08-16"
-    }
-  ]
-}

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

@@ -1,56 +0,0 @@
-{
-  "schemaVersion": 1,
-  "domain": "forms",
-  "dependsOnRequired": true,
-  "docsRoots": [
-    "api-reference/crm/forms"
-  ],
-  "displayName": "Wix Forms",
-  "ownerHint": "Wix Forms (form schemas, form submissions) domain owners — the Forms APIs sit under the CRM docs tree, not Business Solutions",
-  "wixAppsRequired": [
-    "Wix Forms"
-  ],
-  "defaultImportOrder": [
-    "form",
-    "form-submission"
-  ],
-  "sharedPitfalls": [
-    {
-      "code": "forms-app-required",
-      "severity": "blocker",
-      "summary": "The Wix Forms app (`wix_forms`) must be installed before any write in this domain. The Form Submissions docs state plainly that the API 'only works with the Wix Forms app' and tell callers to confirm with GetAppInstance; Create Form additionally rejects an unknown namespace with 400 UNSUPPORTED_FORM_NAMESPACE. Verify during setup, not at import time."
-    },
-    {
-      "code": "submission-create-has-no-suppression-flag",
-      "severity": "blocker",
-      "summary": "Create Submission (POST /forms/v4/submissions) exposes exactly four inputs — submission, additionalMetadata, captchaToken — and NO notification control: no disableNotifications, no suppressNotifications, no flowControlSettings, no participantNotification. Creating a submission fires the Submission Created domain event, which is the documented trigger surface for Wix Automations (the Forms glossary calls these 'post-submission triggers: automated actions that are executed after a form submission is received'), and the site owner's 'new form submission' notification is exactly such an automation. No docs page in this tree states whether Create Submission emails anyone. Treat every submission create as a potential owner-facing and submitter-facing send until proven silent on a live site; the only control we know of is the site-wide MuteSite policy, which is not a per-call flag and is not applied to existing sites by default."
-    },
-    {
-      "code": "form-caps-and-gated-field-types",
-      "severity": "warning",
-      "summary": "Two independent limits, both enforced by FAILING the create rather than degrading. (1) Counts: each namespace has a provider-set maxForms, maxFields and maxDeletedForms, readable live with List Forms Providers Configs (GET /form-schema-service/v4/forms/providers-config); exceeding one returns 400 FORM_FIELDS_COUNT_EXCEEDED / NAMESPACE_FORMS_COUNT_EXCEEDED / FORM_SIZE_EXCEEDED. Note deleted forms occupy their own cap, so a re-run that deletes and recreates schemas can exhaust maxDeletedForms. (2) Field types: About Form Fields marks File upload and Signature as requiring a Premium plan; Product, Fixed price, Custom price and Donation as requiring Premium plan + Wix eCommerce; Appointment as requiring Wix Meetings; Service picker and Multi-service picker as requiring Wix Services. Check both during setup discovery, not at import time."
-    },
-    {
-      "code": "namespace-decides-behaviour",
-      "severity": "warning",
-      "summary": "Every form schema belongs to an app namespace, and the namespace decides both which app renders the form and what status a submission is created in. Imported WordPress forms belong in `wix.form_app.form` (Wix Forms). Do not create schemas in another app's namespace (wix.bookings.v2.bookings, wix.ecom.v1.checkout, wix.pricing_plans.v1.custom_form, …) to make a form 'appear' somewhere — those namespaces carry that app's business logic, including PENDING submissions that are deleted if never confirmed."
-    }
-  ],
-  "evidence": [
-    {
-      "type": "wix-docs",
-      "url": "https://dev.wix.com/docs/api-reference/crm/forms/introduction",
-      "note": "domain root; menu walked 2026-08-16. NOTE: Wix Forms is NOT under api-reference/business-solutions — the whole tree lives under api-reference/crm/forms (Form Schemas, Form Submissions, Service Plugins, Chat Settings, Interactive Form Sessions, Other Services → Intake Forms, Skills, Form Schema Templates)."
-    },
-    {
-      "type": "wix-docs",
-      "url": "https://dev.wix.com/docs/api-reference/crm/forms/form-schemas/introduction",
-      "note": "'form' and 'form schema' are used interchangeably; namespace table for apps made by Wix (Wix Forms = wix.form_app.form); deleted schemas go to a 90-day trash bin and permanently deleting a schema deletes all of its submissions (read 2026-08-16)"
-    },
-    {
-      "type": "domain-kb",
-      "path": "skills/wix-replatform/SKILL.md",
-      "note": "the only notification control available to this domain is the site-level MuteSite primitive; it is applied to new target sites and is opt-in for existing sites — it is not a per-call suppression flag"
-    }
-  ]
-}