@eventmodelers/cli 1.0.6 → 1.0.8

package/cli.js

@@ -1430,7 +1430,9 @@ async function runModeling(kitDir, projectDir, verbose = false) {
       log(`channel "${channelName}": ${status}`);
       if (status === 'SUBSCRIBED') drain().catch((err) => log(`initial drain error: ${err.message}`));
     },
-  );
+  ).catch((err) => {
+    log(`realtime subscribe failed, prompts won't be pushed live: ${err.message}`);
+  });
 
   setInterval(async () => {
     try {
@@ -1930,9 +1932,10 @@ program
   .command('fetch')
   .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)')
-  .option('--spec-kitty', "After fetching, also restate this context as a Spec Kitty mission brief (.kittify/mission-brief.md via `spec-kitty intake`) — deterministic, no LLM call, no mission/spec.md/tasks created. Run `/spec-kitty.specify` afterward to turn the brief into a mission. Requires `spec-kitty init` to already be set up in this project (see lib/adapters/spec-kitty-adapter.js). One-shot: does not start a loop.")
+  .option('--format <format>', 'Output format: json (default, builds the full .slices/ folder structure), yaml, textual, toon, emlang, or esdm (each of these five is dumped to a single .slices/<context>/slicedata.<ext> file instead)', 'json')
+  .option('--slice-id <id>', 'After fetching, print just the slice with this id (requires --format json)')
+  .option('--slice-title <title>', 'After fetching, print just the slice with this title, case-insensitive (requires --format json)')
+  .option('--spec-kitty', "After fetching, also restate this context as a Spec Kitty mission brief (.kittify/mission-brief.md via `spec-kitty intake`) — deterministic, no LLM call, no mission/spec.md/tasks created. Run `/spec-kitty.specify` afterward to turn the brief into a mission. Requires `spec-kitty init` to already be set up in this project (see lib/adapters/spec-kitty-adapter.js) and --format json. One-shot: does not start a loop.")
   .action(async (opts, command) => {
     const cwd = process.cwd();
     const kitDir = findInstalledKitDir(cwd);

package/lib/fetch.js

@@ -17,6 +17,14 @@ export class FetchAuthError extends Error {
 
 const UUID_RE = /^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$/i;
 
+// Mirrors the server's exporter registry (backend/src/slices/change/slicedata/exporters/
+// ExporterRegistry.ts) — json is the canonical shape (drives the full .slices/ folder
+// structure below); every other format is a transform of it and gets dumped as a single
+// file instead, so its extension reflects the transform's actual output, not its name
+// (textual is JSON-wrapped; emlang/esdm are YAML documents; toon is its own thing).
+const SUPPORTED_FORMATS = ['json', 'yaml', 'textual', 'toon', 'emlang', 'esdm'];
+const FORMAT_EXTENSIONS = { yaml: 'yaml', textual: 'json', toon: 'toon', emlang: 'yaml', esdm: 'yaml' };
+
 // `--context` accepts any of: a MODEL_CONTEXT name or id, or a timeline (CHAPTER) name or id.
 // /slicedata's contextId/contextName params now both resolve against MODEL_CONTEXT nodes first,
 // then timelines (id matched exactly, name case-insensitively) — including a timeline with no
@@ -72,7 +80,7 @@ export async function runFetch({ cwd, kitDir, cfg, opts = {} }) {
   // never "board not found". Only 401/403 are credential problems worth the
   // reconfigure-and-retry dance in cli.js; 404 gets reported and the process exits,
   // same as any other non-auth error.
-  async function fetchJson(url, what, { allow404 = false } = {}) {
+  async function fetchResponse(url, what, { allow404 = false } = {}) {
     let res;
     try {
       res = await fetch(url, { headers });
@@ -92,7 +100,19 @@ export async function runFetch({ cwd, kitDir, cfg, opts = {} }) {
       console.error(`❌ ${what}: HTTP ${res.status}`);
       process.exit(1);
     }
-    return res.json();
+    return res;
+  }
+
+  async function fetchJson(url, what, options) {
+    const res = await fetchResponse(url, what, options);
+    return res ? res.json() : res;
+  }
+
+  // Non-json formats aren't a {slices: [...]} payload — just the exporter's raw output
+  // (a YAML doc, a TOON encoding, ...) — so it's written straight to disk, not parsed.
+  async function fetchText(url, what, options) {
+    const res = await fetchResponse(url, what, options);
+    return res ? res.text() : res;
   }
 
   // Falls back to cwd when no kit is installed — fetch doesn't need kit-specific
@@ -100,6 +120,17 @@ export async function runFetch({ cwd, kitDir, cfg, opts = {} }) {
   const SLICES_DIR = join(kitDir || cwd, '.slices');
 
   const contextInput = opts.context;
+  const format = (opts.format || 'json').toLowerCase();
+  if (!SUPPORTED_FORMATS.includes(format)) {
+    console.error(`❌ Unsupported format "${format}". Supported: ${SUPPORTED_FORMATS.join(', ')}`);
+    process.exit(1);
+  }
+  // --slice-id/--slice-title/--spec-kitty all depend on the parsed {slices: [...]} list
+  // that only the json format produces — fail fast instead of silently ignoring them.
+  if (format !== 'json' && (opts.sliceId || opts.sliceTitle || opts.specKitty)) {
+    console.error('❌ --slice-id, --slice-title, and --spec-kitty require --format json (the default).');
+    process.exit(1);
+  }
 
   console.log(`▶ Fetching context "${contextInput}" from ${baseUrl} (board ${cfg.boardId})...`);
 
@@ -112,10 +143,25 @@ export async function runFetch({ cwd, kitDir, cfg, opts = {} }) {
   const contextQuery = UUID_RE.test(contextInput)
     ? `contextId=${encodeURIComponent(contextInput)}`
     : `contextName=${encodeURIComponent(contextInput)}`;
-  const payload = await fetchJson(
-    `${baseUrl}/api/org/${cfg.organizationId}/boards/${cfg.boardId}/slicedata?${contextQuery}`,
-    `slicedata?${contextQuery}`,
-  );
+  const url = `${baseUrl}/api/org/${cfg.organizationId}/boards/${cfg.boardId}/slicedata?${contextQuery}&format=${format}`;
+
+  // Only json builds the full .slices/<context>/<slice>/slice.json folder structure —
+  // every other format has no guaranteed {slices: [...]} shape to walk (it's the
+  // exporter's raw output: a YAML doc, a TOON encoding, ...), so it's just dumped
+  // as a single file. The resolved context name isn't known without parsing JSON,
+  // so the folder is slugified from the raw --context input instead.
+  if (format !== 'json') {
+    const body = await fetchText(url, `slicedata?${contextQuery}&format=${format}`);
+    const contextSlug = slugify(contextInput) || 'default';
+    const baseFolder = join(SLICES_DIR, contextSlug);
+    mkdirSync(baseFolder, { recursive: true });
+    const outFile = join(baseFolder, `slicedata.${FORMAT_EXTENSIONS[format]}`);
+    writeFileSync(outFile, body);
+    console.log(`✅ Fetched context "${contextInput}" as ${format} → ${relative(cwd, outFile)}`);
+    return;
+  }
+
+  const payload = await fetchJson(url, `slicedata?${contextQuery}&format=${format}`);
   const { slices: allSlices } = payload;
   const displayContext = allSlices[0]?.context || contextInput;
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eventmodelers/cli",
-  "version": "1.0.6",
+  "version": "1.0.8",
   "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/shared/build-kit/lib/adapters/pocketbase-realtime-adapter.js

@@ -7,6 +7,15 @@
 
 const REALTIME_EVENTS_COLLECTION = 'realtime_events';
 
+// Same backoff steps the PocketBase SDK uses for its own reconnects (see
+// predefinedReconnectIntervals in the SDK) — reused here because the SDK only
+// applies that backoff to a connection that drops *after* it was established.
+// A failed first handshake (e.g. "Invalid realtime client" from the initial
+// GET /api/realtime and the follow-up subscribe POST landing on different
+// backend instances) rejects immediately with no retry at all, so we retry it
+// ourselves.
+const RECONNECT_INTERVALS_MS = [200, 300, 500, 1000, 1200, 1500, 2000];
+
 export async function createPocketBaseRealtimeAdapter(cfg, initialToken) {
   const { EventSource } = await import('eventsource');
   if (!globalThis.EventSource) globalThis.EventSource = EventSource; // PocketBase's SDK assumes a browser-style global
@@ -16,11 +25,20 @@ export async function createPocketBaseRealtimeAdapter(cfg, initialToken) {
 
   return {
     async subscribe(topic, handlers, onStatus) {
-      await pb.collection(REALTIME_EVENTS_COLLECTION).subscribe('*', (e) => {
-        if (e.action !== 'create' || e.record.topic !== topic) return;
-        handlers[e.record.event]?.(e.record.payload);
-      });
-      onStatus?.('SUBSCRIBED');
+      for (let attempt = 0; ; attempt++) {
+        try {
+          await pb.collection(REALTIME_EVENTS_COLLECTION).subscribe('*', (e) => {
+            if (e.action !== 'create' || e.record.topic !== topic) return;
+            handlers[e.record.event]?.(e.record.payload);
+          });
+          onStatus?.('SUBSCRIBED');
+          return;
+        } catch (err) {
+          if (attempt >= RECONNECT_INTERVALS_MS.length) throw err;
+          onStatus?.(`RECONNECTING (attempt ${attempt + 1}/${RECONNECT_INTERVALS_MS.length}): ${err.message}`);
+          await new Promise((resolve) => setTimeout(resolve, RECONNECT_INTERVALS_MS[attempt]));
+        }
+      }
     },
     setAuth(token) {
       pb.authStore.save(token, null);