@elevasis/sdk 0.5.9 → 0.5.11

package/reference/deployment/api.mdx

@@ -245,7 +245,7 @@ Upload a resource bundle and deploy it. Accepts a multipart request with the com
 }
 ```
 
-Use `elevasis deploy` from the CLI rather than calling this endpoint directly -- the CLI handles bundling, metadata generation, and status streaming automatically.
+Use `elevasis-sdk deploy` from the CLI rather than calling this endpoint directly -- the CLI handles bundling, metadata generation, and status streaming automatically.
 
 ### GET /api/external/deployments
 
@@ -284,13 +284,13 @@ The SDK CLI wraps all execution endpoints. Use these commands instead of calling
 
 | Command | API call | Purpose |
 | ------- | -------- | ------- |
-| `elevasis resources` | `GET /api/external/resources` | List all resources |
-| `elevasis describe <resource>` | `GET /api/external/resources/:id/definition` | Show resource definition |
-| `elevasis exec <resource> --input '...'` | `POST /api/external/execute` | Execute synchronously |
-| `elevasis exec <resource> --input '...' --async` | `POST /api/external/execute-async` | Execute asynchronously |
-| `elevasis executions <resource>` | `GET /api/external/executions/:id` | List execution history |
-| `elevasis execution <resource> <id>` | `GET /api/external/executions/:id/:execId` | Get execution detail |
-| `elevasis deployments` | `GET /api/external/deployments` | List deployments |
+| `elevasis-sdk resources` | `GET /api/external/resources` | List all resources |
+| `elevasis-sdk describe <resource>` | `GET /api/external/resources/:id/definition` | Show resource definition |
+| `elevasis-sdk exec <resource> --input '...'` | `POST /api/external/execute` | Execute synchronously |
+| `elevasis-sdk exec <resource> --input '...' --async` | `POST /api/external/execute-async` | Execute asynchronously |
+| `elevasis-sdk executions <resource>` | `GET /api/external/executions/:id` | List execution history |
+| `elevasis-sdk execution <resource> <id>` | `GET /api/external/executions/:id/:execId` | Get execution detail |
+| `elevasis-sdk deployments` | `GET /api/external/deployments` | List deployments |
 
 ---
 

package/reference/deployment/command-center-ui.mdx

@@ -4,7 +4,7 @@ description: Reference for the Elevasis Command Center -- what each page does, w
 loadWhen: "User asks about the Command Center UI, post-deployment workflow, or monitoring deployed resources"
 ---
 
-The Command Center is the browser UI for interacting with deployed resources. After you run `elevasis deploy`, this is where you run workflows, monitor executions, manage approvals, schedule tasks, and review logs. This reference covers each page and how it connects to your SDK code.
+The Command Center is the browser UI for interacting with deployed resources. After you run `elevasis-sdk deploy`, this is where you run workflows, monitor executions, manage approvals, schedule tasks, and review logs. This reference covers each page and how it connects to your SDK code.
 
 ---
 
@@ -103,7 +103,7 @@ The Execution Logs page shows the history of all executions across every deploye
 - Filter by `failed` status to triage production issues
 - Use date range to narrow down incidents
 
-> **SDK takeaway:** Every `elevasis exec` and every scheduled run appears here. Use this page to verify behavior after deploy and to diagnose failures before opening code.
+> **SDK takeaway:** Every `elevasis-sdk exec` and every scheduled run appears here. Use this page to verify behavior after deploy and to diagnose failures before opening code.
 
 ---
 
@@ -142,9 +142,9 @@ The Deployments page shows the history of all deployments for your organization.
 - Identify the currently active version
 - Compare resource counts across deployments
 
-**How it connects to your code:** Each `elevasis deploy` run creates a new deployment entry. The platform activates the new version atomically -- in-flight executions complete against the previous version while new executions start against the new one.
+**How it connects to your code:** Each `elevasis-sdk deploy` run creates a new deployment entry. The platform activates the new version atomically -- in-flight executions complete against the previous version while new executions start against the new one.
 
-> **SDK takeaway:** Check this page after `elevasis deploy` to confirm your resources are active. If something behaves unexpectedly, look here to confirm the latest version is live.
+> **SDK takeaway:** Check this page after `elevasis-sdk deploy` to confirm your resources are active. If something behaves unexpectedly, look here to confirm the latest version is live.
 
 ---
 

package/reference/deployment/command-view.mdx

@@ -16,8 +16,8 @@ Every resource you deploy becomes a node in the Command View. Some nodes are exe
 
 | Type | What It Does | Deployed By |
 | ---- | ------------ | ----------- |
-| Workflow | Runs step handlers in sequence or branching paths | `elevasis deploy` |
-| Agent | Autonomous LLM-powered resource with tools | `elevasis deploy` |
+| Workflow | Runs step handlers in sequence or branching paths | `elevasis-sdk deploy` |
+| Agent | Autonomous LLM-powered resource with tools | `elevasis-sdk deploy` |
 
 ### Visual-Only Nodes
 
@@ -108,7 +108,7 @@ This means the graph can drift from reality:
 
 ## Deploy-Time Validation
 
-When you run `elevasis deploy` or `elevasis check`, the SDK validates your resource definitions locally using the same `ResourceRegistry` the platform uses.
+When you run `elevasis-sdk deploy` or `elevasis-sdk check`, the SDK validates your resource definitions locally using the same `ResourceRegistry` the platform uses.
 
 ### What Gets Checked
 

package/reference/deployment/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: Deploying Resources
-description: How to deploy your Elevasis SDK resources to the platform using elevasis deploy, including configuration, validation, and environment setup
+description: How to deploy your Elevasis SDK resources to the platform using elevasis-sdk deploy, including configuration, validation, and environment setup
 loadWhen: "Preparing to deploy or debugging deploy failures"
 ---
 
@@ -10,7 +10,7 @@ Deploying your resources makes them live on the Elevasis platform and immediatel
 
 ## How Deployment Works
 
-When you run `elevasis deploy`, the CLI performs these steps in order:
+When you run `elevasis-sdk deploy`, the CLI performs these steps in order:
 
 1. **Authenticate** -- calls the API with your `ELEVASIS_API_KEY` to verify credentials and resolve your organization name
 2. **Validate** -- runs your `src/index.ts` through `ResourceRegistry`, catching the same errors as the platform
@@ -25,7 +25,7 @@ There is no local dev server and no separate staging environment. Deployed resou
 ## Running a Deploy
 
 ```bash
