@eventmodelers/cli 0.0.26 → 0.0.28

package/README.md

@@ -225,9 +225,9 @@ npx @eventmodelers/cli run --ollama                 # same, via local Ollama (ra
 npx @eventmodelers/cli run --bash                   # bash-only loop, no realtime (ralph.sh)
 npx @eventmodelers/cli listen                       # start the code-export listener (code-export.mjs) from the installed kit dir
 npx @eventmodelers/cli listen --port 4000           # same, on a different port
-npx @eventmodelers/cli fetch                        # pull full slice detail from every context on the board into <kit-dir>/.slices/
-npx @eventmodelers/cli fetch --slice-id <id>        # same, then print just that slice
-npx @eventmodelers/cli fetch --slice-title <title>  # same, then print just the slice matching this title
+npx @eventmodelers/cli fetch --context <name>                     # pull full slice detail for one context on the board into <kit-dir>/.slices/ (project root if no kit, or a modeling-kit, is installed)
+npx @eventmodelers/cli fetch --context <name> --slice-id <id>     # same, then print just that slice
+npx @eventmodelers/cli fetch --context <name> --slice-title <title> # same, then print just the slice matching this title
 npx @eventmodelers/cli stacks                       # list available stacks
 npx @eventmodelers/cli status                       # check what's installed
 npx @eventmodelers/cli config                       # print the fully resolved config (file + env), token masked
@@ -238,7 +238,7 @@ npx @eventmodelers/cli uninstall                    # remove everything init/ini
 
 `listen` is the same kind of dispatcher, but for `<kit-dir>/code-export.mjs` — a local HTTP server (port 3001 by default) that the eventmodelers board UI posts slice/screen data to, which then gets written under `<kit-dir>/.slices/`.
 
