@elevasis/sdk 0.5.11 → 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
     };
   }
   /**
@@ -43811,7 +43787,7 @@ async function apiDelete(endpoint, apiUrl = resolveApiUrl()) {
 // package.json
 var package_default = {
   name: "@elevasis/sdk",
-  version: "0.5.11",
+  version: "0.5.12",
   description: "SDK for building Elevasis organization resources",
   type: "module",
   bin: {
@@ -45103,13 +45079,13 @@ var import_path3 = require("path");
 var import_promises2 = require("fs/promises");
 
 // src/cli/commands/templates/core/workspace.ts
-var TEMPLATE_VERSION = 24;
+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
 `;
@@ -45158,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
 `;
@@ -45199,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_...
@@ -45208,12 +45180,12 @@ ELEVASIS_PLATFORM_KEY=sk_...
 ## Development
 
 \`\`\`bash
-elevasis-sdk check                        # Validate resource definitions
-elevasis-sdk deploy                       # Bundle and deploy to platform
-elevasis-sdk exec <resourceId> --input '...'  # Execute a resource
-elevasis-sdk resources                    # List deployed resources
-elevasis-sdk describe <resourceId>        # Show resource definition + schemas
-elevasis-sdk 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
@@ -45234,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-sdk exec platform-status --input '{"timeRange": "24h"}'
+pnpm exec elevasis-sdk exec platform-status --input '{"timeRange": "24h"}'
 \`\`\`
 
 **Input:** \`{ "timeRange": "1h" | "24h" | "7d" }\`
@@ -45246,7 +45218,7 @@ A simple workflow that echoes the input message back. Use it as a starter patter
 for new workflows:
 
 \`\`\`bash
-elevasis-sdk exec echo --input '{"message": "hello"}'
+pnpm exec elevasis-sdk exec echo --input '{"message": "hello"}'
 \`\`\`
 
 **Input:** \`{ "message": string }\`
@@ -45499,13 +45471,18 @@ All \`reference/\` paths resolve to \`node_modules/@elevasis/sdk/reference/\`.
 
 ## Elevasis CLI
 
-**MANDATORY:** Use the \`elevasis-sdk\` 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-sdk exec <resource-id> --input '{...}'\` -- run a resource synchronously
-- \`elevasis-sdk exec <resource-id> --input '{...}' --async\` -- run async, returns execution ID
-- \`elevasis-sdk execution <resource-id> <execution-id>\` -- inspect execution detail
-- \`elevasis-sdk check\` -- validate resource definitions without deploying
-- \`elevasis-sdk 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\`
@@ -45657,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.
 \`\`\`
@@ -45695,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
@@ -45705,12 +45684,12 @@ 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
@@ -45730,7 +45709,108 @@ 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",
@@ -45747,7 +45827,7 @@ 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:
@@ -45770,7 +45850,7 @@ 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
@@ -45792,7 +45872,7 @@ 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
@@ -45808,7 +45888,7 @@ 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
@@ -45824,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
@@ -45843,7 +45923,7 @@ 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).
@@ -45928,114 +46008,14 @@ Compare agent vs workflow for a task.
 Key concepts: agent definition, tool registration, LLM tool calling, execution trace.
 Verify: Run agent with \`elevasis-sdk 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.
-
-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
@@ -46066,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
@@ -46117,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
@@ -46136,7 +46116,7 @@ Last Session: {today's date}
 
 ## Completed Lessons
 
-| Lesson | Title | Completed | Duration |
+| Item | Title | Completed | Duration |
 | --- | --- | --- | --- |
 
 ## Completed Modules
@@ -46144,11 +46124,6 @@ Last Session: {today's date}
 | Module | Title | Completed | Duration |
 | --- | --- | --- | --- |
 
-## Completed MF Lessons
-
-| Lesson | Title | Completed | Notes |
-| --- | --- | --- | --- |
-
 ## Capability Observations
 
 | Source | Observation |
@@ -46160,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() {
@@ -46277,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)
@@ -47179,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) {
@@ -47319,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 = [
@@ -47334,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
@@ -47344,7 +47313,6 @@ var INIT_ONLY_FILES = [
   "pnpm-workspace.yaml",
   "tsconfig.json",
   ".env",
-  ".env.example",
   ".npmrc",
   "src/index.ts",
   "src/operations/platform-status.ts",
@@ -47416,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(),
@@ -47456,7 +47423,7 @@ 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("    # 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) {