@elevasis/sdk 1.28.0 → 1.29.0

package/reference/{cli.mdx → sdk/cli.mdx}

@@ -405,36 +405,49 @@ elevasis-sdk describe onboard-client
 
 ## elevasis-sdk creds
 
-Manage credentials for your project.
+Manage credentials for your organization. Credentials store API keys and secrets server-side so they never appear in your worker code.
 
 **Synopsis:**
 
 ```
 elevasis-sdk creds list
-elevasis-sdk creds set <key> <value>
-elevasis-sdk creds remove <key>
+elevasis-sdk creds create --name <name> --type <type> [--value <json>]
+elevasis-sdk creds update <name> --value <json>
+elevasis-sdk creds rename <name> --to <newName>
+elevasis-sdk creds delete <name> [--force]
 ```
 
-**Behavior:**
+**Subcommands:**
 
-- `list` -- display all credentials configured for the project
-- `set` -- add or update a credential
-- `remove` -- delete a credential
+- `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
+- `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               |
-| ------------------- | ------------------------- |
-| `--api-url <url>` | Override the API base URL |
+| 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                          |
 
 **Examples:**
 
 ```bash
 elevasis-sdk creds list
-elevasis-sdk creds set OPENAI_API_KEY sk-proj-***
-elevasis-sdk creds remove OPENAI_API_KEY
+elevasis-sdk creds create --name openai-key --type api-key --value '{"key":"sk-proj-***"}'
+elevasis-sdk creds update openai-key --value '{"key":"sk-proj-new"}'
+elevasis-sdk creds rename openai-key --to openai-prod-key
+elevasis-sdk creds delete openai-prod-key --force
 ```
 
+**Implementation:** `packages/sdk/src/cli/commands/creds/creds.ts`
+
 ---
 
 ## elevasis-sdk rename
@@ -558,6 +571,49 @@ pnpm -C external/<project>/operations exec elevasis-sdk cli
 
 ---
 
