@elevasis/sdk 1.48.0 → 1.50.0

package/reference/sdk/cli.mdx

@@ -13,7 +13,7 @@ pnpm add @elevasis/sdk
 
 After installation, the `elevasis-sdk` binary is available in your project's `node_modules/.bin/`. Most commands require `ELEVASIS_PLATFORM_KEY` to be set in your environment or a `.env` file.
 
-For management commands (project:\*, note:\*, acquisition:\*, client:\*, agent:\*, session:\*, queue:\*, schedule:\*, om:\*, ui:\*, skill:\*), see [CLI Management](cli-management.mdx).
+For management commands (project:\*, note:\*, error:\*, acquisition:\*, client:\*, agent:\*, session:\*, queue:\*, schedule:\*, om:\*, ui:\*, skill:\*, content:\*, request:\*, grant:\*), see [CLI Management](cli-management.mdx).
 
 ---
 
@@ -41,6 +41,13 @@ elevasis-sdk check
 
 `check` declares no `--api-url` flag -- it validates project source locally and never calls the API, so there is no base URL to override.
 
+**Flags:**
+
+| Flag              | Description                                        |
+| ----------------- | -------------------------------------------------- |
+| `--entry <path>`  | Path to the entry file (default: `./src/index.ts`) |
+| `--skip-coverage` | Skip the skill coverage gate                       |
+
 **Example output (success):**
 
 ```
@@ -84,10 +91,14 @@ elevasis-sdk deploy
 
 **Flags:**
 
-| Flag                | Description                                                |
-| ------------------- | ---------------------------------------------------------- |
-| `--api-url <url>` | Override the API base URL (default: production)            |
-| `--prod`            | Force production target, overriding `NODE_ENV=development` |
+| Flag              | Description                                                  |
+| ----------------- | ------------------------------------------------------------ |
+| `--api-url <url>` | Override the API base URL (default: production)              |
+| `--entry <path>`  | Path to the entry file (default: `./src/index.ts`)           |
+| `--prod`          | Force production target, overriding `NODE_ENV=development`   |
+| `--major`         | Bump the major version before deploying (`1.0.0` -> `2.0.0`) |
+| `--minor`         | Bump the minor version before deploying (`1.0.0` -> `1.1.0`) |
+| `--patch`         | Bump the patch version before deploying (`1.0.0` -> `1.0.1`) |
 
 **Environment variables:**
 
@@ -141,15 +152,20 @@ elevasis-sdk exec <resource> --input '{...}'
 - Use `--async` to return an `executionId` immediately and poll for completion
 - `--input` accepts a JSON string matching the resource's `inputSchema`
 - Organization is derived from your API key -- no org prefix needed
+- On a lost connection during a synchronous run, the CLI looks up the most recent running execution for the resource and resumes polling rather than failing outright
 
 **Flags:**
 
-| Flag                | Description                                             |
-| ------------------- | ------------------------------------------------------- |
-| `--input <json>`  | JSON input matching the resource's input schema         |
-| `--async`           | Execute asynchronously, return execution ID immediately |
-| `--json`            | Output raw JSON instead of formatted display            |
-| `--api-url <url>` | Override the API base URL                               |
+| Flag                      | Description                                                                                                               |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
+| `-i, --input <json>`      | JSON input matching the resource's input schema                                                                           |
+| `-f, --input-file <path>` | Read input from a JSON file instead of `--input` (avoids shell escaping). Relative paths resolve against the project root |
+| `--async`                 | Execute asynchronously, return execution ID immediately                                                                   |
+| `--cleanup-input`         | Delete the input file after a successful execution (only files under `<projectRoot>/tmp/` are eligible)                   |
+| `--prod`                  | Target production (overrides `NODE_ENV=development`)                                                                      |
+| `--api-url <url>`         | Override the API base URL                                                                                                 |
+
+`exec` does not declare a `--json` flag -- output is always the formatted display shown below.
 
 **Example:**
 
@@ -202,9 +218,9 @@ elevasis-sdk resources
 
 **Flags:**
 
-| Flag                | Description               |
-| ------------------- | ------------------------- |
-| `--json`            | Output raw JSON           |
+| Flag              | Description               |
+| ----------------- | ------------------------- |
+| `--json`          | Output raw JSON           |
 | `--api-url <url>` | Override the API base URL |
 
 **Example output:**
@@ -238,11 +254,11 @@ elevasis-sdk executions [resource]
 
 **Flags:**
 
-| Flag                  | Description                                                     |
-| --------------------- | --------------------------------------------------------------- |
-| `--limit <n>`       | Maximum number of executions to return (default: 20)            |
+| Flag                | Description                                                     |
+| ------------------- | --------------------------------------------------------------- |
+| `--limit <n>`       | Maximum number of executions to return (default: 50)            |
 | `--status <status>` | Filter by status: `running`, `completed`, `failed`, `cancelled` |
-| `--json`              | Output raw JSON                                                 |
+| `--json`            | Output raw JSON                                                 |
 | `--api-url <url>`   | Override the API base URL                                       |
 
 **Example:**
@@ -273,15 +289,21 @@ elevasis-sdk execution <resource> <id>
 
 **Behavior:**
 
-- Shows the complete execution record: input, output, logs, duration, and error (if any)
+- Shows the complete execution record: input, result, logs, duration, and error (if any)
+- `--input` and `--result` force those sections to print even when the CLI would otherwise omit them; both print automatically when the execution carries input data, or is `completed` with a result
+- `--logs-only` prints only the execution logs and skips the rest of the record
 - Use `--json` to get the raw JSON response for programmatic use
 
 **Flags:**
 
-| Flag                | Description               |
-| ------------------- | ------------------------- |
-| `--json`            | Output raw JSON           |
-| `--api-url <url>` | Override the API base URL |
+| Flag              | Description                                          |
+| ----------------- | ---------------------------------------------------- |
+| `--logs-only`     | Show only execution logs                             |
+| `--input`         | Force the Input section to print                     |
+| `--result`        | Force the Result section to print                    |
+| `--prod`          | Target production (overrides `NODE_ENV=development`) |
+| `--json`          | Output raw JSON response                             |
+| `--api-url <url>` | Override the API base URL                            |
 
 **Example:**
 
@@ -290,10 +312,12 @@ elevasis-sdk execution onboard-client exec_abc001
 ```
 
 ```
-  Resource:   onboard-client
-  Status:     completed
-  Started:    2026-02-25 14:32:01
-  Duration:   1.2s
+  Resource:     onboard-client
+  Execution ID: exec_abc001
+  Status:       COMPLETED
+  Started:      2026-02-25 14:32:01
+  Ended:        2026-02-25 14:32:02
+  Duration:     1.2s
 
   Input:
   {
@@ -301,17 +325,20 @@ elevasis-sdk execution onboard-client exec_abc001
     "email": "jane@example.com"
   }
 
-  Output:
+  Result:
   {
     "success": true,
     "clientId": "client_1708521600000",
     "welcomeEmailSent": true
   }
 
-  Logs:
+  Execution Logs:
+
   [14:32:01.123]  Starting onboard-client workflow
   [14:32:01.456]  Created client record
   [14:32:01.891]  Welcome email sent to jane@example.com
+
+  Total logs: 3
 ```
 
 ---