-elevasis deploy
+elevasis-sdk deploy
 ```
 
 **Successful deploy output:**
@@ -40,7 +40,7 @@ elevasis deploy
   Deployment: deploy_abc123
 ```
 
-Each deploy creates a new deployment record. The previous active deployment is automatically stopped. You can view all deployments with `elevasis deployments`.
+Each deploy creates a new deployment record. The previous active deployment is automatically stopped. You can view all deployments with `elevasis-sdk deployments`.
 
 ---
 
@@ -67,7 +67,7 @@ The CLI validates your resources before bundling. Validation uses the same `Reso
   2 errors. Deploy aborted.
 ```
 
-Run `elevasis check` at any time to validate without deploying.
+Run `elevasis-sdk check` at any time to validate without deploying.
 
 ---
 
@@ -113,7 +113,7 @@ Place `.env` in your project root. The CLI reads it automatically. Never commit
 
 ## Deployment Lifecycle
 
-Each call to `elevasis deploy` creates a new deployment. The platform tracks all deployments for your organization.
+Each call to `elevasis-sdk deploy` creates a new deployment. The platform tracks all deployments for your organization.
 
 | Status | Meaning |
 | ------ | ------- |
@@ -127,7 +127,7 @@ Only one deployment can be `active` at a time. Deploying again automatically mov
 **View deployment history:**
 
 ```bash
-elevasis deployments
+elevasis-sdk deployments
 ```
 
 ```

package/reference/framework/agent.mdx

@@ -10,7 +10,7 @@ Nothing here requires configuration. The agent reads these files at session star
 
 ## CLAUDE.md
 
-`CLAUDE.md` is the project instruction file for Claude Code. It is read at the start of every session and governs all agent behavior. In an Elevasis SDK project, it is generated by `elevasis init` and lives at the project root.
+`CLAUDE.md` is the project instruction file for Claude Code. It is read at the start of every session and governs all agent behavior. In an Elevasis SDK project, it is generated by `elevasis-sdk init` and lives at the project root.
 
 The file is instruction-driven by design. Non-technical developers should never need to edit it. When the agent learns a new rule worth preserving -- such as an error pattern that recurs three times -- it promotes that rule into `CLAUDE.md` automatically.
 
@@ -42,7 +42,7 @@ At the start of every session the agent runs these steps silently before respond
 
 Slash commands are short Markdown instruction files in `.claude/commands/`. When you type `/command-name` in a Claude Code session, the agent reads the corresponding file and follows its instructions.
 
-Four commands and one skill are scaffolded by `elevasis init` and committed to version control so collaborators get the same experience:
+Four commands and one skill are scaffolded by `elevasis-sdk init` and committed to version control so collaborators get the same experience:
 
 | Command | File | Purpose |
 | --- | --- | --- |
@@ -57,7 +57,7 @@ The `/creds` skill (`.claude/skills/creds/SKILL.md`) is also scaffolded. It auto
 
 The `/meta` command namespace manages the full project lifecycle. It has five operations:
 
-- **`/meta init`** -- First-run guided setup. Runs after `elevasis init` to install dependencies, configure `.env`, run the competency assessment onboarding flow, seed `memory/profile/`, verify the project, and optionally do a first deploy.
+- **`/meta init`** -- First-run guided setup. Runs after `elevasis-sdk init` to install dependencies, configure `.env`, run the competency assessment onboarding flow, seed `memory/profile/`, verify the project, and optionally do a first deploy.
 - **`/meta`** (no arguments) -- Project health status. Shows current template version, SDK version, profile summary, a quick drift check, and last deployment status.
 - **`/meta fix`** -- SDK upgrade check and drift repair. Step 0 offers to run `pnpm update @elevasis/sdk` and merge template changes. Steps 1-8 repair drift: missing managed files, gitignore entries, CLAUDE.md sections, memory structure, doc cross-references, settings, rules health, and project map freshness.
 - **`/meta deploy`** -- Full 9-step deploy pipeline: validate, type-check, verify docs, commit, deploy (auto-regenerates `docs/project-map.mdx`), verify platform, update deployment state, and optionally push.
@@ -132,7 +132,7 @@ Six rule files are scaffolded in `.claude/rules/`. Rule files are auto-injected
 | `task-tracking.md` | MANAGED | Any file in `docs/in-progress/` | `/work` command, task doc format, status values |
 | `workspace-patterns.md` | INIT_ONLY | Any file in the project | Project-specific patterns (starts empty, grows via error promotion) |
 
-MANAGED rules are updated by `elevasis update` when the SDK ships a new version. `workspace-patterns.md` is INIT_ONLY -- it belongs to the project and is never overwritten. When an error recurs 3+ times, the agent promotes a fix into this file so future sessions learn from past mistakes.
+MANAGED rules are updated by `elevasis-sdk update` when the SDK ships a new version. `workspace-patterns.md` is INIT_ONLY -- it belongs to the project and is never overwritten. When an error recurs 3+ times, the agent promotes a fix into this file so future sessions learn from past mistakes.
 
 ## Interaction Guidance
 

package/reference/framework/documentation.mdx

@@ -4,11 +4,11 @@ description: Write and deploy MDX documentation alongside your Elevasis resource
 loadWhen: "Writing or updating project documentation"
 ---
 
-`elevasis deploy` ships your code and your documentation atomically -- one command, no version drift. Documentation files live in a `docs/` directory at your project root and render in the Elevasis platform UI for operators using your resources.
+`elevasis-sdk deploy` ships your code and your documentation atomically -- one command, no version drift. Documentation files live in a `docs/` directory at your project root and render in the Elevasis platform UI for operators using your resources.
 
 ## Directory Structure
 
-Create `.mdx` files inside a `docs/` directory at your project root. `elevasis init` scaffolds a starter structure:
+Create `.mdx` files inside a `docs/` directory at your project root. `elevasis-sdk init` scaffolds a starter structure:
 
 ```
 my-project/
