@elevasis/sdk 1.28.1 → 1.30.0

package/reference/scaffold/reference/glossary.md

@@ -14,10 +14,16 @@ description: Terminology disambiguation for Organization OS concepts used in the
 
 **AccessKeys** -- exported access-key constants from `@elevasis/core/auth` / `@repo/core/auth` for platform-admin, diagnostic, and permission-backed gates.
 
-**Contract** -- the publishable boundary a consumer depends on: Zod schemas, TypeScript types, provider props, resource definitions, or workflow I/O schemas.
+**Boundary invariant** -- Organization Model rule that local resources may bind local System ontology directly, while sibling-System API behavior needs explicit scope through topology. For System Interfaces, lead-gen-to-CRM handoff is allowed through the `sales.lead-gen/crm-handoff` consumer, the `sales.crm/api` provider, scoped resources, and a `metadata.systemInterfaceGrant` topology grant.
+
+**Capability catalog** -- generated SDK-bundled reference that lists the closed System Interface profiles supported by the installed package, their required System paths, interface keys, and derived-readiness requirements. Current source: `packages/core/src/reference/_generated/system-interface-capabilities.md`; SDK mirror: `node_modules/@elevasis/sdk/reference/scaffold/reference/system-interface-capabilities.md`.
+
+**Contract** -- the publishable boundary a consumer depends on: Zod schemas, TypeScript types, provider props, resource definitions, resource ontology workflow I/O refs, or generated reference docs. Retired authored System/Bridge Contract surfaces such as `System.contracts`, `bridgeContracts`, and versioned `*@v1` OM contract IDs are not current authoring patterns.
 
 **DeploymentSpec** -- runtime/deploy assembly for one organization: workflows, agents, triggers, integrations, relationships, external resources, and human checkpoints. It assembles executable behavior around Organization Model resource descriptors; it is not the source of resource identity.
 
+**Derived readiness** -- readiness computed from resolved Organization Model facts instead of hand-authored readiness declarations. For System Interfaces, the checker evaluates the active `apiInterface` marker, scoped resource IDs, active resources, `resource.ontology` bindings, owned ontology, required catalogs, provider readiness, and scoped topology grants.
+
 **Feature** -- legacy or UI-package wording for a platform capability area. In the current Organization Model, use **System** for semantic ownership and **navigation surface** for shell placement. Keep "feature" only when referring to existing UI package folders, exported manifest names, or legacy compatibility recipes.
 
 **SystemGuard** -- retired route-level System gate. Use **AccessGuard** with a System path or `AccessKeys` constant.
@@ -48,6 +54,10 @@ description: Terminology disambiguation for Organization OS concepts used in the
 
 **System** -- tenant-defined bounded context in `OrganizationModel.systems` that groups operational resources and carries governance metadata such as responsible role, governing knowledge, driven goals, kind, lifecycle, System-local ontology, and System-local config.
 
+**System Interface** -- flat `System.apiInterface` marker that adopts a platform-provided API capability for a System. It declares intent through lifecycle, a closed `readinessProfile`, and optional scoped resource IDs; readiness is derived. Custom tenant Systems should not add custom `apiInterface` profiles. They extend behavior through workflows/operations plus ontology, resources, catalogs, topology, and navigation.
+
+**System Interface profile** -- platform-owned readiness profile from `SYSTEM_INTERFACE_PROFILES`, such as `sales.lead-gen.api`, `sales.crm.api`, or `sales.lead-gen.crm-handoff`. Profiles are a closed literal union tied to platform API consumers and readiness checkers, not tenant-defined extension strings.
+
 **ResourceCategory** -- resource metadata category: `production`, `diagnostic`, `internal`, or `testing`.
 
 **ResourceLink** -- graph binding on resource metadata: `{ nodeId, kind }`.
@@ -58,7 +68,9 @@ description: Terminology disambiguation for Organization OS concepts used in the
 
 **Subshell / Sidebar** -- System- or route-prefix-scoped UI region rendered when the current route matches a module whose manifest supplies a sidebar.
 
-**Topology** -- durable OM operational wiring declared in `OrganizationModel.topology.relationships`. Initial relationship kinds are `triggers`, `uses`, and `approval`; relationships use typed refs such as `{ kind: 'resource', id: 'lead-import' }`.
+**Scoped topology bridge** -- topology relationship scoped to a System or interface boundary, with metadata that grants a specific consumer interface access to a provider interface. It replaces authored Bridge Contract declarations for API handoff while keeping the bridge in `OrganizationModel.topology.relationships`.
+
+**Topology** -- durable OM operational wiring declared in `OrganizationModel.topology.relationships`. Relationship kinds are the closed set `triggers`, `uses`, and `approval`; relationships use typed refs such as `{ kind: 'resource', id: 'lead-import' }` and may carry structured metadata such as `systemInterfaceGrant`.
 
 ## Package Boundary
 