@@ -334,11 +361,11 @@ elevasis-sdk execution:cancel <resourceId> <executionId>
 
 **Flags:**
 
-| Flag                | Description                                          |
-| ------------------- | ---------------------------------------------------- |
-| `--prod`            | Target production (overrides `NODE_ENV=development`) |
+| Flag              | Description                                          |
+| ----------------- | ---------------------------------------------------- |
+| `--prod`          | Target production (overrides `NODE_ENV=development`) |
 | `--api-url <url>` | Override the API base URL                            |
-| `--json`            | Output raw JSON response                             |
+| `--json`          | Output raw JSON response                             |
 
 **Example:**
 
@@ -376,13 +403,13 @@ elevasis-sdk executions:delete <resourceId> [--force]
 
 **Flags:**
 
-| Flag                           | Description                                                  |
-| ------------------------------ | ------------------------------------------------------------ |
-| `--prod`                       | Target production (overrides `NODE_ENV=development`)         |
+| Flag                         | Description                                                  |
+| ---------------------------- | ------------------------------------------------------------ |
+| `--prod`                     | Target production (overrides `NODE_ENV=development`)         |
 | `--api-url <url>`            | Override the API base URL                                    |
 | `--resource-status <status>` | Only delete runs from this deployment lane (`dev` | `prod`) |
