@eventmodelers/cli 0.0.20 → 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) {
@@ -1217,8 +1217,14 @@ program
   .option('--modeling', 'Keep one Claude process warm across prompts instead of spawning a fresh one per task, for low-latency voice/live use. Modeling-kit installs only — there is no cold-spawn/tasks.json loop for modeling-kit. Built into the CLI, not a per-project file.')
   .action(async (opts) => {
     const cwd = process.cwd();
-    const kitDir = findInstalledKitDir(cwd);
-    const isModelingKit = kitDir.endsWith(MODELING_KIT.kitDirName);
+    // Both kit dirs can be installed side by side (e.g. running a build-kit and a
+    // modeling-kit agent from the same project). findInstalledKitDir only ever
+    // returns its first fixed-order match, which would silently prefer one stack
+    // over the other regardless of which the caller actually asked for — so here
+    // we resolve each stack's dir independently instead of relying on that order.
+    const installedKitDirs = findAllInstalledKitDirs(cwd);
+    const modelingKitDir = installedKitDirs.find((d) => d.endsWith(MODELING_KIT.kitDirName)) ?? null;
+    const buildKitDir = installedKitDirs.find((d) => d !== modelingKitDir) ?? null;
 
     // No overlap between the two stacks' runtimes: modeling-kit only ever runs the
     // warm, direct-dispatch loop (--modeling); build-kit only ever runs the
@@ -1230,7 +1236,7 @@ program
         console.error('❌ --modeling is mutually exclusive with --bash/--ollama — those select a build-kit runner, which --modeling has no use for.');
         process.exit(1);
       }
-      if (!isModelingKit) {
+      if (!modelingKitDir) {
         console.error(`❌ --modeling only supports a modeling-kit install (${MODELING_KIT.kitDirName}/) — it subscribes to the org-wide prompt queue, which build-kit stacks don't have. Use \`eventmodelers run\` (optionally with --ollama/--bash) for build-kit's slice-status loop instead.`);
         process.exit(1);
       }
@@ -1239,9 +1245,9 @@ program
       // does right after (dynamic imports, config reads) can eat the event-loop tick
       // this write needed to drain, so a piped watcher sees the ping arrive after
       // runModeling's own [modeling] log lines instead of before them.
-      await new Promise((res) => process.stdout.write(`▶ Starting modeling loop (warm Claude process) for ${relative(cwd, kitDir)}...\n\n`, res));
+      await new Promise((res) => process.stdout.write(`▶ Starting modeling loop (warm Claude process) for ${relative(cwd, modelingKitDir)}...\n\n`, res));
       try {
-        await runModeling(kitDir, resolve(kitDir, '..'));
+        await runModeling(modelingKitDir, resolve(modelingKitDir, '..'));
       } catch (err) {
         console.error('[modeling] Fatal:', err);
         process.exit(1);
@@ -1249,10 +1255,15 @@ program
       return;
     }
 
-    if (isModelingKit) {
-      console.error(`❌ A modeling-kit install (${MODELING_KIT.kitDirName}/) only runs via \`eventmodelers run --modeling\` — there is no cold-spawn/tasks.json loop for modeling-only projects.`);
+    if (!buildKitDir) {
+      if (modelingKitDir) {
+        console.error(`❌ A modeling-kit install (${MODELING_KIT.kitDirName}/) only runs via \`eventmodelers run --modeling\` — there is no cold-spawn/tasks.json loop for modeling-only projects.`);
+      } else {
+        console.error(`❌ No kit installed in ${cwd} — run \`eventmodelers install\` first.`);
+      }
       process.exit(1);
     }
+    const kitDir = buildKitDir;
 
     const pickedCount = [opts.bash, opts.ollama].filter(Boolean).length;
     if (pickedCount > 1) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eventmodelers/cli",
-  "version": "0.0.20",
+  "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.