-`fetch` is the pull-based counterpart to `listen`: instead of waiting for the board UI to push data to a running listener, it lists every `MODEL_CONTEXT` node on the board, calls `slicedata?contextId=<id>` for each (full slice detail — commands/events/readmodels/screens/processors/specifications/comments), and writes the same `.slices/<context>/<slice>/slice.json`, `index.json`, and `context.json` layout — useful in CI or any context where nothing is listening on a port. It does not fetch screen images (those only arrive via `listen`'s push). If credentials are missing, it prompts the same way `init-config` does. `--slice-id`/`--slice-title` still fetch and persist everything, then just print the one you asked about.
+`fetch` is the pull-based counterpart to `listen`: instead of waiting for the board UI to push data to a running listener, it calls `slicedata?contextName=<name>` for the required `--context` (full slice detail — commands/events/readmodels/screens/processors/specifications/comments), and writes the same `.slices/<context>/<slice>/slice.json`, `index.json`, and `context.json` layout — useful in CI or any context where nothing is listening on a port. It does not fetch screen images (those only arrive via `listen`'s push). Unlike every other command, `fetch` also works with no kit installed at all — it only needs credentials, not kit-specific files — and, unique to modeling-kit, writes `.slices/` to the project root instead of nesting it under `.agent-modeling-kit/`, since nothing reads it from there (modeling-kit has no `code-export.mjs`/`listen`). If credentials are missing, it prompts the same way `init-config` does. `--slice-id`/`--slice-title` still fetch and persist the whole context, then just print the one slice you asked about.
 
 ### Uninstall
 

package/cli.js

@@ -734,8 +734,15 @@ async function configureCredentials({ config, configPath, targetDir, requiredFie
   }
 
   const stillMissing = force || requiredFields.some((f) => !config[f]);
+  // Sole gate on the persist step below — 'instructions'/'skip' and a paste that
+  // couldn't be parsed all explicitly tell the user nothing was saved, so the
+  // final write must not run for them (it used to run unconditionally, silently
+  // writing out whatever `config` happened to be — `{}` on a first run — which
+  // contradicted those messages and left behind a bogus config.json).
+  let skipWrite = false;
   if (stillMissing && print) {
     console.log('\n  ℹ️  --print — skipping credential prompt, missing fields must be set via flags, EVENTMODELERS_* env vars, or config.json');
+    skipWrite = true;
   } else if (stillMissing) {
     const choice = await selectPrompt('How do you want to configure credentials?', [
       { label: 'Paste values copied from app.eventmodelers.ai/account', value: 'paste' },
@@ -751,12 +758,10 @@ async function configureCredentials({ config, configPath, targetDir, requiredFie
       const parsed = parseCredentialsPaste(pasted, requiredFields);
       if (parsed) {
         config = { ...config, ...parsed };
-        if (!config.baseUrl) config.baseUrl = DEFAULT_BASE_URL;
-        writeFileSync(configPath, JSON.stringify(config, null, 2));
-        console.log(`\n  ✓ Saved to ${relative(targetDir, configPath)}`);
       } else {
         console.log(`\n  ⚠️  Couldn't make sense of that paste — nothing was saved.`);
         console.log(`      Paste it into ${relative(targetDir, configPath)} yourself, or use /connect later.`);
+        skipWrite = true;
       }
     } else if (choice === 'manual') {
       console.log('\n🔑 Enter your Eventmodelers credentials:\n');
@@ -766,9 +771,6 @@ async function configureCredentials({ config, configPath, targetDir, requiredFie
       const boardId = await prompt(`  Board ID${boardIdOptional ? ' (optional)' : ''}: `);
       if (boardId) config.boardId = boardId;
       config.token = await prompt('  Token:           ');
-      if (!config.baseUrl) config.baseUrl = DEFAULT_BASE_URL;
-      writeFileSync(configPath, JSON.stringify(config, null, 2));
-      console.log(`\n  ✓ Credentials saved to ${relative(targetDir, configPath)}`);
     } else if (choice === 'instructions') {
       console.log(`\n  Paste your credentials into:\n`);
       console.log(`    ${configPath}`);
@@ -778,8 +780,10 @@ async function configureCredentials({ config, configPath, targetDir, requiredFie
       const sample = `  {\n    "token": "...",\n    "boardId": "...",\n    "organizationId": "...",\n    "baseUrl": "https://api.eventmodelers.ai"\n  }\n`;
       console.log(sample);
       console.log('  Then re-run this installer, or just run the agent afterwards.\n');
+      skipWrite = true;
     } else {
       console.log('\n  ℹ️  Skipped — use /connect in Claude Code to add credentials later');
+      skipWrite = true;
     }
   } else {
     console.log('\n  ✓ Config already present — skipping credential prompt');
@@ -791,8 +795,10 @@ async function configureCredentials({ config, configPath, targetDir, requiredFie
     config.baseUrl = DEFAULT_BASE_URL;
   }
 
-  writeFileSync(configPath, JSON.stringify(config, null, 2));
-  console.log(`\n  ✓ Saved to ${relative(targetDir, configPath)}`);
+  if (!skipWrite) {
+    writeFileSync(configPath, JSON.stringify(config, null, 2));
+    console.log(`\n  ✓ Saved to ${relative(targetDir, configPath)}`);
+  }
   return config;
 }
 
@@ -1457,12 +1463,19 @@ program
 
 program
   .command('fetch')
-  .description('Pull full slice detail from every context on the board via the slicedata API and write it into .slices/ — the pull-based counterpart to `listen`, without screen images')
+  .description('Pull full slice detail for one context on the board via the slicedata API and write it into .slices/ — the pull-based counterpart to `listen`, without screen images')
+  .requiredOption('--context <name>', 'Name of the MODEL_CONTEXT to fetch')
   .option('--slice-id <id>', 'After fetching, print just the slice with this id')
   .option('--slice-title <title>', 'After fetching, print just the slice with this title (case-insensitive)')
   .action(async (opts, command) => {
     const cwd = process.cwd();
     const kitDir = findInstalledKitDir(cwd);
+    // modeling-kit has no code-export.mjs (useShared:false, no `listen`) and no
+    // skill reads a nested .agent-modeling-kit/.slices/ — so nothing expects fetch's
+    // output there either. Every other kit dir does have a code-export.mjs that
+    // hardcodes its .slices/ next to itself, so those still nest to stay
+    // interchangeable with what `listen` produces.
+    const slicesKitDir = kitDir?.endsWith(MODELING_KIT.kitDirName) ? null : kitDir;
     const globalOpts = command.optsWithGlobals();
     const explicitConfig = globalOpts.config;
     const effective = loadEffectiveConfig(cwd, kitDir, explicitConfig);
@@ -1496,7 +1509,7 @@ program
     if (requiredFields.some((f) => !cfg[f])) await promptForCredentials();
 
     try {
-      await runFetch({ cwd, kitDir, cfg, opts });
+      await runFetch({ cwd, kitDir: slicesKitDir, cfg, opts });
     } catch (err) {
       if (!(err instanceof FetchAuthError)) throw err;
       // Present but wrong, not missing — the connect skill's Step 4 (Verify) treats
@@ -1506,7 +1519,7 @@ program
       if (err.status === 404) delete cfg.boardId;
       else delete cfg.token;
       await promptForCredentials();
-      await runFetch({ cwd, kitDir, cfg, opts });
+      await runFetch({ cwd, kitDir: slicesKitDir, cfg, opts });
     }
   });
 

package/lib/fetch.js

@@ -45,11 +45,13 @@ function sliceFolderName(title) {
   return (title ?? '').replaceAll(' ', '').replaceAll('slice:', '').toLowerCase();
 }
 
-// Pulls full slice detail from every context on a board and writes it into
+// Pulls full slice detail from a single context on a board and writes it into
 // .slices/, mirroring the layout code-export.mjs's /api/generate handler produces
 // (minus screen images, which only ever arrive via that push-based listener).
 //
-// { cwd, kitDir, cfg: { token, organizationId, boardId, baseUrl }, opts: { sliceId?, sliceTitle? } }
+// kitDir here is null for modeling-kit (see cli.js's fetch action) — nothing
+// nests .slices/ under .agent-modeling-kit/, so it lands at cwd instead.
+// { cwd, kitDir, cfg: { token, organizationId, boardId, baseUrl }, opts: { context, sliceId?, sliceTitle? } }
 export async function runFetch({ cwd, kitDir, cfg, opts = {} }) {
   const baseUrl = cfg.baseUrl || DEFAULT_BASE_URL;
   const headers = { 'x-token': cfg.token, 'x-board-id': cfg.boardId, 'x-user-id': 'cli-fetch' };
@@ -72,51 +74,42 @@ export async function runFetch({ cwd, kitDir, cfg, opts = {} }) {
     return res.json();
   }
 
-  console.log(`▶ Fetching slices from ${baseUrl} (board ${cfg.boardId})...`);
+  console.log(`▶ Fetching context "${opts.context}" from ${baseUrl} (board ${cfg.boardId})...`);
 
-  // No dedicated "list contexts" endpoint — MODEL_CONTEXT nodes are the contexts,
-  // same as how the connect skill lists CHAPTER nodes for its health check.
-  const contextNodes = await fetchJson(
-    `${baseUrl}/api/org/${cfg.organizationId}/boards/${cfg.boardId}/nodes?type=MODEL_CONTEXT`,
-    'nodes?type=MODEL_CONTEXT',
-  );
-  if (!contextNodes?.length) {
-    console.log('ℹ️  No contexts found on this board.');
-    return;
-  }
+  // Falls back to cwd when no kit is installed — fetch doesn't need kit-specific
+  // files, just somewhere to write .slices/.
+  const SLICES_DIR = join(kitDir || cwd, '.slices');
 
   // /slicedata (buildSliceData) is per-context and returns full slice detail —
-  // commands/events/readmodels/screens/processors/specifications/comments — unlike
-  // the lightweight /slicedata/slices summary. There's no "all contexts in one
-  // call" variant, so fetch each context's full data and merge client-side.
-  const allSlices = [];
-  for (const node of contextNodes) {
-    const contextName = node.meta?.title ?? node.node?.data?.title ?? '';
-    // contextId is the normal path (we already have the node id); contextName is
-    // the fallback the endpoint itself supports when an id can't be resolved.
-    const contextQuery = node.id ? `contextId=${encodeURIComponent(node.id)}` : `contextName=${encodeURIComponent(contextName)}`;
-    const { slices } = await fetchJson(
-      `${baseUrl}/api/org/${cfg.organizationId}/boards/${cfg.boardId}/slicedata?${contextQuery}`,
-      `slicedata?${contextQuery}`,
-    );
-    allSlices.push(...slices);
+  // commands/events/readmodels/screens/processors/specifications/comments. It
+  // resolves contextName by exact match, so no separate "list contexts" lookup
+  // is needed first.
+  const contextQuery = `contextName=${encodeURIComponent(opts.context)}`;
+  const payload = await fetchJson(
+    `${baseUrl}/api/org/${cfg.organizationId}/boards/${cfg.boardId}/slicedata?${contextQuery}`,
+    `slicedata?${contextQuery}`,
+  );
+  const { slices: allSlices } = payload;
+
+  if (allSlices.length) {
+    // Mirrors code-export.mjs's /api/generate: a raw per-context payload dump at
+    // .slices/<context>/config.json, alongside the per-slice output below — kept
+    // for parity with `listen` even though nothing in this repo reads it back.
+    const contextSlug = slugify(allSlices[0]?.context || opts.context || 'default') || 'default';
+    const baseFolder = join(SLICES_DIR, contextSlug);
+    mkdirSync(baseFolder, { recursive: true });
+    writeFileSync(join(baseFolder, 'config.json'), JSON.stringify(payload, null, 2));
   }
 
   if (!allSlices.length) {
-    console.log('ℹ️  No slices found on this board.');
+    console.log(`ℹ️  No slices found in context "${opts.context}".`);
     return;
   }
 
-  // Falls back to cwd when no kit is installed — fetch doesn't need kit-specific
-  // files, just somewhere to write .slices/.
-  const SLICES_DIR = join(kitDir || cwd, '.slices');
-  const contextNames = new Set();
-
   for (const slice of allSlices) {
     // buildSliceData names this field `context`, not `contextName` (that's the
     // /slicedata/slices summary endpoint's field) — read the one this endpoint sends.
-    const contextName = slice.context || 'default';
-    contextNames.add(contextName);
+    const contextName = slice.context || opts.context || 'default';
     const contextSlug = slugify(contextName) || 'default';
     const baseFolder = join(SLICES_DIR, contextSlug);
     const sliceFolder = sliceFolderName(slice.title);
@@ -151,14 +144,9 @@ export async function runFetch({ cwd, kitDir, cfg, opts = {} }) {
     writeFileSync(indexFile, JSON.stringify(sliceIndices, null, 2));
   }
 
-  // A single shared current_context.json only makes sense when everything fetched
-  // belongs to one context — with several, any one choice would be arbitrary, so
-  // leave whatever `listen`/a prior fetch already wrote there untouched.
-  if (contextNames.size === 1) {
-    writeFileSync(join(SLICES_DIR, 'current_context.json'), JSON.stringify({ name: [...contextNames][0] }, null, 2));
-  }
+  writeFileSync(join(SLICES_DIR, 'current_context.json'), JSON.stringify({ name: opts.context }, null, 2));
 
-  console.log(`✅ Fetched ${allSlices.length} slice${allSlices.length === 1 ? '' : 's'} across ${contextNames.size} context${contextNames.size === 1 ? '' : 's'} → ${relative(cwd, SLICES_DIR)}/`);
+  console.log(`✅ Fetched ${allSlices.length} slice${allSlices.length === 1 ? '' : 's'} from context "${opts.context}" → ${relative(cwd, SLICES_DIR)}/`);
 
   // --slice-id/--slice-title mirror load-slice's Step 4/5 — fetch+persist everything
   // regardless, then just report the one the caller asked about.

package/package.json

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