-| `--force`                      | Skip the typed confirmation prompt                           |
-| `--json`                       | Output raw JSON response                                     |
+| `--force`                    | Skip the typed confirmation prompt                           |
+| `--json`                     | Output raw JSON response                                     |
 
 **Example:**
 
@@ -406,24 +433,31 @@ elevasis-sdk deployments
 
 **Behavior:**
 
-- Shows deployment history with status, timestamp, and resource count
-- Active deployment is marked; previous deployments show as `stopped`
+- Shows deployment history with status, SDK version, and creation timestamp
+- Status is one of `deploying`, `active`, `failed`, `rolled_back`, or `stopped`
 
 **Flags:**
 
-| Flag                | Description               |
-| ------------------- | ------------------------- |
-| `--json`            | Output raw JSON           |
-| `--api-url <url>` | Override the API base URL |
+| Flag              | Description                                          |
+| ----------------- | ---------------------------------------------------- |
+| `--prod`          | Target production (overrides `NODE_ENV=development`) |
+| `--json`          | Output raw JSON                                      |
+| `--api-url <url>` | Override the API base URL                            |
 
 **Example output:**
 
 ```
 $ elevasis-sdk deployments
 
-  deploy_abc123   active    2026-02-25 14:00:00   4 resources
-  deploy_abc122   stopped   2026-02-24 09:30:00   3 resources
-  deploy_abc121   stopped   2026-02-23 11:15:00   3 resources
+1. [ACTIVE] deploy_abc123
+   SDK Version: 1.45.0
+   Created: 2/25/2026, 2:00:00 PM
+
+2. [STOPPED] deploy_abc122
+   SDK Version: 1.44.2
+   Created: 2/24/2026, 9:30:00 AM
+
+2 deployment(s)
 ```
 
 ---
@@ -446,9 +480,9 @@ elevasis-sdk describe <resource>
 
 **Flags:**
 
-| Flag                | Description               |
-| ------------------- | ------------------------- |
-| `--json`            | Output raw JSON response  |
+| Flag              | Description               |
+| ----------------- | ------------------------- |
+| `--json`          | Output raw JSON response  |
 | `--api-url <url>` | Override the API base URL |
 
 **Example:**
@@ -495,21 +529,24 @@ elevasis-sdk creds delete <name> [--force]
 **Subcommands:**
 
 - `list` -- display all credentials (metadata only, no secret values)
-- `create` -- create a new credential; `--name` and `--type` are required; `--value` is an optional JSON string for the initial value
+- `create` -- create a new credential; `--name`, `--type`, and `--value` are all required
 - `update <name>` -- replace the value of an existing credential; `--value` (JSON) is required
 - `rename <name>` -- rename a credential; `--to <newName>` is required
 - `delete <name>` -- delete a credential; pass `--force` to skip the confirmation prompt
 
 **Flags:**
 
-| Flag                | Description                                        |
-| ------------------- | -------------------------------------------------- |
-| `--name <name>`   | Credential name (create: required)                 |
-| `--type <type>`   | Credential type, e.g. `api-key` (create: required) |
-| `--value <json>`  | Credential value as a JSON string                  |
-| `--to <newName>`  | New name (rename: required)                        |
-| `--force`           | Skip confirmation prompt (delete)                  |
-| `--api-url <url>` | Override the API base URL                          |
+| Flag              | Description                                                                     |
+| ----------------- | ------------------------------------------------------------------------------- |
+| `--name <name>`   | Credential name: lowercase letters, digits, and hyphens only (create: required) |
+| `--type <type>`   | Credential type: `api-key` or `webhook-secret` (create: required)               |
+| `--value <json>`  | Credential value as a JSON string (create and update: required)                 |
+| `--to <newName>`  | New name (rename: required)                                                     |
+| `--force`         | Skip confirmation prompt (delete)                                               |
+| `--prod`          | Target production (overrides `NODE_ENV=development`)                            |
+| `--api-url <url>` | Override the API base URL                                                       |
+
+OAuth credentials cannot be created through the CLI -- they require the Command Center's browser OAuth flow. See [Command Center](deployment/command-center.mdx#credentials).
 
 **Examples:**
 
