@eventmodelers/cli 1.0.92 → 1.0.93

package/cli.js

@@ -2631,14 +2631,15 @@ async function runModeling(kitDir, projectDir, { verbose = false, standalone = f
     'way .agent-modeling-kit/CLAUDE-STANDALONE.md describes — read it now if you have not this session, and ' +
     'follow its "Propose mode" section. Read what this needs and no more: every nodeId above in one get_nodes, ' +
     'plus one get_board_outline per chapter you have not read this session. Every change above is by one person, ' +
-    'changed_by, who is talking to you in the chat. ALWAYS post ONE short chat message to them with ' +
-    'post_chat_message (no sessionId, no replyTo, preferUserId = changed_by; at most 1000 characters) — never stay silent after their ' +
-    'edit. A fresh, half-finished element (placeholder name, no ' +
+    'changed_by, who is talking to you in the chat. First check the change is one: if the changed nodes ' +
+    'read the same as before — same names, fields, types and connections, only moved or resized — nothing ' +
+    'changed, so say nothing and reply <promise>NOOP</promise>. Otherwise post ONE short chat message to them with ' +
+    'post_chat_message (no sessionId, no replyTo, preferUserId = changed_by; at most 1000 characters). A fresh, half-finished element (placeholder name, no ' +
     'fields, names still changing) is the reason to speak, not to wait. Something worth doing → say concretely ' +
     'what you would do (element names) and ask whether to go ahead. Nothing concrete → say what you saw and ' +
     'that you are not sure what to do with it, and ask ("You renamed Orders to take — not sure what to do with ' +
     'it yet. Want fields on it?"). Fold anything your earlier unanswered message proposed into this one instead ' +
-    'of repeating it. One to three sentences. Only CHAT_NO_ACTIVE_SESSION (they cleared the conversation or ' +
+    'of repeating it. One to three sentences. Besides a change that changed nothing, only CHAT_NO_ACTIVE_SESSION (they cleared the conversation or ' +
     'switched to another agent) or CHAT_AWAITING_REPLY (you wrote to them less than 3 minutes ago) keep you ' +
     'silent: then change nothing and reply <promise>NOOP</promise>.';
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eventmodelers/cli",
-  "version": "1.0.92",
+  "version": "1.0.93",
   "description": "Eventmodelers CLI — real-time Claude agent + skills for Claude Code, for any stack (Node, Supabase, Axon, OpenCQRS, UmaDB, Kurrent, or modeling-only)",
   "type": "module",
   "bin": {

package/stacks/modeling-kit/templates/kit/CLAUDE-STANDALONE.md

@@ -235,7 +235,11 @@ So on a `mode=propose` turn:
    modeling right now, and the moment to offer the next step.
 2. **Change nothing.** No node writes, no board comments, no `create_prompt`, no subagents. The
    fill-in licence above is `mode=act` only.
-3. **Always post one short message** to that person — `post_chat_message` with no `sessionId`, no
+3. **A change that changed nothing gets nothing.** If the changed nodes read the same as before —
+   same names, fields, types and connections, only moved or resized — there is nothing to say:
+   no chat message, reply `<promise>NOOP</promise>`. Never answer a move with "looks the same to
+   me" or by repeating an earlier offer.
+4. **Otherwise post one short message** to that person — `post_chat_message` with no `sessionId`, no
    `replyTo`, and `preferUserId` = the header's `changed_by`. One to three sentences (never over
    1000 characters — the limit for any chat message), the same style as a chat reply:
    - something worth doing → what you would do, element names included, and ask: *"You just added
@@ -244,9 +248,9 @@ So on a `mode=propose` turn:
      *"You renamed Orders to take — not sure what to do with it yet. Want fields on it?"*
    If an earlier message of yours is still unanswered, fold what it proposed into this one rather
    than repeating it or staying quiet.
-4. **Only two things keep you silent**: `CHAT_NO_ACTIVE_SESSION` (they cleared the conversation or
+5. **Besides that, only two things keep you silent**: `CHAT_NO_ACTIVE_SESSION` (they cleared the conversation or
    switched to another agent — never fall back to acting or to a board comment) and
    `CHAT_AWAITING_REPLY` (you wrote to them less than 3 minutes ago). Then reply `<promise>NOOP</promise>`. A turn in which you posted is not a NOOP.
-5. **The yes arrives as a `CHAT` turn.** Read the session: your proposal is the message before
+6. **The yes arrives as a `CHAT` turn.** Read the session: your proposal is the message before
    the answer. On a yes, create the prompts for exactly what you proposed (`create_prompt`,
    `originMessageId` = the yes); on a partial yes, only that part; on a no, acknowledge and drop it.