@@ -50,7 +50,7 @@ These limits are enforced by the CLI before the deploy request is sent. Validati
 
 ## Starter Template
 
-`elevasis init` writes this starter file to `docs/index.mdx`:
+`elevasis-sdk init` writes this starter file to `docs/index.mdx`:
 
 ```mdx
 ---
@@ -70,15 +70,15 @@ code and rendered in the Elevasis platform UI.
 ## Getting Started
 
 \`\`\`bash
-elevasis check    # Validate resources
-elevasis deploy   # Deploy to platform
-elevasis exec <resourceId> --input '{"key": "value"}'
+elevasis-sdk check    # Validate resources
+elevasis-sdk deploy   # Deploy to platform
+elevasis-sdk exec <resourceId> --input '{"key": "value"}'
 \`\`\`
 ```
 
 ## Deploy Behavior
 
-When you run `elevasis deploy`:
+When you run `elevasis-sdk deploy`:
 
 1. The CLI scans `docs/` recursively for `.mdx` files
 2. Each file's frontmatter (title, description, order) is parsed and stripped from the content

package/reference/framework/index.mdx

@@ -4,13 +4,13 @@ description: The SDK scaffolds a complete development environment for Claude Cod
 loadWhen: "Understanding the agent framework structure"
 ---
 
-`elevasis init` scaffolds more than code. It builds a development environment designed around Claude Code as the primary interface. Most external SDK developers are non-technical -- they write workflows through conversation, not by reading API docs. The framework gives the agent everything it needs to guide those users effectively from the first session onward.
+`elevasis-sdk init` scaffolds more than code. It builds a development environment designed around Claude Code as the primary interface. Most external SDK developers are non-technical -- they write workflows through conversation, not by reading API docs. The framework gives the agent everything it needs to guide those users effectively from the first session onward.
 
 The framework lives entirely in `.claude/`. It is never deployed and never touches the `docs/` directory, which ships to the platform.
 
 ## What Gets Scaffolded
 