@@ -540,24 +577,24 @@ elevasis-sdk rename <old-id> --to <new-id> [--execute] [--prod]
 - Dry-run by default -- shows all affected rows per table without modifying any data
 - Pass `--execute` to perform the rename
 - Org-scoped: only updates rows belonging to your organization
-- Updates resource references across 6 tables:
+- Refuses to run if the new resource ID already has execution history in your organization, to prevent a data collision
+- Updates resource references across 5 tables:
 
-| Table                | Column(s) updated |
-| -------------------- | ----------------- |
-| `executions`         | `resource_id`     |
-| `sessions`           | `resource_id`     |
-| `workflow_configs`   | `resource_id`     |
-| `workflow_schedules` | `resource_id`     |
-| `execution_events`   | `resource_id`     |
-| `session_events`     | `resource_id`     |
+| Table               | Column(s) updated                          |
+| ------------------- | ------------------------------------------ |
+| `execution_logs`    | `resource_id`                              |
+| `execution_metrics` | `resource_id`                              |
+| `sessions`          | `resource_id`                              |
+| `command_queue`     | `origin_resource_id`                       |
+| `task_schedules`    | `origin_resource_id`, `target_resource_id` |
 
 **Flags:**
 
-| Flag                | Description                             |
-| ------------------- | --------------------------------------- |
+| Flag              | Description                             |
+| ----------------- | --------------------------------------- |
 | `--to <new-id>`   | Required. The new resource ID           |
-| `--execute`         | Perform the rename (default is dry-run) |
-| `--prod`            | Target the production environment       |
+| `--execute`       | Perform the rename (default is dry-run) |
+| `--prod`          | Target the production environment       |
 | `--api-url <url>` | Override the API base URL               |
 
 **Example (dry-run):**
@@ -570,14 +607,13 @@ elevasis-sdk rename ist-upload-workflow --to ist-upload-contacts-workflow
   Dry run — no changes made.
 
   Rows that would be updated:
-    executions          6
-    sessions            0
-    workflow_configs    0
-    workflow_schedules  0
-    execution_events    0
-    session_events      0
+    execution_logs       6
+    execution_metrics    6
+    sessions             0
+    command_queue        0
+    task_schedules       0
 
-  Total: 6 rows
+  Total: 12 rows
 
   Re-run with --execute to apply changes.
 ```
@@ -608,11 +644,12 @@ elevasis-sdk cli [domain] [--format markdown|json]
 - When `domain` is omitted, all domains are listed
 - `--format json` returns a structured array suitable for programmatic use; `--format markdown` (default) renders a human-readable table
 - The runtime catalog is always up to date with what is actually registered -- it does not parse TypeScript source
+- This is the only catalog. `elevasis-sdk --help` no longer carries a hand-maintained `Commands:` list in `program.description()`; it prints a short pointer to `elevasis-sdk cli` plus Commander's own list of registered commands, so there is nothing left to drift
 
 **Flags:**
 
-| Flag                  | Description                                                 |
-| --------------------- | ----------------------------------------------------------- |
+| Flag                | Description                                                 |
+| ------------------- | ----------------------------------------------------------- |
 | `--domain <domain>` | Filter output to one domain (alternative to positional arg) |
 | `--format <format>` | Output format: `markdown` (default) or `json`               |
 
@@ -659,12 +696,15 @@ elevasis-sdk doctor [--verbose] [--prod]
 
 **Behavior:**
 
-Runs four sequential checks and reports `[OK]` / `[FAIL]` / `[WARN]` for each. Exits with code 1 if any check fails. Later checks are skipped when a prerequisite fails.
+Runs five sequential checks and reports `[OK]` / `[FAIL]` / `[WARN]` for each. Exits with code 1 if any check fails. Later checks are skipped when a prerequisite fails.
 
 1. Project root resolved -- locates the `.elevasis` marker file from the current working directory
 2. `.env` found at project root
 3. `ELEVASIS_PLATFORM_KEY` present and non-empty
 4. API reachable and key valid -- calls `GET /api/external/health`
+5. Systems roster -- every platform-cataloged System Interface, checked against the deployed readiness snapshot. Reuses the key and connectivity Check 4 already proved. A System the project has not adopted renders `[WARN]`, never `[FAIL]` -- partial adoption is the designed opt-out. `[FAIL]` is reserved for adopted-but-broken Systems: a stale deployed snapshot, an unsatisfied `readinessContract`, or a malformed declaration.
+
+The roster is built from the platform catalog, not from your own declarations, so a System you have **not** adopted still gets a row. A System you declared locally that is missing from the deployed snapshot is treated as drift and renders `[FAIL]`, not `[WARN]`. If the API cannot be reached, the roster renders a single `[WARN]` line and leaves Checks 1-4 with their own results. `--verbose` prints each row's issue codes and messages.
 
 **Flags:**
 
@@ -683,23 +723,31 @@ Running Elevasis SDK doctor checks...
 [OK]   API key: Set (length: 56)
 [OK]   API: Reachable. Workspace: Acme Corp (ws_abc123)
 [WARN] SDK compat: server minSdkVersion is 1.25.0; check is advisory in v1.
+[OK]   Systems: sales.lead-gen/api: ready
+[OK]   Systems: sales.crm/api: ready
+[OK]   Systems: sales.lead-gen/crm-handoff: ready
+[WARN] Systems: content/api: not adopted
 
 All checks passed. Your Elevasis project is correctly configured.
 ```
 