+## elevasis-sdk doctor
+
+Check that your Elevasis project is correctly configured.
+
+**Synopsis:**
+
+```
+elevasis-sdk doctor [--verbose]
+```
+
+**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.
+
+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`
+
+**Flags:**
+
+| Flag        | Description                                                         |
+| ----------- | ------------------------------------------------------------------- |
+| `--verbose` | Print full paths, response bodies, and error details for each check |
+
+**Example output (all passing):**
+
+```
+Running Elevasis SDK doctor checks...
+
+[OK]   Project root: /path/to/my-project
+[OK]   .env: Found at /path/to/my-project/.env
+[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.
+
+All checks passed. Your Elevasis project is correctly configured.
+```
+
+**Implementation:** `packages/sdk/src/cli/commands/doctor.ts`
+
+---
+
 ## Global Flags
 
 These flags are accepted by all commands:

package/reference/sdk/exports.mdx

@@ -0,0 +1,14 @@
+---
+title: "@elevasis/sdk Export Catalog"
+description: "Auto-generated catalog of all published @elevasis/sdk subpath exports, derived from packages/sdk/reference-manifest.ts."
+---
+
+{/* @generated by .claude/_gen/sync-sdk-catalog.ts — DO NOT EDIT */}
+{/* Regenerate: pnpm gen:sdk-catalog */}
+
+| Import | Title | Group | Description |
+| --- | --- | --- | --- |
+| `@elevasis/sdk` | SDK | Getting Started | Root SDK types, config, runtime errors, and registry surface. |
+| `@elevasis/sdk/worker` | Worker Runtime | Runtime | Worker runtime entrypoint, adapters, and platform execution surface. |
+| `@elevasis/sdk/test-utils` | Test Utils | Testing | Workflow runner, registry assertion, and typed adapter mocks for SDK consumers. |
+| `@elevasis/sdk/node` | Node Build Tooling | Tooling | Node-only build helpers: knowledge codegen and other fs/path/process utilities. Not browser-safe. |

package/reference/sdk/index.mdx

@@ -0,0 +1,93 @@
+---
+title: Elevasis SDK
+description: Build and deploy workflows, agents, and resources with the Elevasis SDK
+---
+
+`@elevasis/sdk` lets you build workflows, agents, and resources in TypeScript and deploy them to the Elevasis platform with a single command. The developer experience is Vercel-style: write TypeScript, validate locally, deploy -- the platform handles execution, tool access, and observability. You never manage infrastructure. Zod 4.1 is the only peer dependency.
+
+Workflows are step-based automations with typed inputs and outputs. Agents are autonomous AI resources with access to platform tools. Both are defined in TypeScript, exported from a single entry point, and deployed with `elevasis-sdk deploy`. Resources appear in AI Studio immediately after a successful deploy.
+
+The SDK ships with a full CLI (`elevasis-sdk`) for validation, deployment, execution, inspection, and project-management operations. Platform tools expose 25 adapters (13 integration + 12 platform) across integration adapters and platform services -- Gmail, Stripe, Google Sheets, Attio, and more -- with credentials managed server-side so API keys never cross the execution boundary.
+
+## Quick Start
+
+```bash
+pnpm dlx @elevasis/sdk init my-project
+cd my-project
+pnpm install
+elevasis-sdk deploy
+```
+
+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.
+
+## What You Can Build
+
+- **Workflows** -- Step-based automation with typed inputs and outputs. Steps can be linear, conditional, or branching. Each step is a plain async function. See [Resources](resources/index.mdx) for the complete definition API.
+- **Agents** -- Autonomous AI resources with access to platform tools. Agents run in the worker runtime with full LLM access and platform tool support. Use `--async` when executing agents to avoid HTTP timeout limits on long-running runs.
+- **Feature-driven apps** -- The published `@elevasis/ui` surface includes manifest-backed shared features for Lead Gen, CRM, Projects, Operations, Monitoring, Settings, and SEO, plus dashboard-oriented compatibility components for host-owned shells. See [Provided Features](deployment/index.mdx#provided-features).
+
+## Platform Tools
+
+The platform exposes 25 adapters (13 integration + 12 platform) across integration adapters and platform services -- Gmail, Stripe, Google Sheets, Attio, and more. Import typed adapters from `@elevasis/sdk/worker` inside any workflow step or agent. Credentials are managed server-side; API keys never cross the execution boundary.
+
+See [Platform Tools](platform-tools/index.mdx) for the full catalog, adapter reference, and credential setup.
+
+## 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-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
+
+### Getting Started
+
+- [Getting Started](getting-started.mdx) - Installation, authentication, first workflow, and project structure
+
+### Core Concepts
+
+- [Resources](resources/index.mdx) - Workflow and agent definition patterns, Zod schemas, step types, and routing
+- [Platform Tools](platform-tools/index.mdx) - Full catalog of 25 adapters (13 integration + 12 platform), integration adapters, and credential management
+- [Credential Security](platform-tools/index.mdx#credential-security) - Three-layer credential model, HTTP tool patterns, and credential management
+
+### Reference
+
+- [Concepts](concepts.mdx) - Plain-English concept explanations, glossary, Zod guide, execution model, and common errors
+- [Templates](templates/index.mdx) - 7 workflow templates: web-scraper, data-enrichment, email-sender, lead-scorer, and more
+- [CLI Reference](cli.mdx) - Core commands: check, deploy, exec, resources, executions, deployments, describe, creds, and rename
+- [CLI Management Commands](cli-management.mdx) - Management families: project:\*, note:\*, acquisition:\*, client:\*, agent:\*, session:\*, queue:\*, schedule:\*, om:\*, and ui:\*
+- [Deployment](deployment/index.mdx) - Deploy pipeline, versioning, bundle upload, and registry registration
+- [Runtime](runtime.mdx) - Worker execution model, concurrency, timeouts, cancellation, resource limits, and v1 limitations
+
+### Typed Adapters
+
+- [Integration Adapters](platform-tools/adapters-integration.mdx) - Integration adapter catalog for Attio, Stripe, Google Sheets, Resend, and more
+- [Platform Adapters](platform-tools/adapters-platform.mdx) - All 12 platform service adapters: scheduler, storage, llm, pdf, approval, and more
+
+### Framework
+
+- [Development Framework](framework/index.mdx) - How Claude Code helps you build: project structure, agent integration, memory, and documentation
+- [Project Structure](framework/project-structure.mdx) - Scaffolded file layout, domain barrels, src/index.ts entry point, and config files
+- [Agent Configuration](framework/agent.mdx) - Agent capabilities, tool access, model config, and Claude Code integration patterns
+- [Memory](framework/memory.mdx) - Agent memory system, session state, developer profiles, and workspace conventions
+- [Interaction Guidance](framework/interaction-guidance.mdx) - Skill dimension adaptation rules for platform navigation, API integration, and automation concepts
+- [Tutorial System](framework/tutorial-system.mdx) - 21-item tutorial menu, skill-adaptive lesson variants, progress tracking, and module contents
+- [Resource Documentation](framework/resource-documentation.mdx) - Docs directory structure, frontmatter schema, size limits, deploy behavior, and /docs command reference
+
+### Resources Subpages
+
+- [SDK Types](resources/types.mdx) - Complete type reference for `@elevasis/sdk` exports, config fields, and step handler context
+- [Common Patterns](resources/patterns.mdx) - Sequential steps, conditional branching, error handling, and resource status patterns
+
+### Deployment Subpages
+
+- [Command Center](deployment/command-center.mdx) - Resource graph, relationships, node types, and post-deployment UI reference
+- [Execution Reference](deployment/execution-reference.mdx) - REST endpoints for executing resources, managing deployments, and React UI components for custom Run dialogs
+
+### More
+
+- [Troubleshooting](troubleshooting.mdx) - Static error catalog for CLI, deployment, schema, and runtime failures
+- [Roadmap](roadmap.mdx) - Planned features including error taxonomy, retry semantics, circuit breaker, and metrics
+
+---
+
+**Last Updated:** 2026-05-19

package/reference/sdk/platform-tools/adapters-integration.mdx

@@ -0,0 +1,25 @@
+---
+title: "Integration Adapters"
+description: "Auto-generated table of all 13 integration (credential-bound) adapters exported from @elevasis/sdk/worker, derived from static analysis of the adapter source files."
+---
+
+{/* @generated by .claude/_gen/sync-sdk-adapters.ts — DO NOT EDIT */}
+{/* Regenerate: pnpm gen:sdk-adapters */}
+
+Integration adapters use a factory pattern. Call `create*Adapter(credential)` with a credential name configured in the Command Center to get a typed adapter object.
+
+| Adapter | Factory | Methods | Description |
+| --- | --- | --- | --- |
+| Attio | `createAttioAdapter(credential)` | `createRecord`, `updateRecord`, `listRecords`, `getRecord`, `deleteRecord`, `listObjects`, `listAttributes`, `createAttribute`, `updateAttribute`, `createNote`, `listNotes`, `deleteNote` | Attio CRM — create, read, update, delete records, objects, attributes, and notes. |
+| Apify | `createApifyAdapter(credential)` | `runActor`, `getDatasetItems`, `startActor` | Apify — run actors and retrieve dataset items from web scraping runs. |
+| ClickUp | `createClickUpAdapter(credential)` | `verify`, `createTask` | ClickUp — verify connection and create tasks in ClickUp lists. |
+| Dropbox | `createDropboxAdapter(credential)` | `uploadFile`, `createFolder` | Dropbox — upload files and create folders. |
+| Gmail | `createGmailAdapter(credential)` | `sendEmail` | Gmail — send emails via a bound Gmail credential. |
+| GoogleSheets | `createGoogleSheetsAdapter(credential)` | `readSheet`, `writeSheet`, `appendRows`, `clearRange`, `getSpreadsheetMetadata`, `batchUpdate`, `getHeaders`, `getLastRow`, `getRowByValue`, `updateRowByValue`, `upsertRow`, `filterRows`, `deleteRowByValue` | Google Sheets — read, write, append, filter, and manage spreadsheet data. |
+| Instantly | `createInstantlyAdapter(credential)` | `sendReply`, `removeFromSubsequence`, `getEmails`, `updateInterestStatus`, `addToCampaign`, `listCampaigns`, `getCampaign`, `updateCampaign`, `pauseCampaign`, `activateCampaign`, `getCampaignAnalytics`, `getStepAnalytics`, `bulkAddLeads`, `getAccountHealth`, `createInboxTest`, `createCampaign`, `getDailyCampaignAnalytics`, `listLeads`, `bulkDeleteLeads`, `deleteCampaign`, `patchLead` | Instantly — manage email outreach campaigns, leads, analytics, and inbox health. |
+| MillionVerifier | `createMillionVerifierAdapter(credential)` | `verifyEmail`, `checkCredits` | MillionVerifier — verify email deliverability and check account credits. |
+| Anymailfinder | `createAnymailfinderAdapter(credential)` | `findCompanyEmail`, `findPersonEmail`, `findDecisionMakerEmail`, `verifyEmail` | Anymailfinder — find and verify company and person email addresses. |
+| Tomba | `createTombaAdapter(credential)` | `emailFinder`, `domainSearch`, `emailVerifier` | Tomba — email finder, domain search, and email verifier for prospecting. |
+| Resend | `createResendAdapter(credential)` | `sendEmail`, `getEmail` | Resend — send and retrieve transactional emails. |
+| SignatureApi | `createSignatureApiAdapter(credential)` | `createEnvelope`, `voidEnvelope`, `downloadDocument`, `getEnvelope` | SignatureAPI — create, void, download, and retrieve eSignature envelopes. |
+| Stripe | `createStripeAdapter(credential)` | `createPaymentLink`, `getPaymentLink`, `updatePaymentLink`, `listPaymentLinks`, `createAutoPaymentLink`, `createCheckoutSession` | Stripe — create and manage payment links and checkout sessions. |

package/reference/sdk/platform-tools/adapters-platform.mdx

@@ -0,0 +1,24 @@
+---
+title: "Platform Adapters"
+description: "Auto-generated table of all 12 platform (singleton, no credential) adapters exported from @elevasis/sdk/worker, derived from static analysis of the adapter source files."
+---
+
+{/* @generated by .claude/_gen/sync-sdk-adapters.ts — DO NOT EDIT */}
+{/* Regenerate: pnpm gen:sdk-adapters */}
+
+Platform adapters are singletons — import them directly, no credential required.
+
+| Adapter | Export | Methods | Description |
+| --- | --- | --- | --- |
+| Scheduler | `scheduler` | `createSchedule`, `updateAnchor`, `deleteSchedule`, `findByIdempotencyKey`, `deleteScheduleByIdempotencyKey`, `listSchedules`, `getSchedule`, `cancelSchedule`, `cancelSchedulesByMetadata`, `cancelScheduleByIdempotencyKey` | Scheduler — create, update, cancel, and query task schedules. |
+| Llm | `llm` | `generate` | LLM — generate structured or unstructured text via OpenAI, Anthropic, OpenRouter, or Google. |
+| Storage | `storage` | `upload`, `download`, `createSignedUrl`, `delete`, `list` | Storage — upload, download, list, delete files, and create signed URLs in org-scoped buckets. |
+| Notifications | `notifications` | `create` | Notifications — send in-platform notifications to team members. |
+| AcqDb | `acqDb` | `listLists`, `createList`, `updateList`, `deleteList`, `addContactsToList`, `addCompaniesToList`, `updateCompanyStage`, `updateContactStage`, `createCompany`, `upsertCompany`, `updateCompany`, `getCompany`, `listCompanies`, `deleteCompany`, `createContact`, `upsertContact`, `updateContact`, `getContact`, `getContactByEmail`, `listContacts`, `deleteContact`, `bulkImportContacts`, `bulkImportCompanies`, `deactivateContactsByCompany`, `upsertDeal`, `getDealByEmail`, `getDealByEnvelopeId`, `updateDealEnvelopeId`, `getDealById`, `getContactById`, `getCompanyById`, `updateDiscoveryData`, `updateProposalData`, `markProposalSent`, `markProposalReviewed`, `updateCloseLostReason`, `updateFees`, `cacheInstantlyThreadIds`, `transitionItem`, `setContactNurture`, `cancelSchedulesAndHitlByEmail`, `cancelHitlByDealId`, `clearDealFields`, `deleteDeal`, `recordDealActivity`, `setDealStateKey`, `transitionDeal`, `loadDeal`, `createDealNote`, `listDealNotes`, `createDealTask`, `listDealTasks`, `listDealTasksDue`, `completeDealTask`, `mergeEnrichmentData`, `upsertSocialPosts` | AcqDb — full acquisition database: lists, companies, contacts, deals, notes, tasks, and enrichment. |
+| Projects | `projects` | `listProjects`, `getProject`, `createProject`, `updateProject`, `deleteProject`, `listMilestones`, `createMilestone`, `updateMilestone`, `deleteMilestone`, `listTasks`, `getTask`, `createTask`, `updateTask`, `deleteTask`, `mergeTaskResumeContext`, `listNotes`, `createNote`, `updateNote`, `deleteNote` | Projects — manage delivery projects, milestones, tasks, notes, and resume context. |
+| Crm | `crm` | `getRecentActivity`, `listDeals`, `getDeal`, `getDealByEmail`, `createDealNote`, `listDealNotes`, `createDealTask`, `listDealTasks`, `listDealTasksDue`, `completeDealTask`, `recordActivity`, `deleteDeal` | CRM — read and update deals, notes, tasks, activity, and stage transitions. |
+| List | `list` | `getConfig`, `recordExecution`, `updateCompanyStage`, `updateContactStage`, `listPendingCompanyIds`, `listPendingContactIds` | List — list-scoped workflow execution tracking and stage updates. |
+| Pdf | `pdf` | `render`, `renderToBuffer` | PDF — render PDF documents from structured page definitions. |
+| Approval | `approval` | `create`, `deleteByMetadata` | Approval — create and manage HITL (human-in-the-loop) tasks. |
+| Execution | `execution` | `trigger`, `triggerAsync` | Execution — trigger other workflows or agents within the same organization. |
+| Email | `email` | `send` | Email — send platform emails (from notifications@elevasis.io) to organization members. |

package/reference/{platform-tools → sdk/platform-tools}/index.mdx

@@ -1,9 +1,9 @@
 ---
 title: Platform Tools
-description: Access 70+ tools across integration adapters and platform services from your SDK workflows -- typed adapters, credential security model, and working code examples
+description: Access 25 adapters (13 integration + 12 platform) from your SDK workflows -- typed adapters, credential security model, and working code examples
 ---
 
-Your SDK workflows have access to 70+ tools -- Gmail, Stripe, Google Sheets, PDF generation, human-in-the-loop approvals, storage, scheduling, and more. Credentials are managed server-side and never appear in your code.
+Your SDK workflows have access to 25 adapters (13 integration + 12 platform) -- Gmail, Stripe, Google Sheets, PDF generation, human-in-the-loop approvals, storage, scheduling, and more. Credentials are managed server-side and never appear in your code.
 
 **Typed adapters** are the recommended way to call tools. They provide full TypeScript autocomplete, compile-time method checking, and eliminate boilerplate. Use `platform.call()` only for tools that don't have an adapter yet.
 
@@ -39,20 +39,9 @@ Both patterns return a Promise that resolves with the tool result or rejects wit
 
 ## Integration Adapters
 
-Ten integration adapters give you access to 50+ tool methods covering third-party APIs. Pass the credential name once at adapter creation. Supabase is listed separately under [Database Access](#database-access) below.
-
-| Adapter       | Tools                         | Credential Shape         |
-| ------------- | ----------------------------- | ------------------------ |
-| Attio         | 12 (CRUD + schema + notes)    | `{ apiKey }`             |
-| Google Sheets | 13 (read/write/filter/upsert) | OAuth2 / service account |
-| Stripe        | 6 (payment links + checkout)  | `{ secretKey }`          |
-| Instantly     | 5 (email campaigns)           | `{ apiKey }`             |
-| SignatureAPI  | 4 (envelopes)                 | `{ apiKey }`             |
-| Tomba         | 3 (email discovery)           | `api-key-secret`         |
-| Gmail         | 2 (send email)                | OAuth2 / service account |
-| Resend        | 2 (send/get email)            | `{ apiKey }`             |
-| Dropbox       | 2 (upload/folder)             | `{ accessToken }`        |
-| Apify         | 1 (run actor)                 | `{ token }`              |
+The SDK ships 13 integration adapters (credential-bound factory functions) covering third-party APIs -- Attio, Apify, ClickUp, Dropbox, Gmail, Google Sheets, Instantly, MillionVerifier, Anymailfinder, Tomba, Resend, SignatureAPI, and Stripe. Pass the credential name once at adapter creation. Supabase is covered separately under [Database Access](#database-access) below.
+
+For the full per-adapter method tables, credential shapes, and code examples, see [Integration Adapters](adapters-integration.mdx) -- generated from the adapter source so it never drifts.
 
 ## Credential Security
 
@@ -131,19 +120,9 @@ Credentials are created in the command center UI: navigate to Credentials -> Add
 
 ## Platform Services
 
-Nine built-in platform services are available without a `credential` field. All have typed singleton adapters imported from `@elevasis/sdk/worker`.
+The SDK ships 12 platform service singletons available without a `credential` field -- imported directly from `@elevasis/sdk/worker`: `scheduler`, `llm`, `storage`, `notifications`, `acqDb`, `projects`, `crm`, `list`, `pdf`, `approval`, `execution`, and `email`. The platform injects context server-side, so no credential is passed.
 
-| Tool Key       | Methods                                                                                                                                                                                     | Purpose                                         |
-| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
-| `acqDb`        | 35 methods (CRUD + sync)                                                                                                                                                                    | Acquisition database -- `acqDb` adapter         |
-| `email`        | `send`                                                                                                                                                                                      | Send email to org members -- `email` adapter    |
-| `storage`      | `upload`, `download`, `createSignedUrl`, `delete`, `list`                                                                                                                                   | File storage -- `storage` adapter               |
-| `pdf`          | `render`, `renderToBuffer`                                                                                                                                                                  | PDF rendering -- `pdf` adapter                  |
-| `notification` | `create`                                                                                                                                                                                    | In-app notifications -- `notifications` adapter |
-| `approval`     | `create`, `deleteByMetadata`                                                                                                                                                                | HITL approval gates -- `approval` adapter       |
-| `scheduler`    | `createSchedule`, `updateAnchor`, `deleteSchedule`, `findByIdempotencyKey`, `deleteScheduleByIdempotencyKey`, `listSchedules`, `getSchedule`, `cancelSchedule`, `cancelSchedulesByMetadata` | Task scheduling -- `scheduler` adapter          |
-| `llm`          | `generate`                                                                                                                                                                                  | LLM inference -- `llm` adapter                  |
-| `execution`    | `trigger`                                                                                                                                                                                   | Nested child execution -- `execution` adapter   |
+For the full per-service method tables (including the `acqDb` 41-method surface), see [Platform Adapters](adapters-platform.mdx) -- generated from the adapter source.
 
 ## LLM Tool
 
@@ -207,8 +186,8 @@ const qualified = await platform.call({
 
 ## Documentation
 
-- [Integration Adapters](adapters-integration.mdx) - All 10 integration adapters with method tables and code examples
-- [Platform Adapters](adapters-platform.mdx) - All 9 platform service adapters with method tables and code examples
+- [Integration Adapters](adapters-integration.mdx) - All 13 integration adapters with method tables and code examples
+- [Platform Adapters](adapters-platform.mdx) - All 12 platform service adapters with method tables and code examples
 - [Adapter Type Safety](type-safety.mdx) - Required fields, discriminated unions, and intentionally loose adapter types
 
 ---

package/reference/{resources → sdk/resources}/patterns.mdx

@@ -11,19 +11,23 @@ This page collects the patterns you will reach for most often when writing resou
 
 The simplest pattern: a chain of steps where each step feeds its output into the next.
 
+Each `WorkflowStep` requires `id`, `name`, `description`, `handler`, `inputSchema`, `outputSchema`, and `next`. There is no `type` field on a step -- `StepType` (`LINEAR` / `CONDITIONAL`) is a label for `next.type` only, not a step property.
+
 ```typescript
 import { z } from 'zod';
-import { StepType } from '@elevasis/sdk';
 import type { WorkflowDefinition, WorkflowStep } from '@elevasis/sdk';
 
 const inputSchema = z.object({ orderId: z.string() });
 const outputSchema = z.object({ shipped: z.boolean(), trackingNumber: z.string() });
 
 type Input = z.infer<typeof inputSchema>;
-type Output = z.infer<typeof outputSchema>;
 
 const validateStep: WorkflowStep = {
-  type: StepType.LINEAR,
+  id: 'validate',
+  name: 'Validate Order',
+  description: 'Checks the order exists before shipping',
+  inputSchema: z.object({ orderId: z.string() }),
+  outputSchema: z.object({ order: z.unknown() }),
   handler: async (input: Input) => {
     const order = await getOrder(input.orderId);
     if (!order) throw new Error(`Order ${input.orderId} not found`);
@@ -33,7 +37,11 @@ const validateStep: WorkflowStep = {
 };
 
 const shipStep: WorkflowStep = {
-  type: StepType.LINEAR,
+  id: 'ship',
+  name: 'Ship Order',
+  description: 'Creates a shipment and returns the tracking number',
+  inputSchema: z.object({ order: z.unknown() }),
+  outputSchema: z.object({ shipped: z.boolean(), trackingNumber: z.string() }),
   handler: async (input) => {
     const tracking = await createShipment(input.order);
     return { shipped: true, trackingNumber: tracking.number };
@@ -51,23 +59,29 @@ const fulfillOrder: WorkflowDefinition = {
 
 **Key points:**
 
-- `next: { target: 'stepName' }` routes to the next step
+- Steps require `id`, `name`, `description`, `inputSchema`, `outputSchema`, `handler`, and `next`
+- `next.type` is `'linear'` or `'conditional'` -- this is where `StepType` values apply; the step itself has no `type` field
+- `next: { type: 'linear', target: 'stepName' }` routes to the next step
 - `next: null` marks the terminal step
 - Each step receives the full return value of the previous step as its `input`
-- The terminal step's return value must satisfy `contract.output`
+- The terminal step's return value must satisfy `contract.outputSchema`
 
 ---
 
 ## Conditional Branching
 
-Use `StepType.CONDITIONAL` when the next step depends on the output of the current step.
+Use a `next.type` of `'conditional'` when the next step depends on the output of the current step. The step itself still has no `type` field -- the routing decision lives entirely in `next`.
 
 ```typescript
-import { StepType } from '@elevasis/sdk';
+import { z } from 'zod';
 import type { WorkflowStep } from '@elevasis/sdk';
 
 const scoreStep: WorkflowStep = {
-  type: StepType.CONDITIONAL,
+  id: 'score',
+  name: 'Score Application',
+  description: 'Calculates a risk score and routes on the result',
+  inputSchema: z.object({ applicationId: z.string() }),
+  outputSchema: z.object({ score: z.number(), applicationId: z.string() }),
   handler: async (input) => {
     const score = await calculateRiskScore(input.applicationId);
     return { score, applicationId: input.applicationId };
@@ -103,12 +117,16 @@ const scoreStep: WorkflowStep = {
 Platform tools let your steps call integrations managed by Elevasis (email, CRM, databases, etc.). Import `platform` from `@elevasis/sdk/worker` and call it with the tool name, method, parameters, and an optional credential reference when the tool requires one.
 
 ```typescript
+import { z } from 'zod';
 import { platform, PlatformToolError } from '@elevasis/sdk/worker';
 import type { WorkflowStep } from '@elevasis/sdk';
-import { StepType } from '@elevasis/sdk';
 
 const sendEmailStep: WorkflowStep = {
-  type: StepType.LINEAR,
+  id: 'sendEmail',
+  name: 'Send Email',
+  description: 'Sends a transactional email via the platform email tool',
+  inputSchema: z.object({ recipientEmail: z.string(), subject: z.string(), body: z.string() }),
+  outputSchema: z.object({ sent: z.boolean(), messageId: z.string() }),
   handler: async (input, context) => {
     const result = await platform.call({
       tool: 'email',

package/reference/ui/exports.mdx

@@ -0,0 +1,60 @@
+---
+title: "@elevasis/ui Export Catalog"
+description: "Auto-generated catalog of all published @elevasis/ui subpath exports, derived from packages/ui/reference-manifest.ts."
+---
+
+{/* @generated by .claude/_gen/sync-sdk-catalog.ts — DO NOT EDIT */}
+{/* Regenerate: pnpm gen:sdk-catalog */}
+
+| Import | Title | Group | Description |
+| --- | --- | --- | --- |
+| `@elevasis/ui/provider` | Provider | Provider | Published provider and feature-shell contract for downstream apps. |
+| `@elevasis/ui/provider/ui` | Provider UI | Provider | Published provider UI entry for downstream applications. |
+| `@elevasis/ui/auth` | Auth | Foundation | Published authentication surface for UI integrations. |
+| `@elevasis/ui/auth/context` | Auth Context | Foundation | Published auth context entry for UI integrations. |
+| `@elevasis/ui/hooks` | Hooks | Hooks | Headless hooks surface for executions, sessions, observability, and operations. |
+| `@elevasis/ui/hooks/access` | Hooks Access | Hooks | Published Access Model hook surface for checking route, section, and action access. |
+| `@elevasis/ui/sse` | SSE | Foundation | Published server-sent events helpers and connection utilities. |
+| `@elevasis/ui/initialization` | Initialization | Foundation | Published app initialization provider and bootstrap helpers. |
+| `@elevasis/ui/profile` | Profile | Foundation | Published user profile surface for UI applications. |
+| `@elevasis/ui/organization` | Organization | Foundation | Published organization shell, store, and helper surface. |
+| `@elevasis/ui/features/auth` | Features Auth | Features | Published auth feature surface for downstream shells. |
+| `@elevasis/ui/features/clients` | Features Clients | Features | Published clients feature surface for downstream shells. |
+| `@elevasis/ui/features/crm` | Features CRM | Features | Published CRM feature surface for downstream shells. |
+| `@elevasis/ui/features/dashboard` | Features Dashboard | Features | Published dashboard feature surface for downstream shells. |
+| `@elevasis/ui/features/delivery` | Features Delivery | Features | Published delivery feature surface for downstream shells. |
+| `@elevasis/ui/features/lead-gen` | Features Lead Gen | Features | Published lead generation feature surface for downstream shells. |
+| `@elevasis/ui/features/operations` | Features Operations | Features | Published operations feature surface for downstream shells. |
+| `@elevasis/ui/features/monitoring` | Features Monitoring | Features | Published monitoring feature surface for downstream shells. |
+| `@elevasis/ui/features/monitoring/requests` | Features Monitoring Requests | Features | Published submitted-requests list, detail, and triage surface for downstream shells. |
+| `@elevasis/ui/features/seo` | Features SEO | Features | Published SEO feature surface for downstream shells. |
+| `@elevasis/ui/features/knowledge` | Features Knowledge | Features | Published knowledge feature manifest for downstream shells. |
+| `@elevasis/ui/features/notes` | Features Notes | Features | Published Notes panel view and supporting note components for shared right-panel integrations. |
+| `@elevasis/ui/features/right-panel-host` | Features Right Panel Host | Features | Published right-panel host provider, layer, trigger, keyboard shortcut, store, and view contract. |
+| `@elevasis/ui/knowledge` | Knowledge | Visual | Published knowledge browser primitives: Browser, Tree, NodeList, NodeView, SearchBar, MDX provider, and the generated KNOWLEDGE_BODIES map. |
+| `@elevasis/ui/vite` | Vite | Build | Composite Vite plugin factory (elevasisVite) that bundles all @elevasis/ui Vite plugins into a single array for consumer vite.config.ts files. |
+| `@elevasis/ui/vite-plugin-knowledge` | Vite Plugin Knowledge | Build | Vite plugin that regenerates the build-time knowledge MDX bodies and search index, with HMR support. |
+| `@elevasis/ui/features/settings` | Features Settings | Features | Published settings feature surface for downstream shells. |
+| `@elevasis/ui/types` | Types | Foundation | Published UI types entry for downstream applications. |
+| `@elevasis/ui/components` | Components | Components | Published UI component barrel for downstream applications. |
+| `@elevasis/ui/components/navigation` | Navigation Components | Components | Published navigation component entry for downstream applications. |
+| `@elevasis/ui/components/chat` | Chat Components | Components | Published chat component entry for downstream applications. |
+| `@elevasis/ui/layout` | Layout | Components | Published layout component entry for downstream applications. |
+| `@elevasis/ui/charts` | Charts | Components | Published chart component entry for downstream applications. |
+| `@elevasis/ui/theme` | Theme | Visual | Published theme entry for downstream applications. |
+| `@elevasis/ui/theme/presets` | Theme Presets | Visual | Re-exports the canonical THEME_PRESETS tuple, ThemePresetName union, and ThemePresetEnum Zod enum from @repo/core. Single source of truth for preset names across UI, schemas, and Zustand state. |
+| `@elevasis/ui/api` | API | Foundation | Published API client entry for downstream applications. |
+| `@elevasis/ui/utils` | Utils | Foundation | Published utility entry for downstream applications. |
+| `@elevasis/ui/graph` | Graph | Visual | Published graph helper and visualization entry. |
+| `@elevasis/ui/execution` | Execution | Foundation | Published execution visualization and helper entry. |
+| `@elevasis/ui/router` | Router | Foundation | Published router entry for downstream applications. |
+| `@elevasis/ui/router/context` | Router Context | Foundation | Published router context entry for downstream applications. |
+| `@elevasis/ui/zustand` | Zustand | Foundation | Published Zustand slice entry for downstream applications. |
+| `@elevasis/ui/app` | App | Foundation | Published app factory that composes providers, router, auth, and theme into a mountable React app. |
+| `@elevasis/ui/provider/ElevasisServiceContext` | Elevasis Service Context | Provider | Standalone service context and provider that supplies apiRequest, organizationId, and isReady to child components. |
+| `@elevasis/ui/hooks/delivery` | Hooks Delivery | Hooks | Published delivery hooks for projects, milestones, tasks, and notes. |
+| `@elevasis/ui/hooks/user-notes` | Hooks User Notes | Hooks | Published user-notes query and mutation hooks used by shared Notes surfaces. |
+| `@elevasis/ui/hooks/operations/command-view/utils/transformCommandViewData` | Transform Command View Data | Hooks | Utility that transforms backend CommandViewData arrays into a unified frontend CommandViewGraph with nodes and edges. |
+| `@elevasis/ui/test-utils` | Test Utils | Testing | Published rendering helpers, auth mocks, MSW handlers, and test provider utilities. |
+| `@elevasis/ui/test-utils/setup` | Test Utils Setup | Testing | Vitest setup file for UI consumers using browser mocks and MSW. |
+| `@elevasis/ui/test-utils/setup-integration` | Test Utils Integration Setup | Testing | Vitest setup file for integration tests that avoid MSW and use real network boundaries. |

package/reference/ui/index.mdx

@@ -0,0 +1,75 @@
+---
+title: "@elevasis/ui"
+description: The shared React 19 feature-shell and manifest-backed feature modules for Elevasis — Lead Gen, CRM, Projects, Operations, Monitoring, Settings, SEO, and more. Embeds into any host UI via ElevasisProvider.
+---
+
+`@elevasis/ui` is the shared React feature-shell for the Elevasis platform. It provides an `ElevasisProvider` and a set of manifest-backed feature modules that a host UI embeds and composes. The model is: your shell owns the layout and routing; Elevasis features plug in as self-contained modules.
+
+## Install
+
+```bash
+pnpm add @elevasis/ui
+```
+
+Many peer dependencies are optional. Pull only the peers that the features you use require. If you are not using the graph visualization features, you do not need `cytoscape`. If you are not using TanStack Router, you do not need it either.
+
+## Peer Dependencies
+
+`@elevasis/ui` has a broad peer dependency set. The required peers are React 19 and Mantine 8.2.7. Most others are optional and only needed when specific feature modules are activated.
+
+- **React 19** -- required. The feature modules use React 19 APIs.
+- **Mantine 8.2.7** -- required. The component layer and theming foundation.
+- **TanStack Query** -- required for data-fetching features (most modules).
+- **TanStack Router** -- optional; required if you want the routing-aware feature shells.
+- **Zod 4.1** -- required for schema validation in form-backed features.
+- **Zustand 5** -- required for state management in multi-panel features.
+- **cytoscape** -- optional; required for the graph/knowledge visualization modules only.
+
+## Provider and Feature-Shell Model
+
+The entry point is `ElevasisProvider`, imported from `@elevasis/ui/provider`. Wrap your application root with it to give all child feature modules access to the platform context, auth session, and manifest registry.
+
+```tsx
+import { ElevasisProvider } from "@elevasis/ui/provider";
+
+export function AppRoot() {
+  return (
+    <ElevasisProvider config={elevasisConfig}>
+      {/* your shell and routes */}
+    </ElevasisProvider>
+  );
+}
+```
+
+Feature modules are imported from their own subpaths (e.g. `@elevasis/ui/features/lead-gen`, `@elevasis/ui/features/crm`) and rendered inside the provider tree. Each module is manifest-backed: it reads the platform manifest at runtime to know which resources and workflows are available, so no hard-coded resource IDs are needed in the host UI.
+
+## Available Feature Modules
+
+The published feature surface includes modules for:
+
+- **Lead Gen** -- prospecting pipeline, campaign review, acquisition workflows
+- **CRM** -- client management, deal tracking, contact records
+- **Projects** -- task tracking, project lifecycle, milestones
+- **Operations** -- workflow execution history, operations dashboard
+- **Monitoring** -- execution health, error log, platform diagnostics
+- **Settings** -- organization settings, credential management, member management
+- **SEO** -- content and SEO tooling modules
+- **Notes** -- note capture and structured annotations
+- **Knowledge** -- knowledge base viewer and search UI
+- **Dashboard** -- compatibility components for host-owned dashboard shells
+
+Each module has its own `@elevasis/ui/features/<name>` subpath. See the [Export Catalog](exports.mdx) for the full generated list.
+
+## When To Use @elevasis/ui
+
+Use `@elevasis/ui` when you are building a host application that needs to embed Elevasis features -- lead-gen pipelines, CRM views, operations dashboards -- without re-implementing them. The provider/feature-shell model means you own the shell, navigation, and layout; Elevasis owns the feature logic and UI internals.
+
+You do not need `@elevasis/ui` if you are only writing backend workflows and agents. Tenant automation projects use `@elevasis/sdk` alone.
+
+## Composition With @elevasis/core
+
+`@elevasis/ui` uses `@elevasis/core` internally for entity schemas, org-model types, and auth contracts. Installing `@elevasis/ui` will pull in `@elevasis/core` as a dependency. You do not need to install `@elevasis/core` separately unless you need direct access to its subpaths.
+
+## Export Catalog
+
+See [Export Catalog](exports.mdx) for a generated table of all published subpath exports derived from the reference manifest.