-Running `elevasis init my-project` produces the following agent infrastructure alongside your source files:
+Running `elevasis-sdk init my-project` produces the following agent infrastructure alongside your source files:
 
 ```
 .claude/

package/reference/framework/memory.mdx

@@ -260,7 +260,7 @@ Runtime errors include the resource name since the same error in different resou
 
 | Last Seen | Resource | Error | Resolution | Occurrences |
 | --- | --- | --- | --- | --- |
-| 2026-02-26 | lead-scorer | `PlatformToolError: credential not found` | Set credential via `elevasis env set` | 1 |
+| 2026-02-26 | lead-scorer | `PlatformToolError: credential not found` | Set credential via `elevasis-sdk env set` | 1 |
 ```
 
 ### Error Resolution Flow

package/reference/framework/project-structure.mdx

@@ -1,10 +1,10 @@
 ---
 title: Project Structure
-description: Each file scaffolded by elevasis init and its purpose in the development workflow
+description: Each file scaffolded by elevasis-sdk init and its purpose in the development workflow
 loadWhen: "Understanding scaffolded files or project layout"
 ---
 
-`elevasis init` creates a complete workspace structure. This page explains what each file does and when you will interact with it.
+`elevasis-sdk init` creates a complete workspace structure. This page explains what each file does and when you will interact with it.
 
 ---
 
