open-walnut 0.6.11 → 0.6.12

package/dist/build-info.json

@@ -1,7 +1,7 @@
 {
-  "version": "0.6.11",
-  "commit": "6f44b734",
+  "version": "0.6.12",
+  "commit": "fe49d6a2",
   "branch": null,
-  "builtAt": "2026-10-14T04:49:55.068Z",
+  "builtAt": "2026-10-15T05:22:53.410Z",
   "dirty": false
 }

package/dist/cli-fast.js

@@ -14,8 +14,8 @@ import path from "path";
 import { fileURLToPath } from "url";
 function getVersion() {
   if (cachedVersion) return cachedVersion;
-  if ("0.6.11") {
-    cachedVersion = "0.6.11";
+  if ("0.6.12") {
+    cachedVersion = "0.6.12";
     versionKnown = true;
     return cachedVersion;
   }
@@ -2811,10 +2811,10 @@ var init_output_mode = __esm({
     init_types();
     init_voice_reply();
     OUTPUT_MODE_INSTRUCTION_MARKER = "[Rich output mode: ";
-    RICH_OUTPUT_MODE_ON_INSTRUCTION = `${OUTPUT_MODE_INSTRUCTION_MARKER}ON] Keep writing markdown for what markdown does well (headings, lists, tables, code blocks), and mix raw HTML into the same reply (separated by a blank line) for what markdown cannot express: colour that carries meaning, diagrams (inline <svg>), side-by-side or card layout, and interactivity (<details>, CSS :checked). The client renders it natively while streaming. Set text and background colour together or neither: a custom background with inherited or muted text loses contrast (theme vars --fg, --fg-muted, --bg-secondary, --border always fit). For anything needing <script>, emit a \`\`\`html-app fenced block (rendered in a sandboxed iframe). A short answer needs none of this. Component recipes (steppers, SVG diagrams, animations, islands): \`walnut tools call skill_read '{"dirName":"walnut-rich-output"}'\`.`;
+    RICH_OUTPUT_MODE_ON_INSTRUCTION = `${OUTPUT_MODE_INSTRUCTION_MARKER}ON] Keep writing markdown for what markdown does well (headings, lists, tables, code blocks), and mix raw HTML into the same reply (separated by a blank line) for what markdown cannot express: colour that carries meaning, diagrams (inline <svg>), side-by-side or card layout, and interactivity (<details>, CSS :checked). The client renders it natively while streaming. Write visual HTML directly in your reply, not in a file, screenshot, or HTML code fence, unless the user asks for one. Keep each widget contiguous, without internal blank lines. Set text and background colour together or neither: a custom background with inherited or muted text loses contrast (theme vars --fg, --fg-muted, --bg-secondary, --border always fit). For anything needing <script>, emit a \`\`\`html-app fenced block (rendered in a sandboxed iframe). A short answer needs none of this. Component recipes (steppers, SVG diagrams, animations, islands): \`walnut tools call skill_read '{"dirName":"walnut-rich-output"}'\`.`;
     RICH_OUTPUT_MODE_OFF_INSTRUCTION = `${OUTPUT_MODE_INSTRUCTION_MARKER}OFF] Return to plain markdown replies.`;
     OUTPUT_MODE_REMINDER_MARKER = "[Rich output mode is still on";
-    RICH_OUTPUT_MODE_REMINDER = `${OUTPUT_MODE_REMINDER_MARKER} \u2014 markdown first; add HTML only for colour, diagrams, or layout markdown can't do.]`;
+    RICH_OUTPUT_MODE_REMINDER = `${OUTPUT_MODE_REMINDER_MARKER}: markdown first; for colour, diagrams, or layout, write raw HTML directly in this reply. No files, screenshots, or HTML code fences unless requested (html-app for scripts); no blank lines inside a widget.]`;
   }
 });