@eventmodelers/cli 1.0.141 → 1.0.142

package/cli.js

@@ -4101,7 +4101,7 @@ program
 
 program
   .command('activate-context')
-  .description('Choose which fetched context is active — writes .slices/current_context.json, which `run`/bridge/listen treat as sticky and never cross out of on their own')
+  .description('Choose which fetched context is active — writes .slices/current_context.json, which `run` works through first; once it has no planned slices left, `run` moves on to the next context that does')
   .action(async () => {
     const cwd = process.cwd();
     const kitDir = findInstalledKitDir(cwd);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eventmodelers/cli",
-  "version": "1.0.141",
+  "version": "1.0.142",
   "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/build-kit/lib/ralph.js

@@ -232,9 +232,8 @@ async function fetchAndPersistSlices(cfg, kitDir) {
     contexts[contextSlug].slices.push(slice);
   }
 
-  // current_context.json is STICKY. We work within ONE context at a time and must
-  // not auto-jump to another context just because it happens to have planned work.
-  // Keep the existing context if it still exists; only seed it when absent or stale.
+  // current_context.json is the context being worked on. Keep it here while it exists; the
+  // run loop (getFirstPlannedSlice) advances it when that context has no planned work left.
   const ctxPath = join(slicesDir, 'current_context.json');
   let activeCtx = null;
   if (existsSync(ctxPath)) {
@@ -563,19 +562,32 @@ function readTicketNumber(kitDir, ctx, folder) {
   }
 }
 
-// Returns the first Planned slice IN THE CURRENT CONTEXT ONLY. If the current
-// context has no planned work, returns null so the loop waits — it must NEVER
-// cross into another context to find something to build.
+// Returns the first Planned slice, preferring the current context so a context is finished
+// before the next one starts. When the current context has no planned work, the first other
+// context that does becomes the current one (current_context.json is rewritten), so a slice
+// set to Planned in any context is eventually built.
 function getFirstPlannedSlice(kitDir) {
+  const slicesDir = join(kitDir, '.slices');
   const currentCtx = readCurrentContext(kitDir);
-  if (!currentCtx) return null;
-  const indexPath = join(kitDir, '.slices', currentCtx, 'index.json');
-  if (!existsSync(indexPath)) return null;
+  let others = [];
   try {
-    const { slices } = JSON.parse(readFileSync(indexPath, 'utf-8'));
-    const planned = slices && slices.find((s) => (s.status || '').toLowerCase() === 'planned');
-    if (planned) return { id: planned.id ?? null, title: planned.slice || planned.id || null, ctx: currentCtx, ticketNumber: readTicketNumber(kitDir, currentCtx, planned.folder) };
+    others = readdirSync(slicesDir, { withFileTypes: true }).filter((d) => d.isDirectory()).map((d) => d.name).sort();
   } catch {}
+  const candidates = [...(currentCtx ? [currentCtx] : []), ...others.filter((c) => c !== currentCtx)];
+  for (const ctx of candidates) {
+    const indexPath = join(slicesDir, ctx, 'index.json');
+    if (!existsSync(indexPath)) continue;
+    try {
+      const { slices } = JSON.parse(readFileSync(indexPath, 'utf-8'));
+      const planned = slices && slices.find((s) => (s.status || '').toLowerCase() === 'planned');
+      if (!planned) continue;
+      if (ctx !== currentCtx) {
+        writeFileSync(join(slicesDir, 'current_context.json'), JSON.stringify({ name: ctx }, null, 2), 'utf-8');
+        console.log(`[ralph] No planned slices in context "${currentCtx}" — switching to "${ctx}".`);
+      }
+      return { id: planned.id ?? null, title: planned.slice || planned.id || null, ctx, ticketNumber: readTicketNumber(kitDir, ctx, planned.folder) };
+    } catch {}
+  }
   return null;
 }
 
@@ -755,10 +767,10 @@ async function ralphLoop(kitDir, cfg, onTask, onPlannedSlice, localOnly = false)
     }
 
     if (!didWork) {
-      // No planned work in the current context — wait, do NOT switch contexts.
+      // No planned work in any context — wait.
       const ctx = readCurrentContext(kitDir);
       if (ctx !== lastIdleCtx) {
-        console.log(`[ralph] No planned slices in current context "${ctx}" — waiting. Switch context on the board to continue.`);
+        console.log(`[ralph] No planned slices in any context — waiting.`);
         lastIdleCtx = ctx;
       }
       await sleep(10_000);

package/stacks/axon/templates/build-kit/lib/backend-prompt.md

@@ -6,12 +6,12 @@ The structure defined in the Project-Skills is relevant.
 
 ## Context Boundary (READ FIRST — NON-NEGOTIABLE)
 
-You work within **exactly ONE context at a time** — the one named in `.build-kit/.slices/current_context.json`.
+You work within **exactly ONE context at a time** — the one named in `.build-kit/.slices/current_context.json` (the runner picks it).
 
 - **ONLY** look for and build slices inside `.build-kit/.slices/<currentContext>/`.
 - **NEVER** read, scan, or build slices from any other context directory, even if it has "Planned" slices, and even if the current context has no work left.
 - A "Planned" slice in a *different* context (e.g. "Rename organization" while you are in "Board Invitations") is **NOT yours to build**. Ignore it completely.
-- If the current context has no "Planned" slice, you are **done for this iteration** — reply `<promise>NO_TASKS</promise>` and stop. Do not go looking elsewhere. The context is only ever changed on the board, never by you.
+- If the current context has no "Planned" slice, you are **done for this iteration** — reply `<promise>NO_TASKS</promise>` and stop. Do not go looking elsewhere. The runner moves `current_context.json` on to the next context with planned work between iterations — never change it yourself.
 
 ## Your Task
 

package/stacks/blank/templates/build-kit/lib/backend-prompt.md

@@ -6,12 +6,12 @@ The structure defined in the Project-Skills is relevant.
 
 ## Context Boundary (READ FIRST — NON-NEGOTIABLE)
 
-You work within **exactly ONE context at a time** — the one named in `.build-kit/.slices/current_context.json`.
+You work within **exactly ONE context at a time** — the one named in `.build-kit/.slices/current_context.json` (the runner picks it).
 
 - **ONLY** look for and build slices inside `.build-kit/.slices/<currentContext>/`.
 - **NEVER** read, scan, or build slices from any other context directory, even if it has "Planned" slices, and even if the current context has no work left.
 - A "Planned" slice in a *different* context is **NOT yours to build**. Ignore it completely.
-- If the current context has no "Planned" slice, you are **done for this iteration** — reply `<promise>NO_TASKS</promise>` and stop. Do not go looking elsewhere. The context is only ever changed on the board, never by you.
+- If the current context has no "Planned" slice, you are **done for this iteration** — reply `<promise>NO_TASKS</promise>` and stop. Do not go looking elsewhere. The runner moves `current_context.json` on to the next context with planned work between iterations — never change it yourself.
 
 ## Your Task
 

package/stacks/classic/templates/build-kit/lib/backend-prompt.md

@@ -8,13 +8,13 @@ Usually this is a legacy system being extended: the event model was built from t
 
 ## Context Boundary (READ FIRST — NON-NEGOTIABLE)
 
-You work within **exactly ONE context at a time** — the one named in `.build-kit/.slices/current_context.json`.
+You work within **exactly ONE context at a time** — the one named in `.build-kit/.slices/current_context.json` (the runner picks it).
 
 - **ONLY** look for and build slices inside `.build-kit/.slices/<currentContext>/`.
 - **NEVER** read, scan, or build slices from any other context directory, even if it has "Planned" slices, and even if the current context has no work left.
 - A "Planned" slice in a *different* context is **NOT yours to build**. Ignore it completely.
 - The one exception is **reading** `Done` slices of other contexts as precedents (through the Slice map in `ARCHITECTURE.md`, or by `/learn-architecture` building that map) — they show how the codebase builds things, they are never built.
-- If the current context has no "Planned" slice, you are **done for this iteration** — reply `<promise>NO_TASKS</promise>` and stop. Do not go looking elsewhere. The context is only ever changed on the board, never by you.
+- If the current context has no "Planned" slice, you are **done for this iteration** — reply `<promise>NO_TASKS</promise>` and stop. Do not go looking elsewhere. The runner moves `current_context.json` on to the next context with planned work between iterations — never change it yourself.
 
 ## Your Task
 

package/stacks/kurrent/templates/build-kit/lib/backend-prompt.md

@@ -6,12 +6,12 @@ The structure defined in the Project-Skills is relevant.
 
 ## Context Boundary (READ FIRST — NON-NEGOTIABLE)
 
-You work within **exactly ONE context at a time** — the one named in `.build-kit/.slices/current_context.json`.
+You work within **exactly ONE context at a time** — the one named in `.build-kit/.slices/current_context.json` (the runner picks it).
 
 - **ONLY** look for and build slices inside `.build-kit/.slices/<currentContext>/`.
 - **NEVER** read, scan, or build slices from any other context directory, even if it has "Planned" slices, and even if the current context has no work left.
 - A "Planned" slice in a *different* context (e.g. "Rename organization" while you are in "Board Invitations") is **NOT yours to build**. Ignore it completely.
-- If the current context has no "Planned" slice, you are **done for this iteration** — reply `<promise>NO_TASKS</promise>` and stop. Do not go looking elsewhere. The context is only ever changed on the board, never by you.
+- If the current context has no "Planned" slice, you are **done for this iteration** — reply `<promise>NO_TASKS</promise>` and stop. Do not go looking elsewhere. The runner moves `current_context.json` on to the next context with planned work between iterations — never change it yourself.
 
 ## Your Task
 

package/stacks/node/templates/build-kit/lib/backend-prompt.md

@@ -6,12 +6,12 @@ The structure defined in the Project-Skills is relevant.
 
 ## Context Boundary (READ FIRST — NON-NEGOTIABLE)
 
-You work within **exactly ONE context at a time** — the one named in `.build-kit/.slices/current_context.json`.
+You work within **exactly ONE context at a time** — the one named in `.build-kit/.slices/current_context.json` (the runner picks it).
 
 - **ONLY** look for and build slices inside `.build-kit/.slices/<currentContext>/`.
 - **NEVER** read, scan, or build slices from any other context directory, even if it has "Planned" slices, and even if the current context has no work left.
 - A "Planned" slice in a *different* context (e.g. "Rename organization" while you are in "Board Invitations") is **NOT yours to build**. Ignore it completely.
-- If the current context has no "Planned" slice, you are **done for this iteration** — reply `<promise>NO_TASKS</promise>` and stop. Do not go looking elsewhere. The context is only ever changed on the board, never by you.
+- If the current context has no "Planned" slice, you are **done for this iteration** — reply `<promise>NO_TASKS</promise>` and stop. Do not go looking elsewhere. The runner moves `current_context.json` on to the next context with planned work between iterations — never change it yourself.
 
 ## Your Task
 

package/stacks/opencqrs/templates/build-kit/lib/backend-prompt.md

@@ -6,12 +6,12 @@ The structure defined in the Project-Skills is relevant.
 
 ## Context Boundary (READ FIRST — NON-NEGOTIABLE)
 
-You work within **exactly ONE context at a time** — the one named in `.build-kit/.slices/current_context.json`.
+You work within **exactly ONE context at a time** — the one named in `.build-kit/.slices/current_context.json` (the runner picks it).
 
 - **ONLY** look for and build slices inside `.build-kit/.slices/<currentContext>/`.
 - **NEVER** read, scan, or build slices from any other context directory, even if it has "Planned" slices, and even if the current context has no work left.
 - A "Planned" slice in a *different* context (e.g. "Rename organization" while you are in "Board Invitations") is **NOT yours to build**. Ignore it completely.
-- If the current context has no "Planned" slice, you are **done for this iteration** — reply `<promise>NO_TASKS</promise>` and stop. Do not go looking elsewhere. The context is only ever changed on the board, never by you.
+- If the current context has no "Planned" slice, you are **done for this iteration** — reply `<promise>NO_TASKS</promise>` and stop. Do not go looking elsewhere. The runner moves `current_context.json` on to the next context with planned work between iterations — never change it yourself.
 
 ## Your Task
 

package/stacks/react/templates/build-kit/lib/backend-prompt.md

@@ -6,12 +6,12 @@ The structure defined in the Project-Skills is relevant.
 
 ## Context Boundary (READ FIRST — NON-NEGOTIABLE)
 
-You work within **exactly ONE context at a time** — the one named in `.build-kit/.slices/current_context.json`.
+You work within **exactly ONE context at a time** — the one named in `.build-kit/.slices/current_context.json` (the runner picks it).
 
 - **ONLY** look for and build slices inside `.build-kit/.slices/<currentContext>/`.
 - **NEVER** read, scan, or build slices from any other context directory, even if it has "Planned" slices, and even if the current context has no work left.
 - A "Planned" slice in a *different* context is **NOT yours to build**. Ignore it completely.
-- If the current context has no "Planned" slice, you are **done for this iteration** — reply `<promise>NO_TASKS</promise>` and stop. Do not go looking elsewhere. The context is only ever changed on the board, never by you.
+- If the current context has no "Planned" slice, you are **done for this iteration** — reply `<promise>NO_TASKS</promise>` and stop. Do not go looking elsewhere. The runner moves `current_context.json` on to the next context with planned work between iterations — never change it yourself.
 
 ## Your Task
 

package/stacks/supabase/templates/build-kit/lib/backend-prompt.md

@@ -6,12 +6,12 @@ The structure defined in the Project-Skills is relevant.
 
 ## Context Boundary (READ FIRST — NON-NEGOTIABLE)
 
-You work within **exactly ONE context at a time** — the one named in `.build-kit/.slices/current_context.json`.
+You work within **exactly ONE context at a time** — the one named in `.build-kit/.slices/current_context.json` (the runner picks it).
 
 - **ONLY** look for and build slices inside `.build-kit/.slices/<currentContext>/`.
 - **NEVER** read, scan, or build slices from any other context directory, even if it has "Planned" slices, and even if the current context has no work left.
 - A "Planned" slice in a *different* context (e.g. "Rename organization" while you are in "Board Invitations") is **NOT yours to build**. Ignore it completely.
-- If the current context has no "Planned" slice, you are **done for this iteration** — reply `<promise>NO_TASKS</promise>` and stop. Do not go looking elsewhere. The context is only ever changed on the board, never by you.
+- If the current context has no "Planned" slice, you are **done for this iteration** — reply `<promise>NO_TASKS</promise>` and stop. Do not go looking elsewhere. The runner moves `current_context.json` on to the next context with planned work between iterations — never change it yourself.
 
 ## Your Task
 

package/stacks/supabase-react/templates/build-kit/lib/backend-prompt.md

@@ -6,12 +6,12 @@ The structure defined in the Project-Skills is relevant.
 
 ## Context Boundary (READ FIRST — NON-NEGOTIABLE)
 
-You work within **exactly ONE context at a time** — the one named in `.build-kit/.slices/current_context.json`.
+You work within **exactly ONE context at a time** — the one named in `.build-kit/.slices/current_context.json` (the runner picks it).
 
 - **ONLY** look for and build slices inside `.build-kit/.slices/<currentContext>/`.
 - **NEVER** read, scan, or build slices from any other context directory, even if it has "Planned" slices, and even if the current context has no work left.
 - A "Planned" slice in a *different* context is **NOT yours to build**. Ignore it completely.
-- If the current context has no "Planned" slice, you are **done for this iteration** — reply `<promise>NO_TASKS</promise>` and stop. Do not go looking elsewhere. The context is only ever changed on the board, never by you.
+- If the current context has no "Planned" slice, you are **done for this iteration** — reply `<promise>NO_TASKS</promise>` and stop. Do not go looking elsewhere. The runner moves `current_context.json` on to the next context with planned work between iterations — never change it yourself.
 
 ## Your Task
 

package/stacks/umadb/templates/build-kit/lib/backend-prompt.md

@@ -6,12 +6,12 @@ The structure defined in the Project-Skills is relevant.
 
 ## Context Boundary (READ FIRST — NON-NEGOTIABLE)
 
-You work within **exactly ONE context at a time** — the one named in `.build-kit/.slices/current_context.json`.
+You work within **exactly ONE context at a time** — the one named in `.build-kit/.slices/current_context.json` (the runner picks it).
 
 - **ONLY** look for and build slices inside `.build-kit/.slices/<currentContext>/`.
 - **NEVER** read, scan, or build slices from any other context directory, even if it has "Planned" slices, and even if the current context has no work left.
 - A "Planned" slice in a *different* context (e.g. "Rename organization" while you are in "Board Invitations") is **NOT yours to build**. Ignore it completely.
-- If the current context has no "Planned" slice, you are **done for this iteration** — reply `<promise>NO_TASKS</promise>` and stop. Do not go looking elsewhere. The context is only ever changed on the board, never by you.
+- If the current context has no "Planned" slice, you are **done for this iteration** — reply `<promise>NO_TASKS</promise>` and stop. Do not go looking elsewhere. The runner moves `current_context.json` on to the next context with planned work between iterations — never change it yourself.
 
 ## Your Task