keystone-cli 1.0.0 → 1.0.2

package/README.md

@@ -133,14 +133,17 @@ keystone ui
 
 `keystone init` seeds these workflows under `.keystone/workflows/` (and the agents they rely on under `.keystone/workflows/agents/`):
 
+Top-level workflows:
 - `scaffold-feature`: Interactive workflow scaffolder. Prompts for requirements, plans files, generates content, and writes them.
+- `decompose-problem`: Decomposes a problem into research/implementation/review tasks, waits for approval, runs sub-workflows, and summarizes.
+- `dev`: Self-bootstrapping DevMode workflow for an interactive plan/implement/verify loop.
+
+Sub-workflows:
 - `scaffold-plan`: Generates a file plan from `requirements` input.
 - `scaffold-generate`: Generates file contents from `requirements` plus a `files` plan.
-- `decompose-problem`: Decomposes a problem into research/implementation/review tasks, waits for approval, runs sub-workflows, and summarizes.
 - `decompose-research`: Runs a single research task (`task`) with optional `context`/`constraints`.
 - `decompose-implement`: Runs a single implementation task (`task`) with optional `research` findings.
 - `decompose-review`: Reviews a single implementation task (`task`) with optional `implementation` results.
-- `dev`: Self-bootstrapping DevMode workflow for an interactive plan/implement/verify loop.
 
 Example runs:
 ```bash
@@ -148,7 +151,7 @@ keystone run scaffold-feature
 keystone run decompose-problem -i problem="Add caching to the API" -i context="Node/Bun service"
 ```
 
-The sub-workflows are used by the top-level workflows, but can be run directly if you want just one phase.
+Sub-workflows are used by the top-level workflows, but can be run directly if you want just one phase.
 
 ---
 
