@wix/ditto-codegen-public 1.0.430 → 1.0.431

package/dist/out.js

@@ -11714,10 +11714,11 @@ or reports what it couldn't fix. Validation step only \u2014 never generates fea
     var VALIDATOR_PROMPT = `Run 'validate({ runBuild: true })', fix the errors it reports, and re-run until
 it passes. You are fixing EXISTING code \u2014 do NOT add features or rewrite whole
 files. NEVER force a green build by suppressing types: no 'as any', no
-'@ts-ignore'/'@ts-expect-error', and do NOT switch a correct named import to
+'@ts-ignore', no NEW '@ts-expect-error', and do NOT switch a correct named import to
 'import * as' just to satisfy tsc \u2014 that ships code that compiles but breaks
-at runtime. A type error on a
-Wix SDK method/namespace/parameter means the call is WRONG: look up the correct
+at runtime. Leave an EXISTING '@ts-expect-error' alone when a skill mandates it
+(e.g. a context provider's 'moduleSpecifier' import); removing it is not a fix.
+A type error on a Wix SDK method/namespace/parameter means the call is WRONG: look up the correct
 usage via skills or wix-mcp ('SearchWixSDKDocumentation' \u2192
 'ReadFullDocsMethodSchema') and fix it to the real exported method + its options
 object. Deleting the failing code is a regression, not a fix \u2014 the capability is

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/ditto-codegen-public",
-  "version": "1.0.430",
+  "version": "1.0.431",
   "description": "AI-powered Wix CLI app generator - standalone executable",
   "scripts": {
     "build": "node build.mjs",
@@ -29,5 +29,5 @@
     "esbuild": "^0.27.2",
     "vitest": "^4.0.16"
   },
-  "falconPackageHash": "f9fc3acb00a15379aa0f04d1a851e4d20ff26232815715e6d955031c"
+  "falconPackageHash": "85a0210cddb251eaf19067e588dd30dc2a73f6bb94352b5b386068d3"
 }