@eventmodelers/cli 1.0.110 → 1.0.111

package/cli.js

@@ -1949,7 +1949,7 @@ async function ensureGlobalKit(baseUrl) {
 // untargeted is handed straight back to the queue for another agent to take. It says
 // nothing about the standalone lane — a self-directed turn is nobody's task, so an
 // exclusive standalone agent still works the board on its own initiative.
-async function runModeling(kitDir, projectDir, { verbose = false, standalone = false, exclusive = false, worker = false, overrides = null, maxAgents = DEFAULT_MAX_AGENTS, identity = {}, localAi = null, exec = null, model = null } = {}) {
+async function runModeling(kitDir, projectDir, { codeDir = null, verbose = false, standalone = false, exclusive = false, worker = false, overrides = null, maxAgents = DEFAULT_MAX_AGENTS, identity = {}, localAi = null, exec = null, model = null } = {}) {
   // --worker: only prompts — no chat, and no board-change turns (it has nowhere to propose).
   const chat = !worker;
   const configLibPath = join(kitDir, 'lib', 'config.js');
@@ -2104,8 +2104,13 @@ async function runModeling(kitDir, projectDir, { verbose = false, standalone = f
 
   const claudeArgs = ['--dangerously-skip-permissions', '-p', '--input-format', 'stream-json', '--output-format', 'stream-json', '--verbose'];
   if (cfg.model) claudeArgs.push('--model', cfg.model);
+  // The global install runs in ~/.eventmodelers/kit, away from the code base the person started
+  // the agent in — hand that directory over so code-reading skills (detect-architecture-drift)
+  // can still see it.
+  if (codeDir) claudeArgs.push('--add-dir', codeDir);
   const claudeEnv = {
     ...process.env,
+    ...(codeDir ? { EVENTMODELERS_CODE_DIR: codeDir } : {}),
     ...(cfg.anthropicBaseUrl ? { ANTHROPIC_BASE_URL: cfg.anthropicBaseUrl } : {}),
     EVENTMODELERS_TOKEN: cfg.token,
     // What the connect skill puts in `.mcp.json`'s x-agent-id header and every curl-fallback
@@ -3762,7 +3767,9 @@ credentialFlags(program
       }
       let projectDir = kitDir ? resolve(kitDir, '..') : null;
       let overrides = null;
+      let codeDir = null;
       if (!kitDir) {
+        codeDir = cwd;
         // The blob and the individual flags are both "explicit", so they share a
         // precedence tier — with a single --token/--board-id winning, since overriding one
         // field of a pasted blob is the only reason to pass both.
@@ -3785,7 +3792,7 @@ credentialFlags(program
       const runnerLabel = modelingLocalAi ? 'local model' : opts.exec ? 'one agent process per turn' : 'warm Claude process';
       await new Promise((res) => process.stdout.write(`▶ Starting modeling loop (${runnerLabel}) for ${shown && !shown.startsWith('..') ? shown : kitDir}...\n\n`, res));
       try {
-        await runModeling(kitDir, projectDir, { verbose: !!opts.verbose, standalone: !!opts.standalone, exclusive: !!opts.exclusive, worker: !!opts.worker, overrides, maxAgents, identity, localAi: modelingLocalAi, exec: opts.exec ?? null, model: !opts.exec && modelingLocalAi === null ? model : null });
+        await runModeling(kitDir, projectDir, { codeDir, verbose: !!opts.verbose, standalone: !!opts.standalone, exclusive: !!opts.exclusive, worker: !!opts.worker, overrides, maxAgents, identity, localAi: modelingLocalAi, exec: opts.exec ?? null, model: !opts.exec && modelingLocalAi === null ? model : null });
       } catch (err) {
         console.error('[modeling] Fatal:', err);
         process.exit(1);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eventmodelers/cli",
-  "version": "1.0.110",
+  "version": "1.0.111",
   "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/shared/skills/learn-eventmodelers-api/SKILL.md

@@ -1121,7 +1121,8 @@ Rule of thumb: if you are about to write "Shall I…?", "Want me to…?", "A or
 { kind: 'code',    code: string, language?: string, title?: string }              // monospaced, with a copy button
 { kind: 'report',  chart: 'bar' | 'line' | 'pie', title?: string, unit?: string,
   labels: string[],                                                               // 1–50 points: x axis, or the pie slices
-  series: Array<{ name: string, values: number[] }> }                             // one number per label; bar/line up to 6 series, pie uses only the first (no negatives)
+  series: Array<{ name: string, values: number[] }>,                             // one number per label; bar/line up to 6 series, pie uses only the first (no negatives)
+  confirm?: { headline: string, yesLabel?: string, noLabel?: string } }          // optional yes/no question under the diagram, like a confirm snippet
 ```
 
 ### How to use them
@@ -1131,7 +1132,7 @@ Rule of thumb: if you are about to write "Shall I…?", "Want me to…?", "A or
 - **Name elements** with `nodeId` wherever you can (`tasks`, `changes`, `link`), so the person can click through to them — in a `tasks` list, put the element's name in `description` and its id in `nodeId`.
 - **Answers are text.** For a `tasks` answer, match the titles (or ids) back to your list; an element the person left unticked was declined, not forgotten. A `poll` option with a `message` of your own makes the answer unambiguous.
 - `get_chat_session` shows your snippet on the message as `snippet`, and the person's answer is the user message after it, carrying `context.snippetReply.messageId` (your message's id) — useful to tell an answer to a snippet from a new message.
-- **`report`** draws the numbers you send — it computes nothing, so aggregate first. A series whose length differs from `labels`, or a non-number, makes the whole snippet invisible. Keep `text` as a one-line summary of what the diagram shows.
+- **`report`** draws the numbers you send — it computes nothing, so aggregate first. A series whose length differs from `labels`, or a non-number, makes the whole snippet invisible. Keep `text` as a one-line summary of what the diagram shows. Add `confirm` when the diagram leads to a follow-up question ("Want me to look into the backward arrows?"): the answer comes back like a `confirm` answer, and without it the report is display only.
 - A snippet is shown exactly as you send it — keep secrets and tokens out of `code` and `image`.
 
 ---

package/stacks/modeling-kit/templates/.claude/skills/analyze-existing-model/SKILL.md

@@ -215,10 +215,12 @@ mcp__eventmodelers__post_chat_message {
   "snippet": {
     "kind": "report", "chart": "pie", "title": "Slices by status", "unit": "slices",
     "labels": ["Done", "InProgress", "Planned", "Blocked"],
-    "series": [{ "name": "Slices", "values": [12, 6, 4, 2] }]
+    "series": [{ "name": "Slices", "values": [12, 6, 4, 2] }],
+    "confirm": { "headline": "Want the full list of slices without scenarios?" }
   }
 }
 ```
+- `confirm` is optional: use it when you end on a follow-up question, instead of asking it in the text; the answer arrives as the person's next chat message.
 - Only statuses with at least one slice, one number per label — the chart draws exactly what you send, so count first.
 - One snippet per message: if the person asks for more diagrams (spec coverage, element inventory per type as a `bar`),
   answer each in its own reply.

package/stacks/modeling-kit/templates/.claude/skills/detect-architecture-drift/SKILL.md

@@ -7,7 +7,7 @@ description: Compare the event model on the board with the code in this reposito
 
 ## Step 0 — Is there a code base?
 
-Drift is the gap between the board and the code, so it can only be detected where code exists. **Before anything else — before `connect`, before reading the board — check that the current directory is a code base**: it contains source code (e.g. `src/`, `.build-kit/`, a `package.json`, `pom.xml`, `*.csproj`, `build.gradle`, or similar project files with slice/command/event/projection code).
+Drift is the gap between the board and the code, so it can only be detected where code exists. **Before anything else — before `connect`, before reading the board — resolve the directory to check**: `$EVENTMODELERS_CODE_DIR` if it is set (the agent runs from the global install and was started inside that directory — treat it as the repository root for every step below, not the current directory), otherwise the current directory. Check that it is a code base: it contains source code (e.g. `src/`, `.build-kit/`, a `package.json`, `pom.xml`, `*.csproj`, `build.gradle`, or similar project files with slice/command/event/projection code).
 
 If it is not (an empty folder, a modeling-only workspace holding just `.claude/`, `.eventmodelers/` or `.agent-modeling-kit/`), **stop and answer in one or two plain sentences**, e.g.:
 
@@ -58,7 +58,7 @@ Index the result in memory: per slice → commands, events, read models, screens
 
 ## Step 3 — Understand the code
 
-You are in a repository that may hold any stack. Find out which, don't assume.
+The code base is the directory resolved in Step 0 (`$EVENTMODELERS_CODE_DIR`, else the current directory) — every path below is relative to it, and it may hold any stack. Find out which, don't assume.
 
 1. Read `.build-kit/CLAUDE.md` (and `.build-kit/AGENTS.md` if present) — its *Structure* section says where slices live and how they're named (e.g. `src/slices/{slice}/` for Node, `src/main/java/.../slices/{context}/{slice}/` for Axon).
 2. If `.build-kit/.slices/<context>/<slice>/slice.json` exists, it is the snapshot the code was **last built from** — useful for telling "the code changed" apart from "the model changed since the build" (see Step 5).