@eventmodelers/cli 0.0.21 → 0.0.22

package/cli.js

@@ -835,7 +835,7 @@ async function configureMcp(options = {}) {
 // read-only config resolution (`loadLocalConfig`/`fetchPlatformConfig`) is reused
 // from the kit's lib/config.js, to avoid duplicating the config-file-walk logic.
 // See `claude-modeling.md` in the kit's project root for the per-turn instructions
-// this mode's warm session follows.
+// this mode's modeling session follows.
 async function runModeling(kitDir, projectDir) {
   const configLibPath = join(kitDir, 'lib', 'config.js');
   if (!existsSync(configLibPath)) {
@@ -866,7 +866,7 @@ async function runModeling(kitDir, projectDir) {
     'relevant slice or column node on the board, then continue with your best interpretation of the prompt.\n\n';
 
   // Sent once, on the first turn only — it's what tells CLAUDE.md's dispatcher to
-  // follow claude-modeling.md instead of claude-ralph.md, and gives the warm
+  // follow claude-modeling.md instead of claude-ralph.md, and gives the modeling
   // session its one-time connect credentials. Every later turn only carries the
   // per-prompt fields that actually vary (board_id, comment_id, ...).
   let firstTurn = true;
@@ -952,7 +952,7 @@ async function runModeling(kitDir, projectDir) {
         turn.reject(new Error(`claude process exited (${code}) mid-turn`));
       }
     });
-    log('warm session started');
+    log('modeling session started');
   }
 
   function runClaudeWarm(text) {

package/package.json

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

package/stacks/modeling-kit/templates/root/claude-modeling.md

@@ -1,4 +1,4 @@
-# Modeling Direct-Dispatch — Warm Session Mode
+# Modeling Direct-Dispatch — Modeling Session Mode
 
 Used by `npx @eventmodelers/cli run --modeling`. The CLI itself subscribes to the board's realtime channel and writes each incoming prompt directly to your stdin as a new turn — there is **no `tasks.json` queue** in this mode. Each user message you receive already IS the one prompt to handle; there's nothing to read, pre-filter, or pick from.
 
@@ -12,7 +12,7 @@ You are a long-lived process handling many turns in a row. Don't redo one-time s
    - if this turn's `board_id` differs from the one you last connected with, or
    - if the last API call returned `401`/`403`.
 
-   Otherwise skip straight to executing the prompt — re-running `/connect` every turn defeats the point of a warm session.
+   Otherwise skip straight to executing the prompt — re-running `/connect` every turn defeats the point of a modeling session.
 3. **Resolve `BOARD_ID`** from this turn's `board_id` field; if absent, fall back to `boardId` in `.eventmodelers/config.json`.
 4. Execute the prompt using the skill matched in CLAUDE.md's Skill Selection table.
    **Questioning rule**: you are running autonomously — no human is available to answer questions. If you need clarification, do not pause or ask interactively — post a `QUESTION`-type comment (`/handle-comment` with `action=place`, `type=QUESTION`) on the most relevant node, then continue with your best interpretation.