package/reference/scaffold/reference/system-interface-capabilities.md

@@ -0,0 +1,50 @@
+<!-- @generated by packages/sdk/scripts/copy-reference-docs.mjs -- DO NOT EDIT -->
+<!-- Regenerate: pnpm scaffold:sync -->
+
+<!-- @generated by scripts/monorepo/generate-scaffold-contracts.js -- DO NOT EDIT -->
+<!-- Regenerate: pnpm scaffold:sync -->
+
+# System Interface Capabilities
+
+This catalog is generated from `SYSTEM_INTERFACE_PROFILES` and the derived-readiness checks in `packages/core/src/business/acquisition/ontology-validation.ts`.
+
+System Interface profiles are a closed platform adoption handshake. Tenant custom Systems should extend behavior through workflows/operations plus ontology, resources, and topology instead of declaring custom `apiInterface.readinessProfile` values.
+
+| Profile | Required System path | Interface key |
+| --- | --- | --- |
+| `sales.lead-gen.api` | `sales.lead-gen` | `api` |
+| `sales.crm.api` | `sales.crm` | `api` |
+| `sales.lead-gen.crm-handoff` | `sales.lead-gen` | `crm-handoff` |
+
+## `sales.lead-gen.api`
+
+- Required System path: `sales.lead-gen`
+- Interface key: `api`
+- Derived-readiness requirements:
+  - System Interface marker must be active and scope at least one active `sales.lead-gen` Resource.
+  - Object types: `sales.lead-gen:object/list`, `sales.lead-gen:object/company`, `sales.lead-gen:object/contact`.
+  - Scoped Resource `ontology.reads` bindings for each required object type.
+  - Catalog types with entries: `sales.lead-gen:catalog/build-template`, `sales.lead-gen:catalog/company-stage`, `sales.lead-gen:catalog/contact-stage`, and derived `sales.lead-gen:catalog/lead-gen.stage-catalog`.
+  - Scoped Resource `ontology.usesCatalogs` bindings for each required catalog.
+  - A lead-gen template-step catalog owned by `sales.lead-gen` whose `appliesTo` value is `sales.lead-gen:object/list`, plus a scoped `ontology.usesCatalogs` binding for it.
+
+## `sales.crm.api`
+
+- Required System path: `sales.crm`
+- Interface key: `api`
+- Derived-readiness requirements:
+  - System Interface marker must be active and scope at least one active `sales.crm` Resource.
+  - Catalog type with entries: `sales.crm:catalog/crm.pipeline`.
+  - Scoped Resource `ontology.usesCatalogs` binding for `sales.crm:catalog/crm.pipeline`.
+
+## `sales.lead-gen.crm-handoff`
+
+- Required System path: `sales.lead-gen`
+- Interface key: `crm-handoff`
+- Derived-readiness requirements:
+  - Derived handoff readiness is evaluated for `sales.lead-gen/crm-handoff`; it is not authored as a separate custom tenant API surface.
+  - Lead-gen API readiness requirements must pass for `sales.lead-gen/api`.
+  - CRM pipeline catalog must exist with entries: `sales.crm:catalog/crm.pipeline`. Foreign ownership is allowed because the provider is `sales.crm/api`.
+  - Derived scoped resources are active `sales.lead-gen` Resources whose `ontology.usesCatalogs` includes `sales.crm:catalog/crm.pipeline`.
+  - Provider readiness must pass for `sales.crm/api`.
+  - Topology must include a scoped `systemInterfaceGrant` relationship from consumer `sales.lead-gen/crm-handoff` to provider `sales.crm/api`.

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

@@ -60,14 +60,26 @@ elevasis-sdk project:task:delete <id>
 Task commands also expose agent-oriented resume state:
 
 ```bash
-elevasis-sdk project:task:resume <id> --pretty
-elevasis-sdk project:task:save <id> --current-state "Implemented the route layer"
+elevasis-sdk project:task:resume <id> [--pretty]
+elevasis-sdk project:task:save <id> --current-state <text> [--files-modified <json>] [--next-steps <text>] [--key-docs <json>] [--tools <json>]
 ```
 
-- `project:task:resume` reads the task's `resume_context`
-- `project:task:save` merges fields into `resume_context`
+- `project:task:resume <id>` -- reads the task's `resume_context` JSONB; `--pretty` renders a human-readable briefing with current state, next steps, files modified, key docs, and tools used
+- `project:task:save <id>` -- merges fields into `resume_context`; `--current-state` is required; all other flags are optional JSON arrays or plain text
 - these commands are the CLI counterpart to `/work resume` and `/work save` style flows
 
