refactor(cli): rename crayon run to crayon local run

Groups local dev under a `local` subcommand to distinguish from
`crayon cloud run`. Updates all references in skills and docs.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: cevian

CLAUDE.md

@@ -100,7 +100,7 @@ my-app/
 
 ### CLI (`cli/`)
 - `index.ts` - Commander.js CLI entry point
-- `run.ts` - Interactive `crayon run` (create or launch project)
+- `run.ts` - Interactive `crayon local run` (create or launch project)
 - `discovery.ts` - Workflow/node/agent discovery via jiti
 - `runs.ts` / `trace.ts` - Run history and trace viewing
 
@@ -119,7 +119,7 @@ my-app/
 
 | Command | Description |
 |---------|-------------|
-| `crayon run` | Interactive: create new project or launch existing |
+| `crayon local run` | Interactive: create new project or launch existing |
 | `crayon dev` | Start Dev UI with live DAG + embedded Claude Code |
 | `crayon workflow list` | List workflows (`--json` supported) |
 | `crayon workflow run <name>` | Run workflow with `-i <json>` |

packages/core/src/cli/index.ts

@@ -88,8 +88,10 @@ program
   .description("CLI for crayon workflow engine")
   .version(version);
 
-// ============ Run command ============
-program
+// ============ Local commands ============
+const local = program.command("local").description("Local development commands");
+
+local
   .command("run")
   .description("Create a new project or launch an existing one")
   .action(async () => {

packages/core/src/cli/run.ts

@@ -567,7 +567,7 @@ export async function runRun(): Promise<void> {
         } else {
           s.stop(pc.yellow("Database not ready yet"));
           p.log.warn(
-            `Run later: crayon run won't retry. Use the MCP tools or set up manually.`,
+            `Run later: crayon local run won't retry. Use the MCP tools or set up manually.`,
           );
         }
       } else {
@@ -597,6 +597,6 @@ export async function runRun(): Promise<void> {
   p.outro(pc.green(`Project created at ${directory}`));
   console.log();
   console.log(pc.bold("  To launch later:"));
-  console.log(pc.cyan(`  cd ${directory} && crayon run`));
+  console.log(pc.cyan(`  cd ${directory} && crayon local run`));
   console.log();
 }

skills/compile-workflow/SKILL.md

@@ -240,7 +240,7 @@ Tell the user:
 1. "Updated `src/crayon/workflows/<name>.ts`"
 2. If any missing nodes/agents were created: list the new files
 3. If agent tools were updated from descriptions: list which agents were updated
-4. "To test it, just say **run it** and I'll trigger it for you." — do NOT suggest `crayon run` or opening the Dev UI manually
+4. "To test it, just say **run it** and I'll trigger it for you." — do NOT suggest using the CLI or opening the Dev UI manually
 
 ---
 

skills/create-workflow/SKILL.md

@@ -16,13 +16,13 @@ Design and write a workflow with embedded description fields for crayon.
 Check the current working directory and handle one of three cases:
 
 **Case 1: Empty directory** (no files, or only dotfiles like `.git`)
-→ Tell the user to run `crayon run` first to scaffold a new project, then re-invoke this skill. **Stop here.**
+→ Tell the user this skill must be run inside a crayon project. **Stop here.**
 
 **Case 2: Existing crayon project** (has `src/crayon/workflows/` or `src/crayon/agents/` directories)
 → Good to go. Continue to step 2.
 
 **Case 3: Existing non-crayon directory** (has files/projects but no crayon structure — e.g., home directory, another repo)
-→ Tell the user to run `crayon run` in a subdirectory first, then re-invoke this skill from inside that directory. **Stop here.**
+→ Tell the user this skill must be run from inside a crayon project directory. **Stop here.**
 
 ### 2. Discover Integrations