+A `[WARN]` roster row never changes the exit code. `doctor` still exits `0` with an unadopted System in the list.
+
 **Implementation:** `packages/sdk/src/cli/commands/doctor.ts`
 
+**Related:** [Common Errors -- System Readiness Errors](troubleshooting.mdx#system-readiness-errors-503) for what a `503` refusal from one of these Systems looks like at the terminal and how to clear it.
+
 ---
 
 ## Global Flags
 
 These flags are accepted by all commands:
 
-| Flag                | Description                                                                                         |
-| ------------------- | --------------------------------------------------------------------------------------------------- |
-| `--api-url <url>` | Override the API base URL. Priority: flag > `ELEVASIS_API_URL` env var > `NODE_ENV`-based default |
-| `--json`            | Output raw JSON (available on most commands)                                                        |
-| `--prod`            | Target production, overriding `NODE_ENV=development`                                                |
+| Flag              | Description                                                                                                                      |
+| ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `--api-url <url>` | Override the API base URL. Priority: `--api-url` flag > `--prod` flag > `ELEVASIS_API_URL` env var > `NODE_ENV`-based default |
+| `--json`          | Output raw JSON (available on most commands)                                                                                     |
+| `--prod`          | Target production, overriding `NODE_ENV=development`                                                                             |
 
 **API base URL resolution:**
 
@@ -710,4 +758,4 @@ These flags are accepted by all commands:
 
 ---
 
-**Last Updated:** 2026-08-12
+**Last Updated:** 2026-08-17

package/reference/sdk/define-builders.mdx

@@ -23,7 +23,7 @@ export function defineWorkflow<TWorkflow extends WorkflowDefinition>(workflow: T
 
 What it buys you is narrower inference. Annotate a literal `const echo: WorkflowDefinition = { ... }` and TypeScript widens every field to the interface's declared type -- `config.resourceId` becomes `string`, not `'echo'`. Pass the same object to `defineWorkflow({ ... })` with no annotation and `TWorkflow` is inferred from the literal you wrote, so `defineWorkflow(...).config.resourceId` keeps the literal type `'echo'`. That distinction only matters if something downstream reads the value back and wants the narrower type -- a test asserting on `resourceId`, a lookup table keyed by it, a second resource that imports the first and needs its literal id. A workflow file that is only ever consumed by the deploy pipeline, which just needs it to satisfy `WorkflowDefinition`, gets nothing extra from the wrapper.
 
-That is a real, but narrow, upside -- and it is honestly reflected in what ships. The scaffolded template's own workflow files (`echo.ts`, `email-notification.ts`) use the plain annotated-literal form, not `defineWorkflow`. The builder is real, exported, and demonstrated in the SDK's own test fixtures with exactly the calling convention above -- it is simply not the house style the template ships with. Use the annotated literal by default, matching what a scaffolded project already contains; reach for `defineWorkflow` / `defineStep` / `defineContract` specifically when you want the object's literal types preserved past its own definition.
+That is a real, but narrow, upside -- and it is honestly reflected in what ships. The scaffolded template's own workflow files (`example/echo.ts`, `email-notification/index.ts`) use the plain annotated-literal form, not `defineWorkflow`. The builder is real, exported, and demonstrated in the SDK's own test fixtures with exactly the calling convention above -- it is simply not the house style the template ships with. Use the annotated literal by default, matching what a scaffolded project already contains; reach for `defineWorkflow` / `defineStep` / `defineContract` specifically when you want the object's literal types preserved past its own definition.
 
 `defineWorkflowConfig` is a different kind of helper in this same group -- it derives `config` fields from an Organization Model resource descriptor instead of preserving literal types. It has its own page: see [The Deployment Spec Pattern](project-deployment-spec.mdx#defineworkflowconfig-deriving-config-from-one-om-descriptor).
 

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

@@ -105,8 +105,8 @@ Keep relationships in sync with your handler code. When you add an `execution.tr
 **Validation error examples:**
 
 ```
-ERROR  Relationship target 'send-proposal' not found in organization resources
-ERROR  Duplicate resource ID 'score-lead' in deployment
+ERROR  [acme-corp] Resource 'score-lead' triggers non-existent workflow: send-proposal
+ERROR  Duplicate resource ID 'score-lead' in deployment. Each resource must have a unique ID.
 ```
 
 ### Graph Serialization

package/reference/sdk/deployment/index.mdx

@@ -82,13 +82,14 @@ Each deploy creates a new deployment record. The previous active deployment is a
 
 The CLI validates your resources before bundling. Validation uses the same `ResourceRegistry` as the platform, so errors caught locally are the same errors that would be caught at deploy time.
 
-**Validation checks:**
+**Validation checks that abort the deploy:**
 
 - Duplicate `resourceId` within your organization
 - Invalid model configuration (temperature and token bounds out of range)
 - `ExecutionInterface` form fields not matching `inputSchema`
-- Broken workflow step chains (`next` referencing a step that does not exist)
 - Relationship declarations referencing resources that do not exist
+- Structural failures in your `organizationModel`
+- A System with API-backed resources but no `apiInterface` declaration
 
 **Validation failure output:**
 
@@ -100,6 +101,18 @@ The CLI validates your resources before bundling. Validation uses the same `Reso
   Deploy aborted.
 ```
 
+Every issue is reported in one run. Governance and System Interface readiness failures no longer stop at the first problem, so thirty issues cost one deploy round trip rather than thirty.
+
+**Checks that warn without aborting:**
+
+Workflow-graph problems -- a `next` target that does not exist, an `entryPoint` that names no step, a cycle, or a step unreachable from the entry point -- are reported as warnings so an existing project carrying a latent invalid graph is not blocked on its next deploy. **They still throw at execution**, when the workflow is constructed. Treat a graph warning as a defect with a deadline, not as advisory.
+
+The platform runs its own checks on the server after upload and reports these as warnings too: the `apiInterface` conformance check, agent grammar and token-floor validation, and a cross-check of every declared `IntegrationDefinition.credentialName` against the credentials your organization actually holds. A missing credential is a warning at deploy and a `credentials_missing` failure at execution, so create it before the resource runs. Only credential names are checked; values never leave the command center.
+
+**Downgrading checks temporarily:**
+
+`ELEVASIS_RESOURCE_VALIDATOR=warn-only` downgrades resource governance, contract-ref resolution, System Interface readiness, and the agent grammar and cheap-assertion checks to warnings. Every downgraded check still runs and still prints its issue; it never bypasses the structural schema parse or the conformance gate.
+
 Run `elevasis-sdk check` at any time to validate without deploying.
 
 ---
@@ -121,13 +134,16 @@ The `ElevasConfig` type is exported from `@elevasis/sdk`. You can leave the conf
 
 ## Environment Variables
 
-| Variable                | Required | Description                                                                 |
-| ----------------------- | -------- | --------------------------------------------------------------------------- |
-| `ELEVASIS_PLATFORM_KEY` | Yes      | Your `sk_...` API key. Used for authentication and organization resolution. |
-| `ELEVASIS_API_URL`      | No       | Override the API base URL. Useful for pointing at a staging environment.    |
+| Variable                    | Required | Description                                                                         |
+| --------------------------- | -------- | ----------------------------------------------------------------------------------- |
+| `ELEVASIS_PLATFORM_KEY`     | Yes      | Your `sk_...` API key. Used for authentication and organization resolution.         |
+| `ELEVASIS_API_URL`          | No       | Override the API base URL. Useful for pointing at a staging environment.            |
+| `ELEVASIS_PLATFORM_KEY_DEV` | No       | Key used instead when the request targets a local API. Falls back to the key above. |
 
 The CLI also accepts a `--api-url` flag on every command, which takes priority over `ELEVASIS_API_URL`.
 
+**Which key a request uses is derived from the URL it is sent to**, not from `--prod` or `NODE_ENV` read separately. Both the authentication step and the bundle upload go through the same resolver, so pointing `--api-url` at production while `NODE_ENV=development` is set can no longer authenticate with one key and upload with the other.
+
 **API URL resolution order:**
 
 1. `--api-url` flag (highest priority)
@@ -288,4 +304,5 @@ Dashboard appears before Business in the primary sidebar. Business is a navigati
 
 - [Command Center](command-center.mdx) - Resource graph, relationships, node types, and post-deployment UI reference
 - [Execution Reference](execution-reference.mdx) - REST endpoints for executing resources, managing deployments, and React UI components for custom Run dialogs
-- [Platform Adapters](../platform-tools/adapters-platform.mdx) - `approval.create()` and all platform service adapters
+- [Platform Adapters](../platform-tools/adapters-platform.mdx) - `approval.create()` and the full platform service adapter catalog
+- [Common Errors](../troubleshooting.mdx#deploy-errors-elevasis-sdk-deploy) - Deploy failure catalog, warning meanings, and System readiness refusals

package/reference/sdk/exports.mdx

@@ -8,7 +8,7 @@ description: "Auto-generated catalog of all published @elevasis/sdk subpath expo
 
 | Import | Title | Group | Description |
 | --- | --- | --- | --- |
-| `@elevasis/sdk` | SDK | Getting Started |  |
-| `@elevasis/sdk/worker` | Worker Runtime | Runtime |  |
-| `@elevasis/sdk/test-utils` | Test Utils | Testing |  |
-| `@elevasis/sdk/node` | Node Build Tooling | Tooling |  |
+| `@elevasis/sdk` | SDK | Getting Started | Default entry: defineWorkflow, defineStep, defineContract, contract-ref resolution, shared types, and workflow utilities. |
+| `@elevasis/sdk/worker` | Worker Runtime | Runtime | worker_threads runtime plus the typed platform and integration adapters a step handler calls at execution time. |
+| `@elevasis/sdk/test-utils` | Test Utils | Testing | Workflow test harness, resource registry helpers, and mock adapters for unit-testing definitions without the platform. |
+| `@elevasis/sdk/node` | Node Build Tooling | Tooling | Node-only build-time codegen for knowledge nodes and bodies. Requires fs/path/process -- not browser-safe. |

package/reference/sdk/framework/agent.mdx

@@ -36,6 +36,7 @@ The template ships these skills, all committed to version control:
 | Skill             | Purpose                                                                                          |
 | ----------------- | ------------------------------------------------------------------------------------------------ |
 | `/client`         | Client portfolio management -- list, resolve, inspect, and maintain client records               |
+| `/content`        | Content pipeline operations -- list items, inspect, board view, review queue, distributions      |
 | `/deploy`         | Test, build, fix issues, then commit and push                                                    |
 | `/dsp`            | Dispatch subagents in parallel for implementation tasks                                          |
 | `/elevasis`       | SDK operations -- check, deploy, execute, inspect, and debug resources                           |
@@ -77,11 +78,11 @@ The gate is **outgoing commits**, checked with `git rev-list --count @{u}..HEAD`
 
 ## The Ambient Vibe Layer
 
-External projects run an always-on natural-language intent classifier -- there is no `/vibe` command and no activation phrase. Every message is silently classified into one of seven intents (Capture, Query, Describe, Transition, Navigate, Codify, Toggle) before the agent responds. Codify and Toggle detect intent and delegate immediately to `/om`; the classifier never runs the organization-model ceremony itself. The full classifier definition and fixture tables ship with the SDK at `operations/node_modules/@elevasis/sdk/reference/rules/vibe.md`. Vibe is explicitly off inside the monorepo, which uses the task-class routing in `agent-start-here.md` instead.
+External projects run an always-on natural-language intent classifier -- there is no `/vibe` command and no activation phrase. Every message is silently classified into one of eight intents (Capture, Query, Describe, Transition, Navigate, Codify, Toggle, Operate) before the agent responds. Codify and Toggle detect intent and delegate immediately to `/om`; Operate delegates to `/elevasis` (`elevasis-sdk describe` then a confirmed `exec`); the classifier never runs the organization-model ceremony or executes a deployed resource itself. The full classifier definition and fixture tables ship with the SDK at `operations/node_modules/@elevasis/sdk/reference/rules/vibe.md` and the per-intent detail at `operations/node_modules/@elevasis/sdk/reference/rules/vibe-intents.md`. Vibe is explicitly off inside the monorepo, which uses the task-class routing in `agent-start-here.md` instead.
 
 ## The Rules Layer
 
-`.claude/rules/` in the git-tracked template holds short pointer files with `paths:` frontmatter that Claude Code auto-loads for matching files. The authoritative rule bodies ship with the installed `@elevasis/sdk` package at `operations/node_modules/@elevasis/sdk/reference/rules/` and update whenever the SDK dependency is bumped. Rules include `agent-start-here.md` (always-loaded), `vibe.md` (always-loaded), `organization-os.md`, `deployment.md`, `error-handling.md`, `execution.md`, `frontend.md`, `observability.md`, `operations.md`, `organization-model.md`, `platform.md`, `shared-types.md`, `task-tracking.md`, `ui.md`, and `active-change-index.md` (which flags areas under active platform change).
+`.claude/rules/` in the git-tracked template holds short pointer files with `paths:` frontmatter that Claude Code auto-loads for matching files. The authoritative rule bodies ship with the installed `@elevasis/sdk` package at `operations/node_modules/@elevasis/sdk/reference/rules/` and update whenever the SDK dependency is bumped. The bundle carries 19 rules: `agent-start-here.md` (always-loaded), `vibe.md` (always-loaded), `vibe-intents.md`, `agent-runtime.md`, `content.md`, `organization-os.md`, `deployment.md`, `error-handling.md`, `execution.md`, `frontend.md`, `observability.md`, `operations.md`, `organization-model.md`, `package-taxonomy.md`, `platform.md`, `shared-types.md`, `task-tracking.md`, `ui.md`, and `active-change-index.md` (which flags areas under active platform change). The template also ships a small number of project-authored, System-specific rules directly under `.claude/rules/` -- for example `crm.md` and `lead-gen.md` -- that are not part of the bundled set.
 
 ## Template Version Tracking
 
@@ -89,4 +90,4 @@ The scaffold's version marker is `templateVersion` in the project-root `.elevasi
 
 ---
 
-**Last Updated:** 2026-08-06
+**Last Updated:** 2026-08-17

package/reference/sdk/framework/index.mdx

@@ -83,7 +83,7 @@ See [Tutorial System](tutorial-system.mdx) for the full lesson breakdown, track
 
 ## Documentation
 
-- [Project Structure](project-structure.mdx) - Directory-by-directory walkthrough of the scaffolded project
+- [Project Structure](project-structure.mdx) - Directory-by-directory walkthrough of the scaffolded project's structure and layout
 - [Agent System](agent.mdx) - Skill inventory, rules layer, ambient vibe classifier, and session bootstrap
 - [Tutorial System](tutorial-system.mdx) - Two-track onboarding (8 vibe-coder + 19 technical lessons), track persistence, and progress tracking