@wix/ditto-codegen-public 1.0.465 → 1.0.467

package/dist/opencode-tools/report-wix-feedback.ts

@@ -35,11 +35,13 @@ function buildProvenance(): string {
 
 export default tool({
   description:
-    "Report a problem with Wix docs or the wix-mcp tools to the Wix MCP team. Call it when " +
-    "docs or MCP — not your own code — made the task harder: a search whose top results were " +
-    "off-target, an article or example that is wrong or missing the fields you needed, a " +
-    "method schema that doesn't match the installed SDK types, or an MCP tool error. Include " +
-    "cases you recovered from. Do NOT report your own mistakes or the user's request. Call it " +
+    "Report a problem with the Wix docs (dev.wix.com, read through wix-mcp) or the wix-mcp " +
+    "tools to the Wix MCP team: a search whose top results were off-target, a docs article " +
+    "or example that is wrong or missing the fields you needed, a method schema that " +
+    "doesn't match the installed SDK types, or a wix-mcp tool error. Include cases you " +
+    "recovered from. Do NOT report skill references (SKILL.md, references/*.md), package " +
+    "docs in node_modules, your own mistakes, or the user's request — those aren't wix-mcp " +
+    "issues. Every report must cite the wix-mcp tool or dev.wix.com URL involved. Call it " +
     "at most ONCE per task, covering every friction point you've hit so far.",
   args: {
     message: tool.schema
@@ -47,9 +49,9 @@ export default tool({
       .min(1)
       .describe(
         "Plain-text report. For each friction point: the tool and exact input (search " +
-          "term, docs URL), what came back, what was wrong or missing, the workaround you " +
+          "term, dev.wix.com URL), what came back, what was wrong or missing, the workaround you " +
           "used, and what you expected. Then your best guess of where the fault lives " +
-          "(search ranking / docs article or example / method schema / SDK typings / MCP " +
+          "(search ranking / docs article or example / method schema / SDK typings / wix-mcp " +
           "tool) and whether you confirmed it. End with one line naming the most important " +
           "problem. No secrets or tokens.",
       ),

package/dist/out.js

@@ -11724,8 +11724,9 @@ var require_model_knobs = __commonJS({
     exports2.getSmallReasoningEffort = getSmallReasoningEffort;
     exports2.hasSmallReasoningEffortOverride = hasSmallReasoningEffortOverride;
     exports2.getOpenAiServiceTier = getOpenAiServiceTier;
-    exports2.DEFAULT_MODEL = "anthropic/claude-sonnet-4-6";
-    exports2.DEFAULT_SMALL_MODEL = "anthropic/claude-haiku-4-5-20251001";
+    exports2.DEFAULT_MODEL = "openai/gpt-6-sol";
+    exports2.DEFAULT_SMALL_MODEL = "openai/gpt-6-luna";
+    var DEFAULT_REASONING_EFFORT = "low";
     var SMALL_MODEL_REASONING_EFFORT = "medium";
     var REASONING_EFFORTS = ["xhigh", "high", "medium", "low"];
     var VALID_OPENAI_SERVICE_TIERS = [
@@ -11763,8 +11764,9 @@ var require_model_knobs = __commonJS({
     }
     function getReasoningEffort() {
       const effort = readEnumEnv("CODEGEN_REASONING_EFFORT", REASONING_EFFORTS);
-      if (!effort)
-        return void 0;
+      if (!effort) {
+        return hasModelOverride() || hasSmallModelOverride() ? void 0 : DEFAULT_REASONING_EFFORT;
+      }
       if (!isOpenAiModel(getModel()) || !isOpenAiModel(getSmallModel())) {
         throw new Error("CODEGEN_REASONING_EFFORT requires BOTH the main and small models to be openai/* \u2014 set CODEGEN_MODEL_OVERRIDE and CODEGEN_SMALL_MODEL_OVERRIDE (reasoning-effort variants are only supported on openai models).");
       }
@@ -14232,7 +14234,7 @@ var require_brik_import = __commonJS({
 
 If \`.wix/agentInput/brikMeta.json\` exists AND its \`brikMeta\` object has \`promptVariant\` set to \`skill-v1\`, this job is a Brik tool import: you MUST invoke the \`wix-brik\` skill FIRST and follow it exactly. It owns the import itself - scaffolding the Editor React Component, running the deterministic import script over \`.wix/agentInput/brikImport.json\`, splicing the tool's creative code, then installing dependencies and building plus generating the manifest. Do NOT derive the component's public surface yourself and do NOT re-tune the manifest.
 
-The skill does NOT replace step 5 of the workflow: its \`npx wix build\` transpiles without typechecking. Once its DONE WHEN checks pass, still delegate to the \`codegen-validator\` subagent as usual, and fix whatever it reports in your spliced code only - never in the script-written surface.
+The skill does NOT replace step 5 of the workflow: its \`npx wix build\` transpiles without typechecking. Once its DONE WHEN checks pass, still run step 5 as the workflow says, and fix whatever it reports in your spliced code only - never in the script-written surface.
 
 If \`promptVariant\` is any other value, it is the legacy import pipeline's payload: ignore this rule and follow the job's own instructions.`;
   }
@@ -14934,7 +14936,7 @@ var require_codegen_rules = __commonJS({
     };
     var DIRECT_VALIDATION = {
       toolRule: "- `validate` (tsc + build) \u2014 you call it yourself at step 5. Do NOT delegate it.",
-      step: `5. **Validate**: Call \`validate({ runBuild: true })\` yourself \u2014 it typechecks AND builds in a single pass (tsc runs first and fails fast before the build). Fix any errors and re-run until it passes. Pass installDeps: true only if package.json changed and npm install was not already run in this session. Do NOT delegate this to a subagent, and do NOT make a separate tsc-only call first \u2014 the single runBuild pass already fails fast on type errors. Do NOT move on until the build is clean. After the build is clean, if you created or modified an EDITOR_REACT_COMPONENT extension in this task, run \`npx wix generate manifest\` via bash (idempotent).`
+      step: `5. **Validate**: Call \`validate({ runBuild: true })\` yourself \u2014 it typechecks AND builds in a single pass (tsc runs first and fails fast before the build). Fix any errors and re-run until it passes. Pass installDeps: true only if package.json changed and npm install was not already run in this session. Do NOT delegate this to a subagent, and do NOT make a separate tsc-only call first \u2014 the single runBuild pass already fails fast on type errors. NEVER force a green build: no \`as any\`, no \`@ts-ignore\`, no NEW \`@ts-expect-error\`, no switching a correct named import to \`import * as\`, and no changing runtime behaviour (e.g. unwanted \`defaultProps\` values) or deleting the failing code just to satisfy tsc. Do NOT move on until the build is clean. After the build is clean, if you created or modified an EDITOR_REACT_COMPONENT extension in this task, run \`npx wix generate manifest\` via bash (idempotent).`
     };
     var buildCoreRules = (validation) => `CORE PRINCIPLES:
 - Do NOT invent or assume new types, modules, functions, props, events, or imports.
@@ -14955,7 +14957,7 @@ ${validation.toolRule}
 ${(0, shared_rules_1.buildFileOperationsRules)("fixing type errors")}
 - API discovery (shapes, method signatures, types) \u2014 in this order: (1) loaded skills + KNOWN WIX APIS, if they already cover the API; (2) wix-mcp, yourself: \`SearchWixSDKDocumentation\` to find the method, then \`ReadFullDocsMethodSchema\` for its exact exported name, options object, response fields, enum values and scope IDs \u2014 the schema is the source of truth; an article or its examples are not. Model the call on the SDK view, not REST, and use the direct form inside the extension: \`import { <namespace> } from "@wix/<pkg>"; await <namespace>.<method>(<options>)\` \u2014 never \`createClient\`. Note any setup the docs require from the user (an app to install, a dashboard setting to enable) for the final message. For WDS components/props, use the \`wix-design-system\` skill; (3) grepping \`node_modules\` ONLY as a last resort if the above return nothing \u2014 SDK internals are not a documentation source, and doing it first wastes turns, inflates context, and is unreliable.
 - NEVER write a Wix SDK method, field, or enum value you haven't seen in a skill or a method schema.
-- \`report-wix-feedback\` \u2014 report Wix docs / wix-mcp problems to Wix (when: workflow step 7).
+- \`report-wix-feedback\` \u2014 report problems with the Wix docs (dev.wix.com, via wix-mcp) or the wix-mcp tools to Wix (when: workflow step 7). NOT for skill references or your own code.
 - NEVER run preview, dev, release, or promote commands.
 
 KNOWN WIX APIS (already documented \u2014 do NOT rediscover these from node_modules; for full detail consult the \`wix-app\` skill's references or \`ReadFullDocsMethodSchema\`):
@@ -14969,7 +14971,7 @@ IMPLEMENTATION WORKFLOW:
 4. **Register**: Register all extensions in \`src/extensions.ts\`.
 ${validation.step}
 6. **Declare permissions**: If the generated code requires Wix app permissions, call \`required-permissions\` ONCE with their SCOPE IDs (see PERMISSIONS below). Skip this step entirely if no permissions are needed.
-7. **Report docs problems**: Skip this step if you already called \`report-wix-feedback\` this run. Otherwise look back at the run: if ANY of these happened, call it ONCE covering all of them: (a) you inspected \`node_modules\` to find a Wix SDK signature, shape, or type because the docs didn't give you one that compiles; (b) the validator fixed a Wix SDK call you wrote from the docs \u2014 read its summary; (c) a doc example, article, or schema contradicted the installed SDK types; (d) a search's top results were off-target, or a wix-mcp tool failed. For each: the docs URL or search term, what it showed, and what actually worked.
+7. **Report docs problems**: Skip this step if you already called \`report-wix-feedback\` this run. Otherwise look back at the run: if ANY of these happened, call it ONCE covering all of them: (a) you inspected \`node_modules\` to find a Wix SDK signature, shape, or type because the docs didn't give you one that compiles; (b) the validator fixed a Wix SDK call you wrote from a dev.wix.com doc \u2014 read its summary; (c) a dev.wix.com example, article, or schema contradicted the installed SDK types; (d) a search's top results were off-target, or a wix-mcp tool failed. For each: the dev.wix.com URL or search term, what it showed, and what actually worked. A gap in a skill reference is not a wix-mcp problem \u2014 don't report it here.
 8. **Final message**: Your last message is returned to the user as the codegen output \u2014 keep it short and plain (a sentence or two on what the app now does). Do NOT mention permissions/scopes here (see PERMISSIONS) and follow OUTPUT MESSAGE below.
 9. **Stop**: STOP immediately. Do NOT refactor, clean up, or verify.
 
@@ -14994,7 +14996,7 @@ CRITICAL: Only include permissions you have explicitly seen in the Wix SDK docum
 
 The \`required-permissions\` tool records and surfaces permissions to the user automatically \u2014 NEVER mention permissions/scopes (IDs or names) in your output, or tell the user to grant them.`;
     function isValidatorSubagentSkipped() {
-      return (0, model_knobs_1.readEnumEnv)("CODEGEN_RULES_NO_VALIDATOR", ["1"]) === "1";
+      return (0, model_knobs_1.readEnumEnv)("CODEGEN_RULES_NO_VALIDATOR", ["0", "1"]) !== "0";
     }
     function buildCodegenRules(environmentIdentity) {
       const validation = isValidatorSubagentSkipped() ? DIRECT_VALIDATION : DELEGATED_VALIDATION;
@@ -23838,9 +23840,9 @@ var require_docs_feedback_nudge = __commonJS({
     var write_plugin_1 = require_write_plugin();
     var subagents_1 = require_subagents();
     exports2.WIX_SDK_INTERNALS_RE = /node_modules\/@wix\/(?!patterns\b|design-system\b)[\w-]+/;
-    exports2.SDK_INTERNALS_NOTE = "Docs check: you are reading Wix SDK internals. If it's because the docs didn't give you a signature, shape, or type that compiles, call `report-wix-feedback` once you have the answer \u2014 with the docs URL or search term you used, what it showed, and what you found here.";
-    exports2.VALIDATOR_NOTE = "Docs check: if the validator fixed a Wix SDK call you wrote from a doc example, article, or schema, call `report-wix-feedback` now \u2014 with the docs URL, what it showed, and what the validator changed it to.";
-    exports2.COMPILE_FAILURE_NOTE = "Docs check: if a failure above is in a Wix SDK call you wrote from a doc example, article, or schema, call `report-wix-feedback` once you've fixed it \u2014 with the docs URL, what it showed, and what actually compiled.";
+    exports2.SDK_INTERNALS_NOTE = "Docs check: you are reading Wix SDK internals. If it's because the Wix docs you read through wix-mcp didn't give you a signature, shape, or type that compiles, call `report-wix-feedback` once you have the answer \u2014 with the docs URL or search term you used, what it showed, and what you found here.";
+    exports2.VALIDATOR_NOTE = "Docs check: if the validator fixed a Wix SDK call you wrote from a dev.wix.com doc example, article, or schema you read through wix-mcp, call `report-wix-feedback` now (not for skill references) \u2014 with the docs URL, what it showed, and what the validator changed it to.";
+    exports2.COMPILE_FAILURE_NOTE = "Docs check: if a failure above is in a Wix SDK call you wrote from a dev.wix.com doc example, article, or schema you read through wix-mcp, call `report-wix-feedback` once you've fixed it (not for skill references) \u2014 with the docs URL, what it showed, and what actually compiled.";
     exports2.REPORT_SENT_PREFIX = "Report sent";
     exports2.DOCS_FEEDBACK_NUDGE_FILENAME = "docs-feedback-nudge.ts";
     function buildDocsFeedbackNudgeSource() {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/ditto-codegen-public",
-  "version": "1.0.465",
+  "version": "1.0.467",
   "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": "175eef2c2268c965ea1b16a42224fac32fe17587e762719c5ed06a1b"
+  "falconPackageHash": "6e0bea815a8cc927e371476a9322bb0e2056a44108fca77338b370ff"
 }