@wix/ditto-codegen-public 1.0.336 → 1.0.338

package/dist/out.js

@@ -12215,7 +12215,11 @@ var require_site_data_layer_rules = __commonJS({
     exports2.SITE_DATA_LAYER_RULES = void 0;
     exports2.SITE_DATA_LAYER_RULES = `# Site Data Layer Rules
 
-DATA LAYER \u2014 REST only. The agent operates on a live Wix site (METASITE_ID is in your prompt context). For any persistent-data need \u2014 CMS collections, content tables, schemas, data models, or databases that store items \u2014 use the \`wix-site-data-collection\` skill. The \`wix-app\` skill remains the right tool for surrounding extensions (dashboard pages, modals, widgets); only the data layer is overridden.
+The agent operates on a live Wix site (METASITE_ID is in your prompt context).
+
+For any persistent-data need \u2014 CMS collections, content tables, schemas, data models, or databases that store items \u2014 use the \`wix-site-data-collection\` skill.
+
+The \`wix-app\` skill remains the right tool for surrounding extensions (dashboard pages, modals, widgets); only the data layer is overridden. A Wix CLI data collection extension will NOT work here \u2014 it only provisions on app install, but this is a live site that already exists. Use the \`wix-site-data-collection\` skill to discover the existing collections on the site and wire your code against them.
 
 DO NOT write any code relating to Wix CLI data extensions \u2014 for example, do not generate \`src/extensions/data/extensions.ts\`.`;
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/ditto-codegen-public",
-  "version": "1.0.336",
+  "version": "1.0.338",
   "description": "AI-powered Wix CLI app generator - standalone executable",
   "scripts": {
     "build": "node build.mjs",
@@ -28,5 +28,5 @@
     "esbuild": "^0.27.2",
     "vitest": "^4.0.16"
   },
-  "falconPackageHash": "b88c9d7b3f4ddff9550b92f8435497477552547d5bada1ed4e0d560d"
+  "falconPackageHash": "a81fb5dcaeaa89e3ee490de01cd247de5fdb49be128032f25cf0ede6"
 }