@@ -258,7 +261,7 @@ model: claude-3-5-sonnet-latest
 ```
 
 ### OpenAI Compatible Providers
-You can add any OpenAI-compatible provider (Groq, Together AI, Perplexity, Local Ollama, etc.) by setting the `type` to `openai` and providing the `base_url` and `api_key_env`.
+You can add any OpenAI-compatible provider (Together AI, Perplexity, Local Ollama, etc.) by setting the `type` to `openai` and providing the `base_url` and `api_key_env`.
 
 ### GitHub Copilot Support
 
@@ -476,7 +479,7 @@ All steps support common features:
 - `transform`: Post-process output using expressions.
 - `learn`: Auto-index for few-shot.
 - `reflexion`: Self-correction loop.
-- `auto_heal`: LLM-powered automatic error recovery (alias: `autoHeal`).
+- `auto_heal`: LLM-powered automatic error recovery.
 - `inputSchema` / `outputSchema`: JSON Schema validation.
 - `outputRetries`: Max retries for output validation failures.
 - `repairStrategy`: Strategy for output repair (`reask`, `repair`, `hybrid`).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "keystone-cli",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "description": "A local-first, declarative, agentic workflow orchestrator built on Bun",
   "type": "module",
   "bin": {

package/src/db/memory-db.ts

@@ -1,4 +1,4 @@
-import type { Database } from 'bun:sqlite';
+import { Database } from 'bun:sqlite';
 import { randomUUID } from 'node:crypto';
 import { existsSync, mkdirSync } from 'node:fs';
 import { dirname } from 'node:path';
@@ -24,7 +24,6 @@ export class MemoryDb {
       cached.refCount++;
       this.db = cached.db;
     } else {
-      const { Database } = require('bun:sqlite');
       const dir = dirname(dbPath);
       if (!existsSync(dir)) {
         mkdirSync(dir, { recursive: true });

package/src/db/sqlite-setup.ts

@@ -1,3 +1,5 @@
+import { Database } from 'bun:sqlite';
+import { existsSync } from 'node:fs';
 import { ConsoleLogger, type Logger } from '../utils/logger.ts';
 
 export function setupSqlite(logger: Logger = new ConsoleLogger()) {
@@ -5,9 +7,6 @@ export function setupSqlite(logger: Logger = new ConsoleLogger()) {
   // We need to try to load a custom one (e.g. from Homebrew) if on macOS
   if (process.platform === 'darwin') {
     try {
-      const { Database } = require('bun:sqlite');
-      const { existsSync } = require('node:fs');
-
       // Common Homebrew paths for SQLite
       const paths = [
         '/opt/homebrew/opt/sqlite/lib/libsqlite3.dylib',

package/src/runner/engine-executor.ts

@@ -325,9 +325,7 @@ export async function executeEngineStep(
     throw new Error(`Engine command "${command}" is not in the allowlist. Allowed: ${allowedList}`);
   }
 
-  const versionArgs = allowlistMatch.entry.versionArgs?.length
-    ? allowlistMatch.entry.versionArgs
-    : ['--version'];
+  const versionArgs = allowlistMatch.entry.versionArgs ?? ['--version'];
   const versionOutput = await checkEngineVersion(command, versionArgs, env, cwd, abortSignal);
   if (!versionOutput.includes(allowlistMatch.entry.version)) {
     throw new Error(

package/src/templates/agents/keystone-architect.md

@@ -12,7 +12,7 @@ You are the Keystone Architect. Your goal is to design and generate high-quality
 ## Workflow Schema (.yaml)
 - **name**: Unique identifier for the workflow.
 - **description**: (Optional) Description of the workflow.
-- **inputs**: Map of `{ type: 'string'|'number'|'boolean'|'array'|'object', default: any, description: string }` under the `inputs` key.
+- **inputs**: Map of `{ type: 'string'|'number'|'boolean'|'array'|'object', default: any, description?: string }` under the `inputs` key.
 - **outputs**: Map of expressions (e.g., `${{ steps.id.output }}`) under the `outputs` key.
 - **outputSchema**: (Optional) JSON Schema for final workflow outputs.
 - **env**: (Optional) Map of workflow-level environment variables.
@@ -59,7 +59,7 @@ Markdown files with YAML frontmatter:
 ## Expression Syntax
 - `${{ inputs.name }}`
 - `${{ steps.id.output }}`
-- `${{ steps.id.status }}` (e.g., `'pending'`, `'running'`, `'success'`, `'failed'`, `'skipped'`)
+- `${{ steps.id.status }}` (e.g., `'pending'`, `'running'`, `'success'`, `'failed'`, `'paused'`, `'suspended'`, `'skipped'`, `'canceled'`, `'waiting'`)
 - `${{ args.paramName }}` (used inside agent tools)
 - `${{ item }}` (current item in a `foreach` loop)
 - `${{ secrets.NAME }}` (access redacted secrets)

package/src/templates/batch-processor.yaml

@@ -5,7 +5,7 @@ inputs:
   target_dir: { type: string, default: "./data" }
 
 outputs:
-  processed_count: ${{ steps.process_files.outputs.length }}
+  processed_count: ${{ steps.process_files.output.length }}
 
 env:
   API_KEY: ${{ secrets.API_KEY }}

package/src/templates/loop-parallel.yaml

@@ -3,7 +3,7 @@ description: "Test the foreach race condition fix and .every() support"
 
 outputs:
   all_success: ${{ steps.process_items.items.every(s => s.status == 'success') }}
-  item_count: ${{ steps.process_items.outputs.length }}
+  item_count: ${{ steps.process_items.output.length }}
   first_output: ${{ steps.process_items.items[0].output }}
 
 steps:

package/src/utils/resource-loader.test.ts

@@ -39,16 +39,16 @@ describe('ResourceLoader', () => {
     expect(ResourceLoader.isDirectory(testFile)).toBe(false);
   });
 
-  test('should have embedded assets from repo during tests', () => {
+  test('should expose embedded assets manifest when available', () => {
     const assets = ResourceLoader.getEmbeddedAssets();
     const keys = Object.keys(assets);
-    // We expect at least the default seeded workflows if they exist in .keystone
-    expect(keys.length).toBeGreaterThan(0);
 
-    // Check for a common seeded workflow if it exists
-    const hasScaffold = keys.some((k) => k.includes('scaffold-feature.yaml'));
-    if (hasScaffold) {
-      expect(hasScaffold).toBe(true);
+    // Bundled assets only exist in compiled builds; dev/test may be empty.
+    if (keys.length === 0) {
+      expect(keys.length).toBe(0);
+      return;
     }
+
+    expect(Object.values(assets).every((value) => typeof value === 'string')).toBe(true);
   });
 });