+**`project:task:save` flags:**
+
+| Flag                        | Description                               |
+| --------------------------- | ----------------------------------------- |
+| `--current-state <text>`  | Required. Current state description       |
+| `--files-modified <json>` | JSON array of modified file paths         |
+| `--next-steps <text>`     | Next steps description                    |
+| `--key-docs <json>`       | JSON array of key doc paths               |
+| `--tools <json>`          | JSON array of tool names used             |
+| `--pretty`                  | Human-readable output instead of raw JSON |
+| `--api-url <url>`         | Override the API base URL                 |
+
 ### Notes
 
 ```bash
@@ -336,7 +348,17 @@ JWT-gated routes at the original unprefixed paths remain for the Command Center.
 
 **Note:** List-inspection routing lives in `/om` (Acquisition Operations dispatch). The `/acquisition` skill was folded into `/om`; all list reads still route to `elevasis-sdk acquisition:list:get <uuid>`.
 
-**Flags (all acquisition commands):**
+**`acquisition:list:get` flags:**
+
+| Flag                     | Description                                        |
+| ------------------------ | -------------------------------------------------- |
+| `--no-include-deals`     | Exclude thin deal lineage refs from the response   |
+| `--deal-limit <limit>` | Maximum number of thin deal refs to include        |
+| `--include-progress`     | Include processing progress aggregates             |
+| `--pretty`               | Human-readable terminal output instead of raw JSON |
+| `--api-url <url>`      | Override the API base URL                          |
+
+**Shared flags (all other acquisition commands):**
 
 | Flag                | Description                                        |
 | ------------------- | -------------------------------------------------- |
@@ -409,20 +431,30 @@ elevasis-sdk session:get <id>
 elevasis-sdk session:end <id>
 ```
 
-- `session:list` -- list sessions for the organization; supports filtering by resource, status, and time range
+- `session:list` -- list sessions for the organization; supports filtering by resource ID, user ID, and limit
 - `session:get <id>` -- get full session detail including messages and events
 - `session:end <id>` -- gracefully end an active session
 
-**API routes:** `GET /api/external/sessions`, `/api/external/sessions/:id`, `POST /api/external/sessions/:id/end`
+**API routes:** `GET /api/external/sessions`, `/api/external/sessions/:id`, `DELETE /api/external/sessions/:id`
 
-**Flags:**
+**`session:list` filter flags:**
 
-| Flag                | Description                                        |
-| ------------------- | -------------------------------------------------- |
-| `--pretty`          | Human-readable terminal output instead of raw JSON |
-| `--api-url <url>` | Override the API base URL                          |
+| Flag                   | Description                          |
+| ---------------------- | ------------------------------------ |
+| `--resource-id <id>` | Filter by agent resource ID          |
+| `--user-id <id>`     | Filter by user ID                    |
+| `--limit <limit>`    | Maximum number of sessions to return |
+| `--json`               | Output as JSON                       |
+| `--api-url <url>`    | Override the API base URL            |
+
+**Shared flags (`session:get`, `session:end`):**
+
+| Flag                | Description               |
+| ------------------- | ------------------------- |
+| `--json`            | Output as JSON            |
+| `--api-url <url>` | Override the API base URL |
 
-**Implementation:** `packages/sdk/src/cli/commands/` (session family)
+**Implementation:** `packages/sdk/src/cli/commands/session/session.ts`
 
 ---
 
