@elevasis/sdk 1.28.1 → 1.29.0

package/dist/cli.cjs

@@ -38925,7 +38925,9 @@ function getAllBuildTemplates(model) {
     (catalog) => entriesOf(catalog).map(([templateId, templateEntry]) => {
       const stepCatalogId = stringValue(templateEntry.stepCatalog);
       const stepCatalog = stepCatalogId !== void 0 ? stepCatalogs.get(stepCatalogId) : void 0;
-      const steps = stepCatalog === void 0 ? [] : entriesOf(stepCatalog);
+      const steps = stepCatalog === void 0 ? [] : entriesOf(stepCatalog).sort(
+        ([leftId, left], [rightId, right]) => numberValue(left.order, Number.MAX_SAFE_INTEGER) - numberValue(right.order, Number.MAX_SAFE_INTEGER) || leftId.localeCompare(rightId)
+      );
       return {
         order: numberValue(templateEntry.order, Number.MAX_SAFE_INTEGER),
         template: {
@@ -44712,7 +44714,7 @@ function wrapAction(commandName, fn) {
 // package.json
 var package_default = {
   name: "@elevasis/sdk",
-  version: "1.28.1",
+  version: "1.29.0",
   description: "SDK for building Elevasis organization resources",
   type: "module",
   bin: {

package/dist/index.d.ts

@@ -4546,6 +4546,17 @@ type Database = {
                 Args: never;
                 Returns: undefined;
             };
+            repair_membership_role_assignments: {
+                Args: never;
+                Returns: {
+                    membership_id: string;
+                    organization_id: string;
+                    repaired: boolean;
+                    role_id: string;
+                    role_slug: string;
+                    user_id: string;
+                }[];
+            };
             sync_all_memberships_with_role: {
                 Args: {
                     p_role_id: string;
@@ -4558,6 +4569,13 @@ type Database = {
                 };
                 Returns: undefined;
             };
+            update_membership_role_assignment: {
+                Args: {
+                    p_role_slug: string;
+                    p_workos_membership_id: string;
+                };
+                Returns: string;
+            };
             upsert_user_profile: {
                 Args: never;
                 Returns: {

package/dist/test-utils/index.d.ts

@@ -4379,6 +4379,17 @@ type Database = {
                 Args: never;
                 Returns: undefined;
             };
+            repair_membership_role_assignments: {
+                Args: never;
+                Returns: {
+                    membership_id: string;
+                    organization_id: string;
+                    repaired: boolean;
+                    role_id: string;
+                    role_slug: string;
+                    user_id: string;
+                }[];
+            };
             sync_all_memberships_with_role: {
                 Args: {
                     p_role_id: string;
@@ -4391,6 +4402,13 @@ type Database = {
                 };
                 Returns: undefined;
             };
+            update_membership_role_assignment: {
+                Args: {
+                    p_role_slug: string;
+                    p_workos_membership_id: string;
+                };
+                Returns: string;
+            };
             upsert_user_profile: {
                 Args: never;
                 Returns: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elevasis/sdk",
-  "version": "1.28.1",
+  "version": "1.29.0",
   "description": "SDK for building Elevasis organization resources",
   "type": "module",
   "bin": {
@@ -58,9 +58,9 @@
     "tsup": "^8.0.0",
     "typescript": "5.9.2",
     "zod": "^4.1.0",
-    "@repo/core": "0.35.1",
-    "@repo/typescript-config": "0.0.0",
-    "@repo/eslint-config": "0.0.0"
+    "@repo/core": "0.36.0",
+    "@repo/eslint-config": "0.0.0",
+    "@repo/typescript-config": "0.0.0"
   },
   "scripts": {
     "lint": "eslint src --max-warnings 0",

package/reference/_navigation.md

@@ -46,25 +46,25 @@ Package entries indexed: 60.
 
 | Resource | Location | Description | When to Load |
 | --- | --- | --- | --- |
-| SDK | `index.mdx` | Root SDK types, config, runtime errors, and registry surface. | (not specified) |
+| SDK | `sdk/index.mdx` | Root SDK types, config, runtime errors, and registry surface. | (not specified) |
 
 ## @elevasis/sdk / Runtime
 
 | Resource | Location | Description | When to Load |
 | --- | --- | --- | --- |
-| Worker Runtime | `runtime.mdx` | Worker runtime entrypoint, adapters, and platform execution surface. | (not specified) |
+| Worker Runtime | `sdk/runtime.mdx` | Worker runtime entrypoint, adapters, and platform execution surface. | (not specified) |
 
 ## @elevasis/sdk / Testing
 
 | Resource | Location | Description | When to Load |
 | --- | --- | --- | --- |
-| Test Utils | `runtime.mdx` | Workflow runner, registry assertion, and typed adapter mocks for SDK consumers. | (not specified) |
+| Test Utils | `sdk/runtime.mdx` | Workflow runner, registry assertion, and typed adapter mocks for SDK consumers. | (not specified) |
 
 ## @elevasis/sdk / Tooling
 
 | Resource | Location | Description | When to Load |
 | --- | --- | --- | --- |
-| Node Build Tooling | `cli.mdx` | Node-only build helpers: knowledge codegen and other fs/path/process utilities. Not browser-safe. | (not specified) |
+| Node Build Tooling | `sdk/cli.mdx` | Node-only build helpers: knowledge codegen and other fs/path/process utilities. Not browser-safe. | (not specified) |
 
 ## @elevasis/ui / Build
 

package/reference/_reference-manifest.json

@@ -95,8 +95,8 @@
       "group": "Getting Started",
       "order": 1,
       "sourcePath": "packages/sdk/src/index.ts",
-      "docPath": "apps/docs/content/docs/sdk/index.mdx",
-      "referencePath": "index.mdx",
+      "docPath": "apps/docs/content/docs/sdk/sdk/index.mdx",
+      "referencePath": "sdk/index.mdx",
       "publishedExportPath": "./dist/index.js"
     },
     {
@@ -109,8 +109,8 @@
       "group": "Runtime",
       "order": 1,
       "sourcePath": "packages/sdk/src/worker/index.ts",
-      "docPath": "apps/docs/content/docs/sdk/runtime.mdx",
-      "referencePath": "runtime.mdx",
+      "docPath": "apps/docs/content/docs/sdk/sdk/runtime.mdx",
+      "referencePath": "sdk/runtime.mdx",
       "publishedExportPath": "./dist/worker/index.js"
     },
     {
@@ -123,8 +123,8 @@
       "group": "Testing",
       "order": 1,
       "sourcePath": "packages/sdk/src/test-utils/index.ts",
-      "docPath": "apps/docs/content/docs/sdk/runtime.mdx",
-      "referencePath": "runtime.mdx",
+      "docPath": "apps/docs/content/docs/sdk/sdk/runtime.mdx",
+      "referencePath": "sdk/runtime.mdx",
       "publishedExportPath": "./dist/test-utils/index.js"
     },
     {
@@ -137,8 +137,8 @@
       "group": "Tooling",
       "order": 1,
       "sourcePath": "packages/sdk/src/node/index.ts",
-      "docPath": "apps/docs/content/docs/sdk/cli.mdx",
-      "referencePath": "cli.mdx",
+      "docPath": "apps/docs/content/docs/sdk/sdk/cli.mdx",
+      "referencePath": "sdk/cli.mdx",
       "publishedExportPath": "./dist/node/index.js"
     },
     {

package/reference/claude-config/hooks/scaffold-registry-reminder.mjs

@@ -16,7 +16,7 @@ const ROOT = process.env.CLAUDE_PROJECT_DIR ?? process.cwd()
 const LOG_DIR = join(ROOT, '.claude', 'logs')
 const LOG_FILE = join(LOG_DIR, 'scaffold-registry-reminder.log')
 const STATE_FILE = join(LOG_DIR, 'scaffold-registry-reminder.state.json')
-const REGISTRY_FILE = join(ROOT, '.claude', 'scaffold-registry.compiled.json')
+const REGISTRY_FILE = join(ROOT, '.claude', 'registries', 'scaffold-registry.compiled.json')
 
 const DEFAULT_COOLDOWN_MS = 300_000 // 5 minutes
 
@@ -89,7 +89,7 @@ function emitReminder(entry, relFilePath) {
     lines.push(formatDependentLine(dep))
   }
   lines.push(
-    `  If this is a scaffold-sensitive pattern not in the registry, also add an entry to .claude/scaffold-registry.yml.`
+    `  If this is a scaffold-sensitive pattern not in the registry, also add an entry to .claude/registries/scaffold-registry.yml.`
   )
   return lines.join('\n')
 }
@@ -98,7 +98,7 @@ function emitMissingEntryHint(relFilePath) {
   return [
     `\uD83D\uDD14 Scaffold reminder -- unregistered generated path (${relFilePath})`,
     `  This path looks scaffold-generated but has no registry entry.`,
-    `  If it is scaffold-sensitive, add a new entry to .claude/scaffold-registry.yml`,
+    `  If it is scaffold-sensitive, add a new entry to .claude/registries/scaffold-registry.yml`,
     `  so the reminder hook and /work handoff can track it.`
   ].join('\n')
 }

package/reference/claude-config/skills/tutorial/technical.md

@@ -494,7 +494,7 @@ how data flows between steps.
 **Estimated time:** 25 min
 
 **Files referenced:** `node_modules/@elevasis/sdk/reference/scaffold/operations/workflow-recipes.md`,
-`apps/docs/content/docs/sdk/concepts.mdx` (design decisions section)
+`apps/docs/content/docs/sdk/sdk/concepts.mdx` (design decisions section)
 
 **Flow:**
 
@@ -1044,7 +1044,7 @@ result) and understands when to use an agent definition vs a workflow definition
 **Estimated time:** 25 min
 
 **Files referenced:** `node_modules/@elevasis/sdk/reference/scaffold/operations/workflow-recipes.md`,
-`apps/docs/content/docs/sdk/concepts.mdx` (workflow vs agent section)
+`apps/docs/content/docs/sdk/sdk/concepts.mdx` (workflow vs agent section)
 
 **Flow:**
 
@@ -1076,7 +1076,7 @@ The SDK converts the Zod schema to JSON Schema internally. The LLM is instructed
 matching that shape. The result is validated and returned as the inferred TypeScript type.
 
 **Agent definition vs workflow definition.** Read the glossary entries from
-`apps/docs/content/docs/sdk/concepts.mdx`:
+`apps/docs/content/docs/sdk/sdk/concepts.mdx`:
 
 - **Workflow** -- deterministic, step-by-step, 300s timeout. Use when inputs and outputs are
   known and the process is predefined.
@@ -1171,7 +1171,7 @@ understands the scaffold registry's purpose.
 **Estimated time:** 20 min
 
 **Files referenced:** `.claude/rules/` (all files), `.claude/memory/` (layout),
-`.claude/scaffold-registry.yml` (reference, monorepo-side concept)
+`.claude/registries/scaffold-registry.yml` (reference, monorepo-side concept)
 
 **Flow:**
 
@@ -1205,7 +1205,7 @@ glob of files it applies to. The rules system discovers it automatically -- no r
 Memory files are readable by the agent at session start. The `profile.md` file is particularly
 important: it sets the project-wide tone for all sessions after the tutorial track is selected.
 
-**Scaffold registry (monorepo-side concept).** `.claude/scaffold-registry.yml` is the
+**Scaffold registry (monorepo-side concept).** `.claude/registries/scaffold-registry.yml` is the
 monorepo's source-of-truth for scaffold dependencies -- it maps source paths to generated or
 manual scaffolds that depend on them. It drives the PostToolUse reminder hook and `/work handoff`
 preflight in the monorepo. In an external project you are a consumer, not a contributor, of that

package/reference/claude-config/sync-notes/2026-05-24-platform-invite-router-core-baseline.md

@@ -0,0 +1,28 @@
+# Platform Invite Router Core Baseline
+
+## Why this note exists
+
+The platform invite router train publishes a new `@elevasis/core` auth schema export for the narrow organization auth-config endpoint used by the backend invite router.
+
+## Applies to
+
+- Template-derived projects that consume `@elevasis/core`.
+- Project `core/package.json` and `operations/package.json` package baselines after the core release.
+
+## Required actions
+
+- Accept the `@elevasis/core` dependency baseline update after the core publish stage.
+- Do not add tenant app-origin routing code to template projects from this train; invitation routing remains platform API behavior.
+- Keep tenant app WorkOS login routes accepting `invitation_token` when project-specific launch work has already added that route support.
+
+## Verification
+
+- Run `pnpm sync:verify` after manifest-scoped external sync.
+- For projects receiving the baseline, run project-local checks required by the sync plan.
+
+## Not handled by /git-sync
+
+- Publishing `@elevasis/core`.
+- Updating package baselines after publish.
+- WorkOS production application configuration.
+- Per-tenant invitation smoke tests.

package/reference/core/exports.mdx

@@ -0,0 +1,16 @@
+---
+title: "@elevasis/core Export Catalog"
+description: "Auto-generated catalog of all published @elevasis/core subpath exports, derived from packages/core/reference-manifest.ts."
+---
+
+{/* @generated by .claude/_gen/sync-sdk-catalog.ts — DO NOT EDIT */}
+{/* Regenerate: pnpm gen:sdk-catalog */}
+
+| Import | Title | Group | Description |
+| --- | --- | --- | --- |
+| `@elevasis/core` | Core | Core | Published core wrapper for the curated contract surface. |
+| `@elevasis/core/auth` | Auth | Auth | Published browser-safe auth contracts, AccessKeys, and Access Model primitives. |
+| `@elevasis/core/organization-model` | Organization Model | Organization Model | Published organization-model schema, defaults, resolver, and types. |
+| `@elevasis/core/knowledge` | Knowledge | Knowledge | Published knowledge query layer: bySystem/byKind/byOwner/governs/governedBy queries, parsePath, and output formatters. |
+| `@elevasis/core/entities` | Entities | Entities | Published base entity contracts (Project, Milestone, Task, Deal, Company, Contact) generic over a metadata extension slot. |
+| `@elevasis/core/test-utils` | Test Utilities | Testing | Published test fixtures, mocks, and shared helpers for downstream automated tests. |

package/reference/core/index.mdx

@@ -0,0 +1,58 @@
+---
+title: "@elevasis/core"
+description: The shared Zod contract layer for the Elevasis platform — organization model, entity schemas, knowledge graph, auth types, and test utilities. Used by both @elevasis/sdk and @elevasis/ui.
+---
+
+`@elevasis/core` is the shared contract layer for the Elevasis platform. It exports Zod schemas and TypeScript types that are used by `@elevasis/sdk`, `@elevasis/ui`, and the platform API itself. Installing it gives you the typed contracts without pulling in the full SDK runtime or React dependencies.
+
+## Install
+
+```bash
+pnpm add @elevasis/core
+```
+
+The default export and most subpaths are browser-safe. No Node.js-specific runtime is required for the schema and type contracts.
+
+## Published Subpaths
+
+`@elevasis/core` ships six published subpaths:
+
+- **`.`** (default) -- base schemas, shared utilities, and the root contract surface. Browser-safe.
+- **`./auth`** -- auth contract types: session shapes, membership, role definitions, and WorkOS integration contracts.
+- **`./organization-model`** -- the organization model (OM) schema: system definitions, resource metadata, and the org-model graph types used by the platform's AI routing layer.
+- **`./entities`** -- entity schemas: typed definitions for leads, clients, deals, contacts, and other CRM-adjacent records.
+- **`./knowledge`** -- knowledge graph schemas: document types, embedding metadata, and retrieval contract types.
+- **`./test-utils`** -- Zod-based test fixtures and factory helpers. Not for production use.
+
+Import a subpath directly:
+
+```ts
+import { orgModelSchema } from "@elevasis/core/organization-model";
+import { entitySchema } from "@elevasis/core/entities";
+import { knowledgeDocSchema } from "@elevasis/core/knowledge";
+```
+
+## Browser / Server Split
+
+The default export and all named subpaths above are browser-safe -- they contain only Zod schemas, TypeScript types, and pure utility functions. There are no Node.js-specific APIs, filesystem access, or server-side dependencies in the published surface.
+
+The broader workspace `exports` (~40 paths in `packages/core`) are internal to the monorepo and not part of the published surface. Only the six subpaths listed above are available to tenant projects.
+
+## When To Use @elevasis/core Directly
+
+Most tenant projects install `@elevasis/sdk`, which includes `@elevasis/core` as a dependency. You need `@elevasis/core` directly when:
+
+- You are building a shared library or utility layer that needs the Elevasis types but not the SDK runtime.
+- You are writing a server-side API that validates Elevasis contracts (entity schemas, org model, auth types) without deploying workflows.
+- You are building a custom UI that needs the typed contracts alongside `@elevasis/ui` without the CLI or worker adapter surface.
+- You need `./test-utils` for fixture generation in tests outside an SDK project.
+
+## How It Composes With @elevasis/sdk
+
+`@elevasis/sdk` re-exports the core contracts you need for day-to-day workflow and agent development. When you import step types, entity schemas, or org-model references from `@elevasis/sdk`, those types are sourced from `@elevasis/core` internally.
+
+For advanced use cases -- writing custom validators, extending the org model, or building a server that enforces the same contracts the platform uses -- import from `@elevasis/core` subpaths directly rather than going through the SDK layer.
+
+## Export Catalog
+
+See [Export Catalog](exports.mdx) for a generated table of all published subpath exports derived from the reference manifest.

package/reference/index.mdx

@@ -1,93 +1,62 @@
 ---
 title: Elevasis SDK
-description: Build and deploy workflows, agents, and resources with the Elevasis SDK
+description: The three published Elevasis packages — @elevasis/sdk, @elevasis/core, and @elevasis/ui — that tenant projects install and compose to build AI workflows and feature-rich applications on the platform.
 ---
 
-`@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.
+The Elevasis SDK is the published surface for building on the Elevasis platform. It ships as three independent npm packages that can be installed together or separately depending on what you are building.
 
-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.
+- **`@elevasis/sdk`** -- runtime + resource definitions + CLI + worker adapters. The entry point for any tenant project. Install this to write workflows, agents, and resources and deploy them to the platform.
+- **`@elevasis/core`** -- shared Zod schemas, organization model, knowledge graph, entity contracts, and auth types. Install this when you need the typed contracts without the full SDK runtime.
+- **`@elevasis/ui`** -- React 19 feature-shell and manifest-backed feature modules (Lead Gen, CRM, Projects, Operations, Monitoring, Settings, SEO, and more). Install this when you are building a host UI that embeds Elevasis features.
 
-The SDK ships with a full CLI (`elevasis-sdk`) for validation, deployment, execution, inspection, and project-management operations. Platform tools expose 70+ tools 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.
+## How They Compose
 
-## Quick Start
+A typical tenant project installs `@elevasis/sdk` first. The SDK peer-depends on `@elevasis/core` for its shared schemas, so the contracts are always in sync. A tenant UI project adds `@elevasis/ui` on top to embed the shared React feature modules into its own shell.
 
-```bash
-pnpm dlx @elevasis/sdk init my-project
-cd my-project
-pnpm install
-elevasis-sdk deploy
+```
+@elevasis/sdk       -- workflows, agents, adapters, CLI, deploy
+      |
+      uses types from
+      |
+@elevasis/core      -- Zod schemas, org model, entities, knowledge, auth
+
+@elevasis/ui        -- React feature-shell (provider + manifest-backed modules)
+      |
+      uses types from
+      |
+@elevasis/core
 ```
 
-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 70+ tools 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
+You do not need all three packages. A pure automation project needs only `@elevasis/sdk`. A shared-types layer needs only `@elevasis/core`. A UI host without custom workflows can install `@elevasis/ui` alone.
 
-### Core Concepts
+## Packages
 
-- [Resources](resources/index.mdx) - Workflow and agent definition patterns, Zod schemas, step types, and routing
-- [Platform Tools](platform-tools/index.mdx) - Full catalog of 70+ tools, integration adapters, and credential management
-- [Credential Security](platform-tools/index.mdx#credential-security) - Three-layer credential model, HTTP tool patterns, and credential management
+### @elevasis/sdk (v1.28.1)
 
-### Reference
+The primary developer package. Provides the TypeScript API for defining workflows and agents, the `elevasis-sdk` CLI for validation and deployment, and typed worker adapters for 25 platform and integration tools.
 
-- [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
+**Install:** `pnpm add @elevasis/sdk`
 
-### Typed Adapters
+**Published subpaths:** `.` (default), `./worker`, `./test-utils`, `./node`
 
-- [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 9 platform service adapters: scheduler, storage, llm, pdf, approval, and more
+See [@elevasis/sdk](sdk/index.mdx) for the full group overview, getting started guide, CLI reference, adapter catalog, and more.
 
-### Framework
+### @elevasis/core (v0.35.1)
 
-- [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
+The shared contract layer. Exports Zod schemas and TypeScript types that are shared between the SDK, the UI, and the platform API. Useful when you need the typed contracts (organization model, entities, knowledge, auth) in a package that does not pull in the full SDK runtime.
 
-### Resources Subpages
+**Install:** `pnpm add @elevasis/core`
 
-- [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
+**Published subpaths:** `.` (default), `./auth`, `./test-utils`, `./organization-model`, `./entities`, `./knowledge`
 
-### Deployment Subpages
+See [@elevasis/core](core/index.mdx) for subpath details, browser/server split, and when to use it.
 
-- [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
+### @elevasis/ui (v2.39.1)
 
-### More
+The shared React feature-shell. Provides an `ElevasisProvider` and manifest-backed feature modules that a host UI embeds. Many peer dependencies are optional -- pull only what the features you use require.
 
-- [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
+**Install:** `pnpm add @elevasis/ui`
 
----
+**Peer deps:** React 19, Mantine 8.2.7, TanStack Query, TanStack Router, Zod 4.1, Zustand 5, cytoscape (many optional)
 
-**Last Updated:** 2026-05-19
+See [@elevasis/ui](ui/index.mdx) for the provider model, feature modules, peer dependency details, and when to use it.