@gakim-digital/dexter-bridge 0.13.12 → 0.13.13

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gakim-digital/dexter-bridge",
-  "version": "0.13.12",
+  "version": "0.13.13",
   "description": "Local bridge for InstaWebAI and Dexter — runs Codex, Claude Code, or OpenCode on your machine.",
   "type": "module",
   "bin": {

package/src/framerTools.js

@@ -186,7 +186,7 @@ const TOOL_DEFINITIONS = [
   },
   {
     name: 'framer_undo_run',
-    description: 'Put back exactly what one earlier run in this conversation changed, from context.recentRuns: settings and text return, layers it added are removed, layers it removed come back, and moved layers return to their place. Anything changed again since that run is left as it is and reported. Use it when the user asks to revert or undo earlier work, instead of rebuilding the earlier state by hand. To go further back, undo the later runs first, newest first.',
+    description: 'Put back exactly what one earlier run in this conversation changed, from context.recentRuns: settings and text return, layers it added are removed, layers it removed come back, and moved layers return to their place. Anything changed again since that run is left as it is and reported. Use it when the user asks to revert or undo earlier work, instead of rebuilding the earlier state by hand. To go further back, undo the later runs first, newest first. Skip a run that has undid: it was itself an undo, and undoing it brings back what it removed.',
     inputSchema: {
       type: 'object',
       properties: {

package/src/protocol.js

@@ -519,6 +519,7 @@ export function buildFramerOutcomePrompt(outcome = {}, product, promptContext =
     'Deleting CMS collections, items, or fields, or pages, needs the user\'s clear permission in this conversation; context.permissions.deleteContent is true when they gave it. A request to change, fix, or replace content is not permission to delete it. Without it, ask one plain question naming exactly what you would delete and return blocked, before building any replacement for it.',
     'If you changed layers before asking a question, say in your summary what you changed.',
     'Ask a question once. If the user replies without answering it, do not ask it again: take the option that changes least, such as only the page they are on, do it, and say in your summary which option you took and how to get the other.',
+    'When the user rejects or reverts a change you made, that approach is ruled out for the rest of the conversation: do not apply it again, in the same or another form, unless they ask for it. Find the cause in the layers themselves and fix it a different way; when the user says something worked earlier, read what changed since then instead of reapplying your earlier fix.',
     'When you return blocked, write the question itself in summary, since summary is what the user reads; blockedReason is a short note for Dexter.',
     'summary is the only text the user reads; checks are for Dexter and are never shown to them. Write summary in Markdown. After an edit, a short, plain answer about what changed is enough. When the user asks a question or asks for a report, audit, review, list, or plan, summary is the full answer, formatted with headings, lists, or tables where they help: never shorten it to a line or put it in checks.',
     'Write in the language the user wrote their request in: the summary, any question, and the sentences Dexter shows while you work. Keep layer names and quoted text as they are.',