@@ -440,6 +472,30 @@ elevasis-sdk queue:expire <id> --pretty
 elevasis-sdk queue:status --pretty
 ```
 
+**`queue:list` filter flags:**
+
+| Flag                        | Description                                                                 |
+| --------------------------- | --------------------------------------------------------------------------- |
+| `--status <status>`       | Filter by status: `pending`, `processing`, `completed`, `failed`, `expired` |
+| `--human-checkpoint <id>` | Filter by checkpoint ID, or `ungrouped` for tasks without a checkpoint      |
+| `--time-range <range>`    | Filter by created time range: `1h`, `24h`, `7d`, `30d`                      |
+| `--priority-min <number>` | Minimum priority, 1-10                                                      |
+| `--priority-max <number>` | Maximum priority, 1-10                                                      |
+| `--limit <limit>`         | Maximum number of tasks to return                                           |
+| `--offset <offset>`       | Number of tasks to skip                                                     |
+| `--pretty`                  | Human-readable output instead of raw JSON                                   |
+| `--api-url <url>`         | Override the API base URL                                                   |
+
+**`queue:select` flags:**
+
+| Flag                 | Description                               |
+| -------------------- | ----------------------------------------- |
+| `--action-id <id>` | Required. Action ID to select             |
+| `--payload <json>` | Optional action payload as JSON           |
+| `--notes <notes>`  | Optional human decision notes             |
+| `--pretty`           | Human-readable output instead of raw JSON |
+| `--api-url <url>`  | Override the API base URL                 |
+
 **Auth:** Calls `/api/external/command-queue/*` with API-key auth.
 
 ---
@@ -460,6 +516,20 @@ elevasis-sdk schedule:resume <id> --pretty
 elevasis-sdk schedule:cancel <id> --pretty
 ```
 
+**`schedule:update` flags:**
+
+| Flag                         | Description                                                               |
+| ---------------------------- | ------------------------------------------------------------------------- |
+| `--name <name>`            | New schedule name                                                         |
+| `--description <text>`     | New schedule description                                                  |
+| `--clear-description`        | Remove the schedule description (mutually exclusive with `--description`) |
+| `--schedule-config <json>` | Replacement schedule config JSON                                          |
+| `--max-retries <number>`   | Maximum retry attempts, 0-10                                              |
+| `--pretty`                   | Human-readable output instead of raw JSON                                 |
+| `--api-url <url>`          | Override the API base URL                                                 |
+
+At least one field must be provided. `--description` and `--clear-description` are mutually exclusive.
+
 **Auth:** Calls `/api/external/task-scheduler/schedules*` with API-key auth.
 
 ---
@@ -476,10 +546,86 @@ For the full command reference, flag details, and graph architecture, see the [k
 elevasis-sdk knowledge:ls /by-system/sales.crm
 elevasis-sdk knowledge:cat <node-id>
 elevasis-sdk knowledge:graph
+elevasis-sdk knowledge:search <query>
+elevasis-sdk knowledge:describe <nodeId>
+elevasis-sdk knowledge:skills <nodeId>
+elevasis-sdk knowledge:generate
 ```
 
 These are registered as `knowledge:*` subcommands on `elevasis-sdk`. Both the SDK CLI (`elevasis-sdk knowledge:*`) and the platform CLI (`elevasis knowledge:*`) call the same query functions in `@repo/core/knowledge/queries`.
 
+### knowledge:search
+
+Universal keyword search across the entire Organization Model (systems, resources, knowledge, ontology, roles, policies). Alias: `om:search`.
+
+```bash
+elevasis-sdk knowledge:search <query> [--limit <n>] [--kinds <list>] [--json] [--ids-only]
+```
+
+| Flag               | Description                                                                    |
+| ------------------ | ------------------------------------------------------------------------------ |
+| `--limit <n>`    | Max hits to return; `0` = unlimited. Default: 10                               |
+| `--kinds <list>` | Comma-separated kinds filter: `system,resource,knowledge,ontology,role,policy` |
+| `--json`           | Print wrapped JSON envelope `{ query, limit, kinds, count, results }`          |
+| `--ids-only`       | Print one ID per line (for piping)                                             |
+
+**Examples:**
+
+```bash
+elevasis-sdk om:search "lead gen"
+elevasis-sdk om:search outreach --kinds knowledge
+elevasis-sdk om:search apollo --ids-only
+```
+
+### knowledge:describe
+
+Structured neighborhood view for any OM node ID. Auto-detects kind (system, resource, knowledge, ontology, role, policy) from the ID shape. Alias: `om:describe`.
+
+```bash
+elevasis-sdk knowledge:describe <nodeId> [--json]
+```
+
+**Examples:**
+
+```bash
+elevasis-sdk om:describe sales.lead-gen
+elevasis-sdk om:describe knowledge.outreach-playbook
+```
+
+### knowledge:skills
+
+Show callable invocations on graph neighbors for a knowledge node -- useful for discovering which actions or agent resources are linked to a given knowledge entry. Alias: `om:skills`.
+
+```bash
+elevasis-sdk knowledge:skills <nodeId> [--json]
+```
+
+**Example:**
+
+```bash
+elevasis-sdk om:skills knowledge.new-vertical-launch-playbook
+```
+
+### knowledge:generate
+
+Generate Organization Model knowledge nodes from MDX source files. Alias: `om:generate`.
+
+```bash
+elevasis-sdk knowledge:generate [--source <path>] [--output <path>] [--flags-output <path>]
+```
+
+| Flag                      | Description                                                                                           |
+| ------------------------- | ----------------------------------------------------------------------------------------------------- |
+| `--source <path>`       | MDX source directory relative to project root. Default: `core/config/knowledge/nodes`                 |
+| `--output <path>`       | Generated TS file path relative to project root. Default: `core/config/knowledge/_generated/nodes.ts` |
+| `--flags-output <path>` | Generated knowledge flag registry path. Default: `.claude/registries/knowledge-flags.json`            |
+
+**Example:**
+
+```bash
+elevasis-sdk om:generate
+```
+
 ---
 
 ## elevasis-sdk ui:use-local / ui:use-published

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. |