@elevasis/sdk 0.5.10 → 0.5.12

package/dist/cli.cjs

@@ -40164,18 +40164,6 @@ var DOMAIN_MAP = {
   [DOMAINS.DIAGNOSTIC]: DIAGNOSTIC_DOMAIN
 };
 
-// ../core/src/execution/core/server/environment.ts
-function detectEnvironment() {
-  const env2 = process.env.NODE_ENV || "development";
-  if (env2 === "production") return "production";
-  if (env2 === "staging") return "staging";
-  return "development";
-}
-function canExecuteResource(resource, environment) {
-  const env2 = environment || detectEnvironment();
-  return env2 === "production" ? resource.status === "prod" : true;
-}
-
 // ../core/src/execution/engine/base/errors.ts
 var ExecutionError = class extends Error {
   /**
@@ -43293,9 +43281,8 @@ var ResourceRegistry = class {
    * List all resources for an organization
    * Returns ResourceDefinition metadata (not full definitions)
    *
-   * Environment filtering (automatic):
-   * - Development: Returns all resources (dev + prod)
-   * - Production: Returns only prod resources (filters out dev)
+   * All resources are returned regardless of server environment.
+   * Pass an explicit `environment` filter to get only 'dev' or 'prod' resources.
    */
   listResourcesForOrganization(organizationName, environment) {
     const orgResources = this.registry[organizationName];
@@ -43308,7 +43295,6 @@ var ResourceRegistry = class {
         environment
       };
     }
-    const currentEnv = detectEnvironment();
     const workflows = (orgResources.workflows || []).map((def) => ({
       resourceId: def.config.resourceId,
       name: def.config.name,
@@ -43317,12 +43303,7 @@ var ResourceRegistry = class {
       type: def.config.type,
       status: def.config.status,
       origin: this.remoteResources.has(`${organizationName}/${def.config.resourceId}`) ? "remote" : "local"
-    })).filter((resource) => {
-      if (environment) {
-        return resource.status === environment;
-      }
-      return canExecuteResource(resource, currentEnv);
-    });
+    })).filter((resource) => !environment || resource.status === environment);
     const agents = (orgResources.agents || []).map((def) => ({
       resourceId: def.config.resourceId,
       name: def.config.name,
@@ -43332,18 +43313,13 @@ var ResourceRegistry = class {
       status: def.config.status,
       sessionCapable: def.config.sessionCapable ?? false,
       origin: this.remoteResources.has(`${organizationName}/${def.config.resourceId}`) ? "remote" : "local"
-    })).filter((resource) => {
-      if (environment) {
-        return resource.status === environment;
-      }
-      return canExecuteResource(resource, currentEnv);
-    });
+    })).filter((resource) => !environment || resource.status === environment);
     return {
       workflows,
       agents,
       total: workflows.length + agents.length,
       organizationName,
-      environment: environment || (currentEnv === "production" ? "prod" : void 0)
+      environment
     };
   }
   /**
@@ -43694,7 +43670,7 @@ function wrapAction(commandName, fn) {
     } catch (error46) {
       const errorMessage = error46 instanceof Error ? error46.message : String(error46);
       console.error(source_default.red("\nError:"), errorMessage);
-      console.error(source_default.gray(`Run "elevasis ${commandName} --help" for more information`));
+      console.error(source_default.gray(`Run "elevasis-sdk ${commandName} --help" for more information`));
       process.exit(1);
     }
   };
@@ -43811,12 +43787,10 @@ async function apiDelete(endpoint, apiUrl = resolveApiUrl()) {
 // package.json
 var package_default = {
   name: "@elevasis/sdk",
-  version: "0.5.10",
+  version: "0.5.12",
   description: "SDK for building Elevasis organization resources",
-  "comment:bin": "IMPORTANT: This package shares the 'elevasis' binary name with @repo/cli. They never conflict because @elevasis/sdk must NEVER be added as a dependency of any workspace package (apps/*, packages/*, organizations/*). Workspace projects use @repo/cli for the 'elevasis' binary. External developers (outside the workspace) get this SDK's binary via npm install.",
   type: "module",
   bin: {
-    elevasis: "./dist/cli.cjs",
     "elevasis-sdk": "./dist/cli.cjs"
   },
   exports: {
@@ -43942,7 +43916,7 @@ async function generateResourceMap(org) {
     "",
     "# Resource Map",
     "",
-    "> Auto-generated by `elevasis deploy`. Do not edit manually.",
+    "> Auto-generated by `elevasis-sdk deploy`. Do not edit manually.",
     ""
   ];
   if (workflows.length > 0) {
@@ -43998,7 +43972,7 @@ async function generateProjectMap(org) {
     "",
     "# Project Map",
     "",
-    "> Auto-generated by `elevasis deploy` and `/meta fix`. Do not edit manually.",
+    "> Auto-generated by `elevasis-sdk deploy` and `/meta fix`. Do not edit manually.",
     "",
     "## Project Overview",
     "",
@@ -44330,7 +44304,7 @@ async function generateProjectMap(org) {
   await (0, import_promises.writeFile)((0, import_path.resolve)("docs/project-map.mdx"), lines.join("\n"), "utf-8");
 }
 function registerDeployCommand(program3) {
-  program3.command("deploy").description("Validate, bundle, upload, and deploy project resources\n  Example: elevasis deploy --api-url http://localhost:5170").option("--api-url <url>", "API URL").option("--entry <path>", "Path to entry file (default: ./src/index.ts)").option("--prod", "Deploy to production (overrides NODE_ENV=development)").action(wrapAction("deploy", async (options2) => {
+  program3.command("deploy").description("Validate, bundle, upload, and deploy project resources\n  Example: elevasis-sdk deploy --api-url http://localhost:5170").option("--api-url <url>", "API URL").option("--entry <path>", "Path to entry file (default: ./src/index.ts)").option("--prod", "Deploy to production (overrides NODE_ENV=development)").action(wrapAction("deploy", async (options2) => {
     const startTime = Date.now();
     const apiUrl = resolveApiUrl(options2.apiUrl, options2.prod);
     const env2 = resolveEnvironment(options2.prod);
@@ -44578,7 +44552,7 @@ startWorker(org)
 // src/cli/commands/check.ts
 var import_meta2 = {};
 function registerCheckCommand(program3) {
-  program3.command("check").description("Validate project resources against the ResourceRegistry\n  Example: elevasis check --entry ./src/index.ts").option("--entry <path>", "Path to entry file (default: ./src/index.ts)").action(wrapAction("check", async (options2) => {
+  program3.command("check").description("Validate project resources against the ResourceRegistry\n  Example: elevasis-sdk check --entry ./src/index.ts").option("--entry <path>", "Path to entry file (default: ./src/index.ts)").action(wrapAction("check", async (options2) => {
     const entryPath = options2.entry ?? "./src/index.ts";
     const spinner = ora("Validating resources...").start();
     try {
@@ -44732,7 +44706,7 @@ async function pollForCompletion(resourceId, executionId, apiUrl) {
 }
 function registerExecCommand(program3) {
   program3.command("exec <resourceId>").description(`Execute a deployed resource
-  Example: elevasis exec my-workflow -i '{"key":"value"}'`).option("-i, --input <json>", "Input data as JSON string").option("--async", "Execute asynchronously with polling").option("--api-url <url>", "API URL").action(wrapAction("exec", async (resourceId, options2) => {
+  Example: elevasis-sdk exec my-workflow -i '{"key":"value"}'`).option("-i, --input <json>", "Input data as JSON string").option("--async", "Execute asynchronously with polling").option("--api-url <url>", "API URL").action(wrapAction("exec", async (resourceId, options2) => {
     const input = options2.input ? JSON.parse(options2.input) : {};
     const apiUrl = resolveApiUrl(options2.apiUrl);
     if (options2.async) {
@@ -44814,7 +44788,7 @@ function registerResourcesCommand(program3) {
     }
     if (data.resources.length === 0) {
       console.log(source_default.yellow("No deployed resources found."));
-      console.log(source_default.gray("Deploy with: elevasis deploy"));
+      console.log(source_default.gray("Deploy with: elevasis-sdk deploy"));
       return;
     }
     const workflows = data.resources.filter((r) => r.resourceType === "workflow");
@@ -44845,7 +44819,7 @@ function registerResourcesCommand(program3) {
 
 // src/cli/commands/executions.ts
 function registerExecutionsCommand(program3) {
-  program3.command("executions <resourceId>").description("List execution history for a resource\n  Example: elevasis executions my-workflow --limit 10").option("--api-url <url>", "API URL").option("--json", "Output as JSON").option("--limit <number>", "Limit number of results (default: 50)").option("--status <status>", "Filter by status (running|completed|failed)").action(wrapAction("executions", async (resourceId, options2) => {
+  program3.command("executions <resourceId>").description("List execution history for a resource\n  Example: elevasis-sdk executions my-workflow --limit 10").option("--api-url <url>", "API URL").option("--json", "Output as JSON").option("--limit <number>", "Limit number of results (default: 50)").option("--status <status>", "Filter by status (running|completed|failed)").action(wrapAction("executions", async (resourceId, options2) => {
     const apiUrl = resolveApiUrl(options2.apiUrl);
     const spinner = ora(`Fetching executions for ${resourceId}...`).start();
     const params = new URLSearchParams();
@@ -44895,7 +44869,7 @@ function registerExecutionsCommand(program3) {
     console.log();
     console.log(
       source_default.dim("Use"),
-      source_default.cyan(`elevasis execution ${resourceId} <execution-id>`),
+      source_default.cyan(`elevasis-sdk execution ${resourceId} <execution-id>`),
       source_default.dim("to view details")
     );
   }));
@@ -44903,7 +44877,7 @@ function registerExecutionsCommand(program3) {
 
 // src/cli/commands/execution.ts
 function registerExecutionCommand(program3) {
-  program3.command("execution <resourceId> <executionId>").description("Get detailed information about a specific execution\n  Example: elevasis execution my-workflow abc-123-uuid --logs-only").option("--api-url <url>", "API URL").option("--json", "Output raw JSON response").option("--logs-only", "Show only execution logs").option("--input", "Include input data in output").option("--result", "Include result data in output").action(wrapAction("execution", async (resourceId, executionId, options2) => {
+  program3.command("execution <resourceId> <executionId>").description("Get detailed information about a specific execution\n  Example: elevasis-sdk execution my-workflow abc-123-uuid --logs-only").option("--api-url <url>", "API URL").option("--json", "Output raw JSON response").option("--logs-only", "Show only execution logs").option("--input", "Include input data in output").option("--result", "Include result data in output").action(wrapAction("execution", async (resourceId, executionId, options2) => {
     const apiUrl = resolveApiUrl(options2.apiUrl);
     const spinner = ora("Fetching execution details...").start();
     const execution = await apiGet(
@@ -45019,7 +44993,7 @@ function registerDeploymentsCommand(program3) {
     }
     if (data.deployments.length === 0) {
       console.log(source_default.yellow("No deployments found."));
-      console.log(source_default.gray("Deploy with: elevasis deploy"));
+      console.log(source_default.gray("Deploy with: elevasis-sdk deploy"));
       return;
     }
     for (const [index, dep] of data.deployments.entries()) {
@@ -45065,7 +45039,7 @@ function registerDeploymentsCommand(program3) {
 
 // src/cli/commands/describe.ts
 function registerDescribeCommand(program3) {
-  program3.command("describe <resourceId>").description("Show resource definition (metadata + schemas)\n  Example: elevasis describe my-workflow").option("--api-url <url>", "API URL").option("--json", "Output raw JSON response").action(wrapAction("describe", async (resourceId, options2) => {
+  program3.command("describe <resourceId>").description("Show resource definition (metadata + schemas)\n  Example: elevasis-sdk describe my-workflow").option("--api-url <url>", "API URL").option("--json", "Output raw JSON response").action(wrapAction("describe", async (resourceId, options2) => {
     const apiUrl = resolveApiUrl(options2.apiUrl);
     const spinner = ora("Fetching resource definition...").start();
     const definition = await apiGet(
@@ -45105,13 +45079,13 @@ var import_path3 = require("path");
 var import_promises2 = require("fs/promises");
 
 // src/cli/commands/templates/core/workspace.ts
-var TEMPLATE_VERSION = 23;
+var TEMPLATE_VERSION = 27;
 function configTemplate() {
   return `import type { ElevasConfig } from '@elevasis/sdk'
 
 export default {
   templateVersion: ${TEMPLATE_VERSION},
-  // defaultStatus: 'dev',     // Default status for new resources ('dev' | 'production')
+  // defaultStatus: 'dev',     // Default status for new resources ('dev' | 'prod')
   // dev: { port: 5170 },      // Local API port (internal development only)
 } satisfies ElevasConfig
 `;
@@ -45123,8 +45097,8 @@ function packageJsonTemplate(organization) {
     type: "module",
     scripts: {
       "check-types": "tsc --noEmit",
-      check: "elevasis check",
-      deploy: "elevasis deploy"
+      check: "elevasis-sdk check",
+      deploy: "elevasis-sdk deploy"
     },
     dependencies: {
       "@elevasis/sdk": `^${SDK_VERSION}`
@@ -45160,10 +45134,6 @@ function envTemplate() {
   return `ELEVASIS_PLATFORM_KEY=
 `;
 }
-function envExampleTemplate() {
-  return `ELEVASIS_PLATFORM_KEY=sk_your_key_here
-`;
-}
 function npmrcTemplate() {
   return `auto-install-peers = true
 `;
@@ -45175,6 +45145,7 @@ dist/
 __elevasis_worker.ts
 .claude/settings.local.json
 .claude/memory/
+package-lock.json
 `;
   if (ctx.hasUI) {
     content += `ui/node_modules/
@@ -45200,7 +45171,7 @@ An [Elevasis](https://elevasis.io) workspace built with the \`@elevasis/sdk\`.
 pnpm install
 \`\`\`
 
-Copy \`.env.example\` to \`.env\` and add your API key:
+Add your API key to \`.env\`:
 
 \`\`\`
 ELEVASIS_PLATFORM_KEY=sk_...
@@ -45209,12 +45180,12 @@ ELEVASIS_PLATFORM_KEY=sk_...
 ## Development
 
 \`\`\`bash
-elevasis check                        # Validate resource definitions
-elevasis deploy                       # Bundle and deploy to platform
-elevasis exec <resourceId> --input '...'  # Execute a resource
-elevasis resources                    # List deployed resources
-elevasis describe <resourceId>        # Show resource definition + schemas
-elevasis executions <resourceId>      # View execution history
+pnpm run check                                              # Validate resource definitions
+pnpm run deploy                                             # Bundle and deploy to platform
+pnpm exec elevasis-sdk exec <resourceId> --input '...'      # Execute a resource
+pnpm exec elevasis-sdk resources                            # List deployed resources
+pnpm exec elevasis-sdk describe <resourceId>                # Show resource definition + schemas
+pnpm exec elevasis-sdk executions <resourceId>              # View execution history
 \`\`\`
 
 ## Project Structure
@@ -45235,7 +45206,7 @@ A multi-step workflow that queries platform status and compiles a natural langua
 summary using an LLM. Demonstrates platform API usage with the \`llm\` typed adapter and \`platform.call()\`.
 
 \`\`\`bash
-elevasis exec platform-status --input '{"timeRange": "24h"}'
+pnpm exec elevasis-sdk exec platform-status --input '{"timeRange": "24h"}'
 \`\`\`
 
 **Input:** \`{ "timeRange": "1h" | "24h" | "7d" }\`
@@ -45247,7 +45218,7 @@ A simple workflow that echoes the input message back. Use it as a starter patter
 for new workflows:
 
 \`\`\`bash
-elevasis exec echo --input '{"message": "hello"}'
+pnpm exec elevasis-sdk exec echo --input '{"message": "hello"}'
 \`\`\`
 
 **Input:** \`{ "message": string }\`
@@ -45500,13 +45471,18 @@ All \`reference/\` paths resolve to \`node_modules/@elevasis/sdk/reference/\`.
 
 ## Elevasis CLI
 
-**MANDATORY:** Use the \`elevasis\` CLI for all execution/platform operations -- never \`npx\`, \`curl\`, or any other tool.
+**MANDATORY:** Use the \`elevasis-sdk\` CLI for all execution/platform operations -- never \`curl\` or any other tool.
+
+Use pnpm scripts for check and deploy (they resolve the local binary automatically):
+
+- \`pnpm run check\` -- validate resource definitions without deploying
+- \`pnpm run deploy\` -- deploy to the platform
 
-- \`elevasis exec <resource-id> --input '{...}'\` -- run a resource synchronously
-- \`elevasis exec <resource-id> --input '{...}' --async\` -- run async, returns execution ID
-- \`elevasis execution <resource-id> <execution-id>\` -- inspect execution detail
-- \`elevasis check\` -- validate resource definitions without deploying
-- \`elevasis deploy\` -- deploy to the platform
+Use \`pnpm exec elevasis-sdk\` for runtime commands (resolves the locally installed binary):
+
+- \`pnpm exec elevasis-sdk exec <resource-id> --input '{...}'\` -- run a resource synchronously
+- \`pnpm exec elevasis-sdk exec <resource-id> --input '{...}' --async\` -- run async, returns execution ID
+- \`pnpm exec elevasis-sdk execution <resource-id> <execution-id>\` -- inspect execution detail
 
 Organization is derived from your API key -- no org prefix needed in the resource ID.
 For full CLI reference: \`reference/cli/index.mdx\`
@@ -45658,32 +45634,34 @@ Example (first time, no progress):
 Elevasis Tutorial
 ==================
 
-ORCHESTRATION CONCEPTS                              0/7
-  1  Welcome & Orientation                          [ ]
-  2  Your First Custom Workflow                     [ ]
-  3  Understanding Data (Schemas)                   [ ]
-  4  Using Platform Tools                           [ ]
-  5  Multi-Step Workflows                           [ ]
-  6  Decision Points                                [ ]
-  7  Going to Production                            [ ]
-
-EXAMPLES & ADVANCED MODULES                        0/9
-  8  Human-in-the-Loop                              [ ]
-  9  Task Scheduling                                [ ]
- 10  Notification System                            [ ]
- 11  Real-World Integrations                        [ ]
- 12  Error Handling Mastery                         [ ]
- 13  Advanced Workflows                             [ ]
- 14  Resource Composition                           [ ]
- 15  LLM Integration                               [ ]
- 16  AI Agents                                     [ ]
-
-META-FRAMEWORK                                     0/5
- 17  The Agent Framework                            [ ]
- 18  The /meta Command                              [ ]
- 19  /work and /docs                                [ ]
- 20  Rules, Memory, and Customization               [ ]
- 21  Template Lifecycle                             [ ]
+INTRODUCTION                                       0/4
+  1  Welcome & Orientation                         [ ]
+  2  How This Workspace Works                      [ ]
+  3  The /meta Command                             [ ]
+  4  /work and /docs                               [ ]
+
+CORE CONCEPTS                                      0/6
+  5  Your First Custom Workflow                    [ ]
+  6  Understanding Data (Schemas)                  [ ]
+  7  Using Platform Tools                          [ ]
+  8  Multi-Step Workflows                          [ ]
+  9  Decision Points                               [ ]
+ 10  Going to Production                           [ ]
+
+ADVANCED MODULES                                   0/9
+ 11  Human-in-the-Loop                             [ ]
+ 12  Task Scheduling                               [ ]
+ 13  Notification System                           [ ]
+ 14  Real-World Integrations                       [ ]
+ 15  Error Handling Mastery                        [ ]
+ 16  Advanced Workflows                            [ ]
+ 17  Resource Composition                          [ ]
+ 18  LLM Integration                               [ ]
+ 19  AI Agents                                     [ ]
+
+ADVANCED WORKSPACE                                 0/2
+ 20  Rules, Memory, and Customization              [ ]
+ 21  Template Lifecycle                            [ ]
 
 Pick a number to start.
 \`\`\`
@@ -45696,7 +45674,7 @@ indicators from completed/current state. \`"status"\` -> show the same table.
 1. Read \`.claude/memory/tutorial-progress.md\`
 2. Show the full menu table (## Menu) with progress filled in
 3. User picks a number -> start or resume that lesson or module directly
-4. After completion: mark done in progress file, show updated menu table
+4. After user confirms readiness: mark done in progress file, show updated menu table
 5. All 21 items complete -> congratulate, suggest exploring docs/ or /work
 
 ## Lesson Flow
@@ -45706,18 +45684,18 @@ Each lesson follows this flow:
 2. Explain the concept (read docs per skill level, adapt to user)
 3. Guide user to build or modify something (agent writes all code for automation: none)
 4. Verify it works (CLI primary for all levels; Command Center for visual review -- Command View, Execution Logs)
-5. Celebrate success, record observations in \`.claude/memory/tutorial-progress.md\`
-6. Ask: "Ready for the next lesson, or want to practice more?"
+5. Celebrate success and ask: "Any questions, or ready to continue?"
+6. Once the user confirms, record observations in \`.claude/memory/tutorial-progress.md\`
 
 ## Lessons
 
-**Lesson 1: Welcome & Orientation**
+**Item 1: Welcome & Orientation**
 
 When automation is none:
 Skip the file tour. Start with what Elevasis does for their business -- use analogies
 from \`reference/developer/interaction-guidance.mdx\` (recipe, assembly line, kitchen
 appliance). Explain deployment plainly: "You write the recipe here, then deploy it so
-it's live." Deploy the starter echo workflow (\`elevasis check\` + \`elevasis deploy\`),
+it's live." Deploy the starter echo workflow (\`elevasis-sdk check\` + \`elevasis-sdk deploy\`),
 THEN tour the Command Center so the user sees populated pages, not empty ones. Tour:
 Command View (echo node), Execution Logs (result).
 Observation focus: automation value understanding, Command Center comfort.
@@ -45726,52 +45704,153 @@ When automation is low-code or custom:
 Tour project files: src/index.ts (registry), src/example/echo.ts (starter
 workflow), src/operations/platform-status.ts (platform API example),
 elevasis.config.ts, .env, docs/. Explain the execution model.
-Verify: run \`elevasis resources\`. Then open the Command Center and tour the
+Verify: run \`elevasis-sdk resources\`. Then open the Command Center and tour the
 main pages: Command View (resource graph), Execution Logs.
 Point out the echo workflow node in Command View.
 Observation focus: cloud deployment model, UI navigation comfort.
 
-**Lesson 2: Your First Custom Workflow**
+**Item 2: How This Workspace Works**
+
+When automation is none:
+"This workspace comes with a built-in assistant that knows your project, your tools,
+and your goals. Let me show you how it's set up." Open CLAUDE.md and explain in
+plain terms: it's the agent's instruction sheet. Point out the commands in the
+Commands table. Show /meta, /tutorial, /work. Explain the creds skill as
+"the assistant automatically helps when you mention API keys." Tour the memory folder
+at a high level -- "this is where the agent stores what it learns about your project."
+Verify: Ask the user a question about their business goal and show how the agent
+references their profile in the answer.
+Observation focus: agent-as-assistant concept, CLAUDE.md as instruction sheet.
+
+When automation is low-code:
+Read CLAUDE.md and walk through each section. Explain: what the agent reads on
+session start, how the navigation table works, what the Skills section means.
+Explain the four commands briefly. Show that the agent has memory: open
+\`.claude/memory/profile/skills.md\` and show their own profile -- "every session,
+the agent reads this and adapts." Explain the initialized flag.
+Verify: Run /meta to see project status.
+Observation focus: memory system concept, session initialization flow.
+
+When automation is custom:
+Read CLAUDE.md in full. Explain the session initialization sequence: CLAUDE.md ->
+navigation table -> memory files -> context loading. Walk through: Commands section
+(4 commands + creds skill), Rules section (auto-loaded based on file paths), Skills
+section (auto-triggered by content patterns). Point out the initialized flag and
+explain how /meta init set it.
+Verify: Run /meta to see project status; observe which fields it reports.
+Observation focus: initialization model, command-vs-rule-vs-skill distinction.
+
+**Item 3: The /meta Command**
+
+When automation is none:
+"Think of /meta as your project dashboard -- it shows what's healthy and what needs
+attention." Run /meta (no arguments) and narrate the output in plain language: what
+each field means. Explain /meta fix as "the agent tidies up and applies updates."
+Explain /meta deploy as "the agent publishes your changes in one step." Briefly note
+/meta health shows what happened when something goes wrong.
+Verify: Run /meta (no arguments). Narrate the output together.
+Observation focus: project lifecycle concept, dashboard reading.
+
+When automation is low-code:
+Show all /meta operations with their purpose. Map to familiar concepts: /meta fix is
+like "repair this Zap" in Zapier; /meta deploy is a one-command publish pipeline.
+Walk through the /meta (no-args) output: template version (SDK template your workspace
+uses), SDK version (installed package), profile summary, drift check.
+Verify: Run /meta and interpret each field together.
+Observation focus: deploy pipeline understanding, version tracking.
+
+When automation is custom:
+Read \`.claude/commands/meta.md\`. Walk through each operation: init (first-run setup
+with assessment), (no-args) (status dashboard), fix (drift repair + SDK upgrade +
+rules health), deploy (7-step pipeline: check, typecheck, docs, git, deploy,
+project-map, verify), health (runtime diagnostics). Explain the merge strategy for
+CLAUDE.md and commands. Note the template access model: templates read from
+@elevasis/sdk/templates subpath.
+Verify: Run /meta to see project status. Identify what a version mismatch looks like.
+Observation focus: full lifecycle coverage, pipeline internals.
+
+**Item 4: /work and /docs**
+
+When automation is none:
+"You can ask the assistant to track work across conversations. When you start something
+complex, use /work create to save your place. Next session, /work resume picks up where
+you left off." Walk through the concept without deep command details. Then introduce /docs:
+"When a task is finished, /work complete moves it to docs/ permanently. After that, /docs
+helps you find and read what's there -- like a notebook for your project." Run /docs (no
+args) to show the docs/ overview together.
+Verify: Create a task with \`/work create "practice task"\`, then run /work to see it listed.
+Then run /docs to see the docs/ structure.
+Observation focus: persistence concept, cross-session continuity, docs as permanent notes.
+
+When automation is low-code:
+Show /work operations: create (task doc with frontmatter + sections), save (updates
+Progress + Resume Context), resume (loads context for next session), complete (moves
+to permanent docs/).
+Then introduce /docs: "/docs is for permanent knowledge -- things that don't expire. Use
+/docs create to document a workflow or integration. Use /docs verify to check if your
+docs match the current code." Explain the boundary: /work manages in-progress/, /docs
+manages permanent docs/.
+Verify: Create a task with \`/work create "practice task"\`, run /work save, inspect the
+file. Then run /docs to browse docs/.
+Observation focus: task tracking workflow, /work vs /docs separation.
+
+When automation is custom:
+Read \`.claude/commands/work.md\`. Full /work coverage:
+/work create (kebab-case filename, frontmatter with status, Objective/Plan/Progress/
+Resume Context sections), /work save (Progress + Resume Context update), /work resume
+(multiple-task disambiguation), /work complete (moves to final location).
+Then read \`.claude/commands/docs.md\`. Cover /docs operations:
+/docs (default): browse permanent docs/, categorized with read-only auto-generated files
+separate; /docs create: interview-driven, resource-aware doc creation from src/ code
+analysis; /docs verify: cross-references resource IDs, schema fields, platform tools in
+docs against src/ -- standalone analog of /meta fix step 5.
+Explain the relationship: /work owns docs/in-progress/ (task lifecycle), /work complete
+moves docs to permanent location, /docs browses and verifies what's there.
+Verify: Create a task doc, save progress, run /work complete to move it. Then run /docs
+to see it in the permanent docs/ listing.
+Observation focus: task doc anatomy, /work-to-/docs handoff, docs verification as standalone tool.
+
+**Item 5: Your First Custom Workflow**
 
 When automation is none:
 Frame the workflow as "a recipe." Use plain language: "settings" not "config",
 "what data it needs" not "contract", "instructions" not "steps", "where it starts"
-not "entryPoint." Agent writes all code changes. Agent runs \`elevasis exec\` to verify
+not "entryPoint." Agent writes all code changes. Agent runs \`elevasis-sdk exec\` to verify
 and narrates the result in plain terms.
 Observation focus: recipe-to-result connection.
 
 When automation is low-code or custom:
 Modify the echo workflow. Walk through each part: config, contract, steps,
-entryPoint. Deploy: \`elevasis check\` then \`elevasis deploy\`. Test with
-\`elevasis exec echo --input '{"message":"hello"}'\`. Then open the Execution
+entryPoint. Deploy: \`elevasis-sdk check\` then \`elevasis-sdk deploy\`. Test with
+\`elevasis-sdk exec echo --input '{"message":"hello"}'\`. Then open the Execution
 Runner in the Command Center, find the echo workflow, fill out the form, and
 run it from the UI. Compare the result to the CLI output.
 Observation focus: deployment-to-execution loop, TypeScript syntax comfort.
 
-**Lesson 3: Understanding Data (Schemas)**
+**Item 6: Understanding Data (Schemas)**
 
 When automation is none:
 Frame as "What information does your automation need?" Describe types in plain English:
 text, number, yes/no, a choice from a list. NO Zod, no z.string(), no z.infer(), no
 code shown. Agent reads identity.md goals and writes the workflow schema. Agent runs
-\`elevasis exec\` with sample input and narrates the result.
+\`elevasis-sdk exec\` with sample input and narrates the result.
 Observation focus: data-to-input connection, required vs optional understanding.
 
 When automation is low-code:
 "Field mapping like Zapier, but with validation." Show Zod types briefly. Demonstrate
 how \`.describe()\` documents each field. Build schema based on identity.md goals.
-After deploy, run with \`elevasis exec --input '{...}'\` to verify each field.
+After deploy, run with \`elevasis-sdk exec --input '{...}'\` to verify each field.
 Observation focus: schema-to-input mapping, optional fields, types.
 
 When automation is custom:
 Explain schemas in plain English (concepts page). Show common Zod types.
 Explain \`z.infer\`. Build a new workflow with real-world input schema based
 on the user's goals (read .claude/memory/profile/identity.md). After deploy,
-run with \`elevasis exec --input '{...}'\` to verify the schema and inspect
+run with \`elevasis-sdk exec --input '{...}'\` to verify the schema and inspect
 the execution output.
 Observation focus: schema-to-input mapping, optional fields, types.
 
-**Lesson 4: Using Platform Tools**
+**Item 7: Using Platform Tools**
 
 When automation is none:
 Frame as "Connecting your automation to a service you already use." Pick ONE
@@ -45793,12 +45872,12 @@ If using the approval tool, note that pending requests surface in Command Queue.
 See reference/platform-tools/adapters.mdx for full API.
 Observation focus: credential setup (CLI + UI), async/await.
 
-**Lesson 5: Multi-Step Workflows**
+**Item 8: Multi-Step Workflows**
 
 When automation is none:
 Frame as "Step 1 passes its result to Step 2, like a relay race." Command View is
 PRIMARY teaching tool -- show the visual graph before explaining code. Agent builds
-the 2-step workflow. Agent runs \`elevasis exec\` to verify and shows output flow.
+the 2-step workflow. Agent runs \`elevasis-sdk exec\` to verify and shows output flow.
 User opens Command View to see the two nodes + arrow. Code is secondary.
 Observation focus: relay-race concept, visual graph comprehension.
 
@@ -45809,12 +45888,12 @@ relationship edges between resources. Explain how declared relationships map
 to the visual graph.
 Observation focus: data flow reasoning, relationship visualization.
 
-**Lesson 6: Decision Points**
+**Item 9: Decision Points**
 
 When automation is none:
 Frame as "If the customer is VIP, do this -- otherwise, do that." No StepType.CONDITIONAL
 jargon -- focus on the concept, not the implementation. Agent adds the condition.
-Agent runs \`elevasis exec\` for both paths. Open Execution Logs to see which
+Agent runs \`elevasis-sdk exec\` for both paths. Open Execution Logs to see which
 path ran. Guide log navigation step-by-step.
 Observation focus: branching concept understanding, log navigation.
 
@@ -45825,7 +45904,7 @@ Execution Logs in the Command Center, filter by the resource, and show how
 each path appears in the log detail (step trace, input/output).
 Observation focus: branching logic reasoning, execution log interpretation.
 
-**Lesson 7: Going to Production**
+**Item 10: Going to Production**
 
 When automation is none:
 Frame as "draft vs live" not "dev vs production." Error handling: "when something
@@ -45839,12 +45918,12 @@ Change status from dev to production. Cover error handling: try/catch,
 ExecutionError, PlatformToolError. Create a schedule in Task Scheduler (use
 Recurring type for a cron schedule). If docs/ has pages, show Knowledge Base.
 Open Deployments page to confirm the latest version is active. Show CLI
-monitoring: elevasis executions, elevasis execution. Suggest next steps.
+monitoring: elevasis-sdk executions, elevasis-sdk execution. Suggest next steps.
 Observation focus: readiness for independent operation (CLI + UI).
 
 ## Module Menu
 
-Module order (items 8-16 in the main menu): hitl, schedules, notifications,
+Module order (items 11-19 in the main menu): hitl, schedules, notifications,
 integrations, error-handling, workflows, composition, llm, agents.
 
 After completing a module, show the updated full menu table (## Menu).
@@ -45927,116 +46006,16 @@ Read: \`reference/framework/agent.mdx\`.
 Build: Create an agent definition with tools. Configure LLM tool calling.
 Compare agent vs workflow for a task.
 Key concepts: agent definition, tool registration, LLM tool calling, execution trace.
-Verify: Run agent with \`elevasis exec\`, review tool call trace in Execution Logs.
-
-## Meta-Framework Track
-
-The Meta-Framework track teaches you how the Claude Code workspace works -- the commands,
-rules, memory system, and customization model. It is independent of the core path and
-can be taken in any order.
-
-**MF1: The Agent Framework -- How This Workspace Works**
-
-When automation is none:
-"This workspace comes with a built-in assistant that knows your project, your tools,
-and your goals. Let me show you how it's set up." Open CLAUDE.md and explain in
-plain terms: it's the agent's instruction sheet. Point out the commands in the
-Commands table. Show /meta, /tutorial, /work. Explain the creds skill as
-"the assistant automatically helps when you mention API keys." Tour the memory folder
-at a high level -- "this is where the agent stores what it learns about your project."
-Verify: Ask the user a question about their business goal and show how the agent
-references their profile in the answer.
-Observation focus: agent-as-assistant concept, CLAUDE.md as instruction sheet.
-
-When automation is low-code:
-Read CLAUDE.md and walk through each section. Explain: what the agent reads on
-session start, how the navigation table works, what the Skills section means.
-Explain the four commands briefly. Show that the agent has memory: open
-\`.claude/memory/profile/skills.md\` and show their own profile -- "every session,
-the agent reads this and adapts." Explain the initialized flag.
-Verify: Run /meta to see project status.
-Observation focus: memory system concept, session initialization flow.
-
-When automation is custom:
-Read CLAUDE.md in full. Explain the session initialization sequence: CLAUDE.md ->
-navigation table -> memory files -> context loading. Walk through: Commands section
-(4 commands + creds skill), Rules section (auto-loaded based on file paths), Skills
-section (auto-triggered by content patterns). Point out the initialized flag and
-explain how /meta init set it.
-Verify: Run /meta to see project status; observe which fields it reports.
-Observation focus: initialization model, command-vs-rule-vs-skill distinction.
-
-**MF2: The /meta Command -- Project Lifecycle**
-
-When automation is none:
-"Think of /meta as your project dashboard -- it shows what's healthy and what needs
-attention." Run /meta (no arguments) and narrate the output in plain language: what
-each field means. Explain /meta fix as "the agent tidies up and applies updates."
-Explain /meta deploy as "the agent publishes your changes in one step." Briefly note
-/meta health shows what happened when something goes wrong.
-Verify: Run /meta (no arguments). Narrate the output together.
-Observation focus: project lifecycle concept, dashboard reading.
-
-When automation is low-code:
-Show all /meta operations with their purpose. Map to familiar concepts: /meta fix is
-like "repair this Zap" in Zapier; /meta deploy is a one-command publish pipeline.
-Walk through the /meta (no-args) output: template version (SDK template your workspace
-uses), SDK version (installed package), profile summary, drift check.
-Verify: Run /meta and interpret each field together.
-Observation focus: deploy pipeline understanding, version tracking.
+Verify: Run agent with \`elevasis-sdk exec\`, review tool call trace in Execution Logs.
 
-When automation is custom:
-Read \`.claude/commands/meta.md\`. Walk through each operation: init (first-run setup
-with assessment), (no-args) (status dashboard), fix (drift repair + SDK upgrade +
-rules health), deploy (7-step pipeline: check, typecheck, docs, git, deploy,
-project-map, verify), health (runtime diagnostics). Explain the merge strategy for
-CLAUDE.md and commands. Note the template access model: templates read from
-@elevasis/sdk/templates subpath.
-Verify: Run /meta to see project status. Identify what a version mismatch looks like.
-Observation focus: full lifecycle coverage, pipeline internals.
+## Advanced Workspace Track
 
-**MF3: /work and /docs -- Task and Documentation Lifecycle**
+The Advanced Workspace track teaches power-user workspace customization and maintenance --
+rules, memory, and the template lifecycle. Independent of the core path; can be taken at any time.
 
-When automation is none:
-"You can ask the assistant to track work across conversations. When you start something
-complex, use /work create to save your place. Next session, /work resume picks up where
-you left off." Walk through the concept without deep command details. Then introduce /docs:
-"When a task is finished, /work complete moves it to docs/ permanently. After that, /docs
-helps you find and read what's there -- like a notebook for your project." Run /docs (no
-args) to show the docs/ overview together.
-Verify: Create a task with \`/work create "practice task"\`, then run /work to see it listed.
-Then run /docs to see the docs/ structure.
-Observation focus: persistence concept, cross-session continuity, docs as permanent notes.
+Each item follows the same flow as core lessons: announce, explain per skill level, verify, record observations.
 
-When automation is low-code:
-Show /work operations: create (task doc with frontmatter + sections), save (updates
-Progress + Resume Context), resume (loads context for next session), complete (moves
-to permanent docs/).
-Then introduce /docs: "/docs is for permanent knowledge -- things that don't expire. Use
-/docs create to document a workflow or integration. Use /docs verify to check if your
-docs match the current code." Explain the boundary: /work manages in-progress/, /docs
-manages permanent docs/.
-Verify: Create a task with \`/work create "practice task"\`, run /work save, inspect the
-file. Then run /docs to browse docs/.
-Observation focus: task tracking workflow, /work vs /docs separation.
-
-When automation is custom:
-Read \`.claude/commands/work.md\`. Full /work coverage:
-/work create (kebab-case filename, frontmatter with status, Objective/Plan/Progress/
-Resume Context sections), /work save (Progress + Resume Context update), /work resume
-(multiple-task disambiguation), /work complete (moves to final location).
-Then read \`.claude/commands/docs.md\`. Cover /docs operations:
-/docs (default): browse permanent docs/, categorized with read-only auto-generated files
-separate; /docs create: interview-driven, resource-aware doc creation from src/ code
-analysis; /docs verify: cross-references resource IDs, schema fields, platform tools in
-docs against src/ -- standalone analog of /meta fix step 5.
-Explain the relationship: /work owns docs/in-progress/ (task lifecycle), /work complete
-moves docs to permanent location, /docs browses and verifies what's there.
-Verify: Create a task doc, save progress, run /work complete to move it. Then run /docs
-to see it in the permanent docs/ listing.
-Observation focus: task doc anatomy, /work-to-/docs handoff, docs verification as standalone tool.
-
-**MF4: Rules, Memory, and Customization**
+**Item 20: Rules, Memory, and Customization**
 
 When automation is none:
 "The assistant has a set of reminders specific to your project. Over time, when it
@@ -46050,7 +46029,7 @@ Observation focus: customization concept, owned vs managed files.
 
 When automation is low-code:
 Show the \`.claude/rules/\` directory. Explain the two types: sdk-patterns.md (MANAGED --
-updated by elevasis update) and workspace-patterns.md (INIT_ONLY -- yours to edit).
+updated by elevasis-sdk update) and workspace-patterns.md (INIT_ONLY -- yours to edit).
 Explain path-scoping briefly: "These rules only activate when the agent is working on
 certain file types." Show an example rule with WRONG/RIGHT pattern. Explain error
 promotion: if something goes wrong 3+ times, add it here.
@@ -46067,7 +46046,7 @@ workspace-patterns.md. Walk through how to add a new rule.
 Verify: Read \`.claude/rules/workspace-patterns.md\`. Add a sample rule entry together.
 Observation focus: MANAGED vs INIT_ONLY lifecycle, rule authoring, memory layout.
 
-**MF5: Advanced -- Template Lifecycle and Extending**
+**Item 21: Template Lifecycle**
 
 When automation is none:
 "When Elevasis SDK releases updates, the assistant can apply them to your workspace
@@ -46080,7 +46059,7 @@ Next steps: point to reference docs in docs/, encourage using /work for new task
 Observation focus: update model concept, project map as navigation aid.
 
 When automation is low-code:
-Explain MANAGED (auto-updated by elevasis update) vs INIT_ONLY (set once, yours).
+Explain MANAGED (auto-updated by elevasis-sdk update) vs INIT_ONLY (set once, yours).
 Show how /meta fix applies SDK updates with conflict handling: "If a file changed,
 it shows you both versions and lets you decide."
 Show \`docs/project-map.mdx\` and explain what it contains: resources, commands,
@@ -46104,7 +46083,7 @@ Observation focus: full template lifecycle, conflict resolution pattern.
 
 **automation: none**
 Use the non-technical variant for each lesson. Agent writes all code -- user
-never types code. Agent runs \`elevasis exec\` for verification and narrates results.
+never types code. Agent runs \`elevasis-sdk exec\` for verification and narrates results.
 Avoid all jargon; use analogies. CLI is the primary verification tool.
 Always deploy before directing the user to the Command Center.
 
@@ -46118,7 +46097,7 @@ for intermediate/advanced users.
 
 **General rules (all levels)**
 - If user is fast, acknowledge and offer to skip ahead within a lesson
-- After each lesson, update \`.claude/memory/tutorial-progress.md\`
+- After the user confirms readiness at the end of a lesson, update \`.claude/memory/tutorial-progress.md\`
 - If user demonstrates a level change, promote to skills.md Growth Log
 - After completing a module, show the updated full menu table
 - Adapt module depth to skill level as with lessons
@@ -46137,7 +46116,7 @@ Last Session: {today's date}
 
 ## Completed Lessons
 
-| Lesson | Title | Completed | Duration |
+| Item | Title | Completed | Duration |
 | --- | --- | --- | --- |
 
 ## Completed Modules
@@ -46145,11 +46124,6 @@ Last Session: {today's date}
 | Module | Title | Completed | Duration |
 | --- | --- | --- | --- |
 
-## Completed MF Lessons
-
-| Lesson | Title | Completed | Notes |
-| --- | --- | --- | --- |
-
 ## Capability Observations
 
 | Source | Observation |
@@ -46161,13 +46135,14 @@ Last Session: {today's date}
 \`\`\`
 
 Update rules:
-- \`Current\`: free-form, e.g. "L4: Using Platform Tools" or "M:integrations" or "MF2"
+- \`Current\`: free-form, e.g. "4: Using Platform Tools" or "M:integrations" or "20: Rules, Memory, and Customization"
 - \`Last Session\`: update to today's date on each \`/tutorial\` invocation
-- Completed tables: add a row when a lesson/module/MF lesson finishes
-- Capability Observations: prefix source with L# for lessons, M:<id> for modules, MF# for MF lessons
+- Completed Lessons: add a row when any numbered item (1-10, 20-21) finishes
+- Completed Modules: add a row when any module (items 11-19) finishes
+- Capability Observations: prefix source with item number for lessons (#), M:<id> for modules
 - Assessment Notes: bullet points of general skill observations
 
-Backward-compatible: missing Completed Modules or Completed MF Lessons sections treated as empty.
+Backward-compatible: missing Completed Modules treated as empty. Old files with Completed MF Lessons: map entries to items 2-4 and 20-21 by lesson title match.
 `;
 }
 function claudeMetaCommandTemplate() {
@@ -46200,7 +46175,7 @@ by the \`<!-- initialized: false -->\` flag in CLAUDE.md, or run manually.
    \`\`\`
    No other keys (no \`NODE_ENV\`, no extras). The \`.env\` file must contain
    only \`ELEVASIS_PLATFORM_KEY\`.
-   Validate the key works: run \`elevasis resources\` (should return an empty
+   Validate the key works: run \`elevasis-sdk resources\` (should return an empty
    list, not an auth error). If auth fails, tell the user their key appears
    invalid and ask them to check it in the Elevasis dashboard.
 
@@ -46261,7 +46236,7 @@ by the \`<!-- initialized: false -->\` flag in CLAUDE.md, or run manually.
    - If git remote exists: note remote URL in memory/profile/preferences.md
 
 5. **Verify project**
-   Run \`elevasis check\` to confirm the starter resource is valid.
+   Run \`elevasis-sdk check\` to confirm the starter resource is valid.
    Optionally deploy the echo workflow.
 
 6. **Report**
@@ -46278,8 +46253,7 @@ by the \`<!-- initialized: false -->\` flag in CLAUDE.md, or run manually.
 ### \`/meta\` (no arguments) -- Project Status
 
 Display a project health summary:
-1. Current template version vs latest available
-2. SDK package version from package.json
+1. Template version (from elevasis.config.ts) and installed SDK version (from package.json). Suggest \`elevasis-sdk update\` to check for updates
 3. Profile summary (from memory/profile/skills.md)
 4. Quick drift check: count of missing managed files, missing gitignore entries
 5. Last deployment status (from memory/deployment-state.md if it exists)
@@ -46290,7 +46264,7 @@ Detect and repair all drift. Optionally upgrades the SDK first.
 
 0. **SDK version check** -- Compare installed \`@elevasis/sdk\` against the latest
    available. If behind, offer to run \`pnpm update @elevasis/sdk\` before
-   continuing. If the user accepts, run it, then run \`elevasis update\` to add
+   continuing. If the user accepts, run it, then run \`elevasis-sdk update\` to add
    any new managed files and flag conflicts. For each flagged file:
    - Read the current project file and the new template from \`@elevasis/sdk/templates\`
    - Add new sections that don't exist; preserve user customizations
@@ -46319,7 +46293,7 @@ Detect and repair all drift. Optionally upgrades the SDK first.
    suggest adding patterns. Surface suggestions only -- do not auto-generate.
 8. **Project map freshness:** Check whether \`docs/project-map.mdx\` reflects the
    current project state (resources, commands, rules, skills, memory files).
-   Compare filesystem state against the map. If stale, run \`elevasis deploy\`
+   Compare filesystem state against the map. If stale, run \`elevasis-sdk deploy\`
    to regenerate, or patch inline for minor drift.
 
 Each step reports its result. Steps 1-8 run even if step 0 is skipped.
@@ -46329,11 +46303,11 @@ Each step reports its result. Steps 1-8 run even if step 0 is skipped.
 0. Read \`reference/deployment/command-view.mdx\` -- understand the Command View
    model, relationship declarations, and what deploy-time validation checks.
    This context is essential for diagnosing validation failures in steps 1-2.
-1. Run \`elevasis check\` (validation)
+1. Run \`elevasis-sdk check\` (validation)
 2. Type check if \`tsconfig.json\` exists
 3. Verify docs reflect current resources
 4. If git configured: stage changes, commit with deploy message
-5. Run \`elevasis deploy\`
+5. Run \`elevasis-sdk deploy\`
 6. \`docs/project-map.mdx\` is auto-regenerated by deploy (no manual bump needed)
 7. Verify deployment via platform
 8. Update \`memory/deployment-state.md\` with count, timestamp, inventory
@@ -46846,7 +46820,7 @@ occurred multiple times or represent a deliberate convention -- not speculative
 ## Rule File Ownership
 
 This file is yours. The other \`.claude/rules/\` files are SDK-owned and updated by
-\`elevasis update\` -- do not add project-specific notes to them, add them here instead:
+\`elevasis-sdk update\` -- do not add project-specific notes to them, add them here instead:
 
 - \`sdk-patterns.md\` -- SDK imports, source structure, runtime, adapter patterns
 - \`docs-authoring.md\` -- MDX escaping, frontmatter, docs conventions
@@ -46931,10 +46905,10 @@ description: Project map conventions -- auto-generated, do not edit, maintained
 
 # Project Map
 
-- \`docs/project-map.mdx\` and \`docs/resource-map.mdx\` are fully auto-generated by \`elevasis deploy\`
+- \`docs/project-map.mdx\` and \`docs/resource-map.mdx\` are fully auto-generated by \`elevasis-sdk deploy\`
 - Do not edit either file manually -- changes are overwritten on next deploy
 - \`/meta fix\` step 8 checks for drift and patches the map
-- If a new command, rule, skill, or memory file is added, run \`/meta fix\` or \`elevasis deploy\` to update
+- If a new command, rule, skill, or memory file is added, run \`/meta fix\` or \`elevasis-sdk deploy\` to update
 `;
 }
 function claudeTaskTrackingRuleTemplate() {
@@ -47180,8 +47154,7 @@ function getUIFiles(orgSlug) {
     "ui/src/App.tsx": uiAppTsxTemplate(),
     "ui/src/AuthRedirect.tsx": uiAuthRedirectTemplate(),
     "ui/src/vite-env.d.ts": uiViteEnvDtsTemplate(),
-    "ui/.env": uiEnvTemplate(),
-    "ui/.env.example": uiEnvExampleTemplate()
+    "ui/.env": uiEnvTemplate()
   };
 }
 function uiPackageJsonTemplate(orgSlug) {
@@ -47320,10 +47293,6 @@ function uiEnvTemplate() {
   return `VITE_WORKOS_CLIENT_ID=
 `;
 }
-function uiEnvExampleTemplate() {
-  return `VITE_WORKOS_CLIENT_ID=your_workos_client_id
-`;
-}
 
 // src/cli/commands/templates/ui/index.ts
 var UI_INIT_FILES = [
@@ -47335,8 +47304,7 @@ var UI_INIT_FILES = [
   "ui/src/App.tsx",
   "ui/src/AuthRedirect.tsx",
   "ui/src/vite-env.d.ts",
-  "ui/.env",
-  "ui/.env.example"
+  "ui/.env"
 ];
 
 // src/cli/commands/init.ts
@@ -47345,7 +47313,6 @@ var INIT_ONLY_FILES = [
   "pnpm-workspace.yaml",
   "tsconfig.json",
   ".env",
-  ".env.example",
   ".npmrc",
   "src/index.ts",
   "src/operations/platform-status.ts",
@@ -47372,11 +47339,12 @@ var MANAGED_FILES = [
   ".claude/rules/docs-authoring.md",
   ".claude/rules/memory-conventions.md",
   ".claude/rules/project-map.md",
-  ".claude/rules/task-tracking.md"
+  ".claude/rules/task-tracking.md",
+  ".claude/scripts/statusline-command.js"
 ];
 var SCAFFOLD_FILES = [...INIT_ONLY_FILES, ...MANAGED_FILES];
 function registerInitCommand(program3) {
-  program3.command("init [directory]").description("Scaffold a new Elevasis workspace\n  Example: elevasis init my-workspace").option("--force", "Overwrite existing files").option("--ui", "Include a Vite + React UI app in ui/").action(wrapAction("init", async (directory, options2) => {
+  program3.command("init [directory]").description("Scaffold a new Elevasis workspace\n  Example: elevasis-sdk init my-workspace").option("--force", "Overwrite existing files").option("--ui", "Include a Vite + React UI app in ui/").action(wrapAction("init", async (directory, options2) => {
     const targetDir = directory ? (0, import_path3.resolve)(directory) : process.cwd();
     const orgSlug = toSlug((0, import_path3.basename)(targetDir));
     if (!options2.force) {
@@ -47403,6 +47371,7 @@ function registerInitCommand(program3) {
     await (0, import_promises2.mkdir)((0, import_path3.resolve)(targetDir, "src/shared"), { recursive: true });
     await (0, import_promises2.mkdir)((0, import_path3.resolve)(targetDir, "docs/in-progress"), { recursive: true });
     await (0, import_promises2.mkdir)((0, import_path3.resolve)(targetDir, ".claude/hooks"), { recursive: true });
+    await (0, import_promises2.mkdir)((0, import_path3.resolve)(targetDir, ".claude/scripts"), { recursive: true });
     await (0, import_promises2.mkdir)((0, import_path3.resolve)(targetDir, ".claude/commands"), { recursive: true });
     await (0, import_promises2.mkdir)((0, import_path3.resolve)(targetDir, ".claude/skills/creds"), { recursive: true });
     await (0, import_promises2.mkdir)((0, import_path3.resolve)(targetDir, ".claude/rules"), { recursive: true });
@@ -47415,7 +47384,6 @@ function registerInitCommand(program3) {
       "pnpm-workspace.yaml": pnpmWorkspaceTemplate(),
       "tsconfig.json": tsconfigTemplate(),
       ".env": envTemplate(),
-      ".env.example": envExampleTemplate(),
       ".npmrc": npmrcTemplate(),
       ".gitignore": gitignoreTemplate({ hasUI: options2.ui }),
       "src/index.ts": starterTemplate(),
@@ -47439,7 +47407,8 @@ function registerInitCommand(program3) {
       ".claude/rules/docs-authoring.md": claudeDocsAuthoringRuleTemplate(),
       ".claude/rules/memory-conventions.md": claudeMemoryConventionsRuleTemplate(),
       ".claude/rules/project-map.md": claudeProjectMapRuleTemplate(),
-      ".claude/rules/task-tracking.md": claudeTaskTrackingRuleTemplate()
+      ".claude/rules/task-tracking.md": claudeTaskTrackingRuleTemplate(),
+      ".claude/scripts/statusline-command.js": claudeStatuslineScriptTemplate()
     };
     if (options2.ui) {
       Object.assign(files, getUIFiles(orgSlug));
@@ -47454,9 +47423,9 @@ function registerInitCommand(program3) {
       console.log(source_default.gray(`    cd ${directory}`));
     }
     console.log(source_default.gray("    pnpm install"));
-    console.log(source_default.gray("    # Copy .env.example to .env and add your API key"));
-    console.log(source_default.gray("    elevasis check"));
-    console.log(source_default.gray("    elevasis deploy"));
+    console.log(source_default.gray("    # Add your API key to .env"));
+    console.log(source_default.gray("    elevasis-sdk check"));
+    console.log(source_default.gray("    elevasis-sdk deploy"));
     if (options2.ui) {
       console.log("");
       console.log(source_default.gray("  UI app:"));
@@ -47769,7 +47738,7 @@ async function listCreds(apiUrl, json2) {
   }
   if (data.credentials.length === 0) {
     console.log(source_default.yellow("No credentials found."));
-    console.log(source_default.gray("Create one with: elevasis creds create --name my-key --type api-key"));
+    console.log(source_default.gray("Create one with: elevasis-sdk creds create --name my-key --type api-key"));
     return;
   }
   console.log(source_default.cyan(`
@@ -47861,7 +47830,7 @@ Example: --value '{"apiKey":"sk-new-key"}'`
     spinner.stop();
     throw new Error(
       `Credential '${name}' not found.
-Run "elevasis creds list" to see available credentials.`
+Run "elevasis-sdk creds list" to see available credentials.`
     );
   }
   await apiPatch(`/api/external/credentials/${credential.id}`, { value }, apiUrl);
@@ -47888,7 +47857,7 @@ async function renameCreds(apiUrl, name, newName) {
     spinner.stop();
     throw new Error(
       `Credential '${name}' not found.
-Run "elevasis creds list" to see available credentials.`
+Run "elevasis-sdk creds list" to see available credentials.`
     );
   }
   const conflict = data.credentials.find((c) => c.name === newName);
@@ -47922,7 +47891,7 @@ async function deleteCreds(apiUrl, name, force) {
     spinner.stop();
     throw new Error(
       `Credential '${name}' not found.
-Run "elevasis creds list" to see available credentials.`
+Run "elevasis-sdk creds list" to see available credentials.`
     );
   }
   spinner.stop();
@@ -47971,22 +47940,22 @@ function registerCredsCommand(program3) {
 // src/cli/index.ts
 (0, import_dotenv.config)({ path: (0, import_path5.resolve)(process.cwd(), ".env"), override: true });
 var program2 = new Command();
-program2.name("elevasis").description(
+program2.name("elevasis-sdk").description(
   source_default.cyan("Elevasis SDK CLI") + `
 
 Commands:
-  elevasis check                                Validate project resources
-  elevasis deploy                               Bundle and deploy to platform
-  elevasis resources                            List deployed resources
-  elevasis describe <resourceId>                Describe a resource
-  elevasis exec <resourceId> -i '{}'            Execute a resource
-  elevasis executions <resourceId>              List execution history
-  elevasis execution <resourceId> <id>          Get execution details
-  elevasis deployments                          List deployments
-  elevasis update                              Update workspace scaffold to latest template
-  elevasis init [directory]                     Scaffold a new workspace
-
-Use "elevasis <command> --help" for more information about a command.`
+  elevasis-sdk check                                Validate project resources
+  elevasis-sdk deploy                               Bundle and deploy to platform
+  elevasis-sdk resources                            List deployed resources
+  elevasis-sdk describe <resourceId>                Describe a resource
+  elevasis-sdk exec <resourceId> -i '{}'            Execute a resource
+  elevasis-sdk executions <resourceId>              List execution history
+  elevasis-sdk execution <resourceId> <id>          Get execution details
+  elevasis-sdk deployments                          List deployments
+  elevasis-sdk update                              Update workspace scaffold to latest template
+  elevasis-sdk init [directory]                     Scaffold a new workspace
+
+Use "elevasis-sdk <command> --help" for more information about a command.`
 ).version(SDK_VERSION);
 registerCheckCommand(program2);
 registerDeployCommand(program2);