@@ -60,7 +60,7 @@ export default {
 } satisfies ElevasConfig
 ```
 
-Leave this file minimal -- the platform provides sensible defaults. Do not remove `templateVersion`; it is read by `elevasis update` to determine which template changes need to be applied to your project.
+Leave this file minimal -- the platform provides sensible defaults. Do not remove `templateVersion`; it is read by `elevasis-sdk update` to determine which template changes need to be applied to your project.
 
 ---
 
@@ -68,7 +68,7 @@ Leave this file minimal -- the platform provides sensible defaults. Do not remov
 
 ### `docs/index.mdx`
 
-The entry point for your workspace's documentation. Documentation files in `docs/` are deployed alongside your code during `elevasis deploy` and rendered in the Elevasis platform UI.
+The entry point for your workspace's documentation. Documentation files in `docs/` are deployed alongside your code during `elevasis-sdk deploy` and rendered in the Elevasis platform UI.
 
 Use MDX frontmatter to set page metadata:
 
@@ -84,7 +84,7 @@ Add more pages by creating additional `.mdx` files in `docs/`. Nested directorie
 
 ### `docs/project-map.mdx`
 
-Auto-generated by `elevasis deploy` on every deploy and by `/meta fix` step 8. Contains a full project snapshot: organization, SDK version, template version, last deploy date, source domains, resource tables (workflows and agents), documentation index, SDK reference summary, commands/rules/skills, memory system listing, and configuration state. The agent reads this file at session start for project orientation.
+Auto-generated by `elevasis-sdk deploy` on every deploy and by `/meta fix` step 8. Contains a full project snapshot: organization, SDK version, template version, last deploy date, source domains, resource tables (workflows and agents), documentation index, SDK reference summary, commands/rules/skills, memory system listing, and configuration state. The agent reads this file at session start for project orientation.
 
 This file is fully auto-generated -- do not edit manually. Changes are overwritten on the next deploy.
 
@@ -98,22 +98,22 @@ This file is NOT scaffolded by default. The agent creates it the first time you
 
 Work-in-progress task documents created by `/work create`. Each file represents an active work item with objective, plan, progress markers, and resume context. `/work complete` moves finished items to their permanent location in `docs/`.
 
-This directory is NOT deployed -- it is filtered out during the doc scan in `elevasis deploy`.
+This directory is NOT deployed -- it is filtered out during the doc scan in `elevasis-sdk deploy`.
 
 ---
 
 ## Progressive Disclosure Directories
 
-Only `src/` and `docs/` are scaffolded by `elevasis init`. The following directories are NOT created by default -- they appear when a specific need arises:
+Only `src/` and `docs/` are scaffolded by `elevasis-sdk init`. The following directories are NOT created by default -- they appear when a specific need arises:
 
 | Directory | Created by | When |
 |-----------|-----------|------|
-| `src/operations/` | `elevasis init` (default) | Always -- platform-status workflow lives here |
-| `src/example/` | `elevasis init` (default) | Always -- echo starter workflow lives here (replace with your own) |
-| `src/shared/` | `elevasis init` (default) | Always -- cross-domain shared utilities (starts empty) |
-| `docs/` | `elevasis init` (default) | Always |
+| `src/operations/` | `elevasis-sdk init` (default) | Always -- platform-status workflow lives here |
+| `src/example/` | `elevasis-sdk init` (default) | Always -- echo starter workflow lives here (replace with your own) |
+| `src/shared/` | `elevasis-sdk init` (default) | Always -- cross-domain shared utilities (starts empty) |
+| `docs/` | `elevasis-sdk init` (default) | Always |
 | `docs/in-progress/` | Agent (on first `/work create`) | When you create a task doc for in-progress work |
-| `docs/project-map.mdx` | `elevasis deploy` | Auto-generated on every deploy |
+| `docs/project-map.mdx` | `elevasis-sdk deploy` | Auto-generated on every deploy |
 | `docs/priorities.mdx` | Agent (on first goal discussion) | When you discuss project goals or priorities |
 | `data/` | Agent (on demand) | When you connect a database |
 | `scripts/` | Agent (on demand) | When you need local scripts not deployed to the platform |
@@ -135,9 +135,9 @@ Local utility scripts for tasks that do not run on the platform: database seeds,
 
 ---
 
-## `elevasis deploy` Scope
+## `elevasis-sdk deploy` Scope
 
-`elevasis deploy` touches only two directories:
+`elevasis-sdk deploy` touches only two directories:
 
 | Directory | Action | Deployed? |
 |-----------|--------|-----------|
@@ -271,21 +271,21 @@ Not all scaffolded files participate in template updates. Files fall into two ca
 
 **SCAFFOLD_FILES total: 30**
 
-**INIT_ONLY** (15 files) -- Written once during `elevasis init`, never updated by `elevasis update`:
+**INIT_ONLY** (15 files) -- Written once during `elevasis-sdk init`, never updated by `elevasis-sdk update`:
 - `package.json`, `pnpm-workspace.yaml`, `tsconfig.json`
 - `.env`, `.env.example`, `.npmrc`
 - `src/index.ts`, `src/operations/platform-status.ts`, `src/operations/index.ts`, `src/example/echo.ts`, `src/example/index.ts`, `src/shared/.gitkeep`
 - `docs/index.mdx`, `docs/in-progress/.gitkeep`
 - `.claude/rules/workspace-patterns.md`
 
-**MANAGED** (15 files) -- Written during `elevasis init` and checked/updatable by `elevasis update`:
+**MANAGED** (15 files) -- Written during `elevasis-sdk init` and checked/updatable by `elevasis-sdk update`:
 - `elevasis.config.ts`, `.gitignore`, `CLAUDE.md`, `.claude/settings.json`
 - One hook: `.claude/hooks/enforce-sdk-boundary.mjs`
 - Four command files: `.claude/commands/meta.md`, `.claude/commands/docs.md`, `.claude/commands/tutorial.md`, `.claude/commands/work.md`
 - One skill: `.claude/skills/creds/SKILL.md`
 - Five rule files: `.claude/rules/sdk-patterns.md`, `.claude/rules/docs-authoring.md`, `.claude/rules/memory-conventions.md`, `.claude/rules/project-map.md`, `.claude/rules/task-tracking.md`
 
-Run `elevasis update` after installing a new SDK version to bring managed files up to date. The command adds missing files directly and flags files that differ from the new template for agent-assisted review via `/meta fix`.
+Run `elevasis-sdk update` after installing a new SDK version to bring managed files up to date. The command adds missing files directly and flags files that differ from the new template for agent-assisted review via `/meta fix`.
 
 ---
 
@@ -296,7 +296,7 @@ Run `elevasis update` after installing a new SDK version to bring managed files
 | `src/index.ts` | Adding or removing resources (the `/resource` command does this automatically) |
 | `src/<domain>/*.ts` | Writing and modifying workflow logic (organized by business domain) |
 | `docs/index.mdx` | Updating project documentation |
-| `docs/project-map.mdx` | Never -- auto-generated by `elevasis deploy` |
+| `docs/project-map.mdx` | Never -- auto-generated by `elevasis-sdk deploy` |
 | `docs/priorities.mdx` | When goals or priorities change |
 | `elevasis.config.ts` | Changing project-level settings |
 | `.env` | Adding environment variables |

package/reference/getting-started/index.mdx

@@ -4,31 +4,20 @@ description: Install the Elevasis SDK, scaffold a project, and run your first de
 loadWhen: "Setting up a new project or onboarding"
 ---
 
-This guide takes you from a fresh install to a running deployment in four steps: install, scaffold, deploy, and execute.
+**Prerequisites:** Node.js 20+ and pnpm (`npm install -g pnpm`).
 
-## Installation
+## Create a Project
 
-Install the SDK and its peer dependency:
+Scaffold a new project and install dependencies:
 
 ```bash
-npm install @elevasis/sdk zod
-# or
-pnpm add @elevasis/sdk zod
-```
-
-The `.npmrc` file scaffolded by `elevasis init` sets `auto-install-peers = true`, so peer dependencies are handled automatically on subsequent installs.
-
----
-
-## Scaffold a Project
-
-Run `elevasis init` to create a new project directory with all required files:
-
-```bash
-elevasis init my-project
+pnpm dlx @elevasis/sdk init my-project
 cd my-project
+pnpm install
 ```
 
+`pnpm dlx` downloads the SDK temporarily to run `elevasis-sdk init`, which scaffolds your project with a working echo workflow, TypeScript config, and Claude Code integration. `pnpm install` then installs the SDK and its dependencies locally -- after that, all `elevasis-sdk` commands work directly via the scripts in `package.json` or `pnpm exec elevasis-sdk <command>`.
+
 The command scaffolds 29 files covering configuration, source, documentation, and Claude Code integration:
 
 ```
@@ -74,7 +63,7 @@ my-project/
 └── .gitignore                      # Excludes worker temp file, claude files
 ```
 
-The scaffolded `elevasis.config.ts` includes a `templateVersion` field that tracks which template generation your project uses. Leave it as-is -- it is managed automatically by `elevasis update`:
+The scaffolded `elevasis.config.ts` includes a `templateVersion` field that tracks which template generation your project uses. Leave it as-is -- it is managed automatically by `elevasis-sdk update`:
 
 ```ts
 import type { ElevasConfig } from '@elevasis/sdk'
@@ -109,19 +98,19 @@ If the automatic setup doesn't trigger, you can start it manually with `/meta in
 Validate your resources and deploy:
 
 ```bash
-elevasis check    # Validate resource definitions
-elevasis deploy   # Bundle and deploy to the platform
+elevasis-sdk check    # Validate resource definitions
+elevasis-sdk deploy   # Bundle and deploy to the platform
 ```
 
-`elevasis check` runs validation without deploying. Fix any errors it reports before running `elevasis deploy`.
+`elevasis-sdk check` runs validation without deploying. Fix any errors it reports before running `elevasis-sdk deploy`.
 
-`elevasis deploy` bundles your `src/` code and `docs/` documentation into a single deployment transaction. Both ship atomically -- there is no separate upload step for documentation.
+`elevasis-sdk deploy` bundles your `src/` code and `docs/` documentation into a single deployment transaction. Both ship atomically -- there is no separate upload step for documentation.
 
 After a successful deploy, confirm the resources are live:
 
 ```bash
-elevasis resources       # List deployed resources
-elevasis deployments     # Show deployment history
+elevasis-sdk resources       # List deployed resources
+elevasis-sdk deployments     # Show deployment history
 ```
 
 ---
@@ -131,14 +120,14 @@ elevasis deployments     # Show deployment history
 Execute the scaffolded echo workflow to verify end-to-end connectivity:
 
 ```bash
-elevasis exec echo --input '{"message": "hello"}'
+elevasis-sdk exec echo --input '{"message": "hello"}'
 ```
 
 View the execution result:
 
 ```bash
-elevasis executions echo    # Execution history
-elevasis execution echo \<execution-id\>  # Full detail for one execution
+elevasis-sdk executions echo    # Execution history
+elevasis-sdk execution echo \<execution-id\>  # Full detail for one execution
 ```
 
 Replace `<execution-id>` with the ID returned from the executions list.
@@ -153,7 +142,7 @@ Replace `<execution-id>` with the ID returned from the executions list.
 - [CLI Reference](../cli/index.mdx) -- Full command reference with flags
 - [Deployment](../deployment/index.mdx) -- Deployment lifecycle and environment variables
 
-When a new SDK version is released, run `/meta fix` in Claude Code for an interactive upgrade that includes SDK update, drift repair, and documentation verification. Alternatively, run `elevasis update` from the terminal to update managed files (CLAUDE.md, slash commands, `.gitignore`) without agent interaction.
+When a new SDK version is released, run `/meta fix` in Claude Code for an interactive upgrade that includes SDK update, drift repair, and documentation verification. Alternatively, run `elevasis-sdk update` from the terminal to update managed files (CLAUDE.md, slash commands, `.gitignore`) without agent interaction. To update the SDK package itself, run `pnpm update @elevasis/sdk`.
 
 ---
 

package/reference/index.mdx

@@ -9,12 +9,13 @@ loadWhen: "First session or new to the SDK"
 ## Quick Start
 
 ```bash
-npm install @elevasis/sdk
-elevasis init
-elevasis deploy
+pnpm dlx @elevasis/sdk init my-project
+cd my-project
+pnpm install
+elevasis-sdk deploy
 ```
 
-After `elevasis init`, your project is scaffolded with a working echo workflow, config file, TypeScript setup, and a `CLAUDE.md` that gives Claude Code full awareness of the SDK. After `elevasis deploy`, your resources appear in AI Studio and are available to run immediately.
+After `pnpm dlx @elevasis/sdk init`, your project is scaffolded with a working echo workflow, config file, TypeScript setup, and a `CLAUDE.md` that gives Claude Code full awareness of the SDK. After `elevasis-sdk deploy`, your resources appear in AI Studio and are available to run immediately.
 
 Here is a minimal workflow definition:
 
@@ -77,7 +78,7 @@ See [Platform Tools](platform-tools/index.mdx) for the full catalog.
 ## Known Limitations
 
 - **No streaming logs** -- Execution logs are returned in the response body after completion. Real-time log streaming is not available.
-- **Agent HTTP timeouts** -- Use `elevasis exec --async` for agent executions. Agents can run for minutes; the synchronous endpoint will time out for long-running runs. The `--async` flag returns an execution ID immediately and polls for the result.
+- **Agent HTTP timeouts** -- Use `elevasis-sdk exec --async` for agent executions. Agents can run for minutes; the synchronous endpoint will time out for long-running runs. The `--async` flag returns an execution ID immediately and polls for the result.
 
 ## Documentation
 

package/reference/platform-tools/index.mdx

@@ -136,12 +136,12 @@ The invoked resource must belong to the same organization. The `organizationId`
 
 ## Managing Environment Variables
 
-Use the `elevasis env` CLI to manage environment variables for your deployed workers:
+Use the `elevasis-sdk env` CLI to manage environment variables for your deployed workers:
 
 ```bash
-elevasis env list
-elevasis env set KEY value
-elevasis env remove KEY
+elevasis-sdk env list
+elevasis-sdk env set KEY value
+elevasis-sdk env remove KEY
 ```
 
 Environment variables set this way are injected into your worker process at startup and are available via `process.env`.

package/reference/resources/index.mdx

@@ -266,7 +266,7 @@ const myStep: StepHandler = async (input, context) => {
 
 Agents are autonomous resources that use an LLM and tools to complete a goal. You define them with `AgentDefinition`.
 
-**Note:** Use `elevasis exec --async` when executing agents. Agents can run for minutes or longer, and the synchronous execute endpoint will time out for long-running runs. The `--async` flag returns an execution ID immediately and polls for the result.
+**Note:** Use `elevasis-sdk exec --async` when executing agents. Agents can run for minutes or longer, and the synchronous execute endpoint will time out for long-running runs. The `--async` flag returns an execution ID immediately and polls for the result.
 
 ```typescript
 import type { AgentDefinition } from '@elevasis/sdk';
@@ -308,13 +308,13 @@ const org: OrganizationResources = {
 export default org;
 ```
 
-The keys under `workflows` and `agents` are used as resource identifiers on the platform. They appear in CLI output (`elevasis resources`), execution commands (`elevasis exec`), and the dashboard.
+The keys under `workflows` and `agents` are used as resource identifiers on the platform. They appear in CLI output (`elevasis-sdk resources`), execution commands (`elevasis-sdk exec`), and the dashboard.
 
 ### Resource Status
 
 Set `config.status` to control whether the platform accepts execution requests:
 
-- `'dev'` - Resource is visible in the dashboard but the platform will not route scheduled or webhook-triggered executions to it. You can still trigger it manually via `elevasis exec`.
+- `'dev'` - Resource is visible in the dashboard but the platform will not route scheduled or webhook-triggered executions to it. You can still trigger it manually via `elevasis-sdk exec`.
 - `'production'` - Resource is live and accepts all execution sources.
 
 Use `'dev'` while you are building and testing. Switch to `'production'` when you are ready to go live.

package/reference/resources/patterns.mdx

@@ -131,7 +131,7 @@ const sendEmailStep: WorkflowStep = {
 **Key points:**
 
 - `platform.call()` is async and times out after 60 seconds
-- `credential` is the name of a platform environment variable set via `elevasis env set`
+- `credential` is the name of a platform environment variable set via `elevasis-sdk env set`
 - On failure, `platform.call()` throws `PlatformToolError` (not `ToolingError`)
 - Always log success so executions are easy to debug in the dashboard
 
@@ -274,8 +274,8 @@ const myWorkflow: WorkflowDefinition = {
 
 Dev resources:
 
-- Appear in `elevasis resources` output
-- Can be triggered with `elevasis exec my-workflow --input '{...}'`
+- Appear in `elevasis-sdk resources` output
+- Can be triggered with `elevasis-sdk exec my-workflow --input '{...}'`
 - Will NOT receive scheduled or webhook-triggered executions
 - Will NOT appear as available to external callers
 

package/reference/resources/types.mdx

@@ -6,8 +6,8 @@ loadWhen: "Looking up type signatures or SDK exports"
 
 `@elevasis/sdk` is published to the public npm registry. It bundles all platform types from `@repo/core` into a single self-contained type declaration file with zero internal monorepo references. External developers install the package and get full TypeScript support without any monorepo tooling.
 
-```
-npm install @elevasis/sdk zod
+```bash
+pnpm add @elevasis/sdk zod
 ```
 
 Zod is a peer dependency and must be installed separately.

package/reference/roadmap/index.mdx

@@ -108,7 +108,7 @@ Metrics are aggregated at multiple levels:
 - **Per-execution:** Total AI spend and total duration
 - **Per-resource:** Aggregated over configurable time periods (daily, weekly, monthly)
 - **Per-organization:** Total platform cost (execution time + AI spend + managed hosting compute)
-- **Visibility:** Platform dashboard and the CLI via `elevasis executions <resourceId>`
+- **Visibility:** Platform dashboard and the CLI via `elevasis-sdk executions <resourceId>`
 
 ### Developer-Defined Metrics
 

package/reference/runtime/index.mdx

@@ -59,7 +59,7 @@ Cancellation is initiated by the platform and requires no special code in your h
 Errors are displayed depending on the surface you use to inspect them:
 
 - **AI Studio:** Shows the error message and execution status. Example: `Remote resource 'onboard-client' failed: Email delivery failed: invalid address`
-- **CLI (`elevasis execution <resourceId> <id>`):** Shows full execution detail including the error message. The `--json` flag includes an `error` field in structured output.
+- **CLI (`elevasis-sdk execution <resourceId> <id>`):** Shows full execution detail including the error message. The `--json` flag includes an `error` field in structured output.
 - **Error message source:** The error string comes directly from your handler's catch block (`String(err)`). The platform stores this verbatim and displays it as-is. Write descriptive error messages in your handlers -- they surface directly to users.
 
 ### What Causes a Failed Execution
@@ -92,7 +92,7 @@ Logs are delivered to the platform atomically with the execution result:
 
 - **Retention:** 30 days by default (configurable per plan).
 - **Real-time fanout:** After execution completes, logs are stored and fanned out to AI Studio and CLI subscribers. AI Studio shows them in the execution detail view.
-- **CLI access:** Use `elevasis execution <resourceId> <id>` to view execution details including logs.
+- **CLI access:** Use `elevasis-sdk execution <resourceId> <id>` to view execution details including logs.
 
 ---
 
@@ -114,7 +114,7 @@ v1 versioning is intentionally simple:
 
 ### Deletion
 
-- **Via CLI:** Remove the resource from your `OrganizationResources` export and run `elevasis deploy`. Resources absent from the new bundle are automatically deregistered from the platform.
+- **Via CLI:** Remove the resource from your `OrganizationResources` export and run `elevasis-sdk deploy`. Resources absent from the new bundle are automatically deregistered from the platform.
 - **Via AI Studio:** The delete button unregisters the resource immediately and marks the deployment stopped.
 - **In-flight executions:** Workers already running complete normally. Deletion affects only new execution attempts.
 - **Data retention:** Execution logs and history for a deleted resource are retained for 30 days, then purged.

package/reference/security/credentials.mdx

@@ -115,7 +115,7 @@ Credential names are case-sensitive. A mismatch causes a `PlatformToolError` wit
 ELEVASIS_API_KEY=sk_your_key_here
 ```
 
-This key authenticates CLI operations (`elevasis deploy`, `elevasis check`, `elevasis exec`). It is never uploaded to the platform and never injected into workers.
+This key authenticates CLI operations (`elevasis-sdk deploy`, `elevasis-sdk check`, `elevasis-sdk exec`). It is never uploaded to the platform and never injected into workers.
 
 Do not put integration API keys in `.env`. They will not be available inside workflows.
 
@@ -132,9 +132,9 @@ Do not put integration API keys in `.env`. They will not be available inside wor
 
 ---
 
-## Migrating from elevasis env
+## Migrating from elevasis-sdk env
 
-If you previously set integration credentials via `elevasis env set`, that command no longer exists. Use `elevasis env list` to see what was set, then recreate each entry as a platform credential in the command center. Update workflow code from `process.env.KEY` to `platform.call({ tool: 'http', credential: '...', ... })` or `platform.getCredential('...')`, then redeploy. The `.env` file remains but is scoped to `ELEVASIS_API_KEY` only.
+If you previously set integration credentials via `elevasis-sdk env set`, that command no longer exists. Use `elevasis-sdk env list` to see what was set, then recreate each entry as a platform credential in the command center. Update workflow code from `process.env.KEY` to `platform.call({ tool: 'http', credential: '...', ... })` or `platform.getCredential('...')`, then redeploy. The `.env` file remains but is scoped to `ELEVASIS_API_KEY` only.
 
 ---