@elevasis/sdk 1.13.2 → 1.14.1

package/dist/test-utils/index.js

@@ -6716,6 +6716,7 @@ createAdapter("acqDb", [
   "updateList",
   "deleteList",
   "addContactsToList",
+  "addCompaniesToList",
   "updateCompanyStage",
   "updateContactStage",
   // Company operations
@@ -6758,11 +6759,9 @@ createAdapter("acqDb", [
   "clearDealFields",
   "deleteDeal",
   "recordDealActivity",
-  "recordTouchpoint",
   "setDealStateKey",
   "transitionDeal",
   "loadDeal",
-  "listDealTouchpoints",
   // Deal note operations
   "createDealNote",
   "listDealNotes",
@@ -24276,7 +24275,11 @@ var mockAcqDb = (overrides) => createMockAdapter(
     "listDealTasksDue",
     "completeDealTask",
     "mergeEnrichmentData",
-    "upsertSocialPosts"
+    "upsertSocialPosts",
+    // Stateful trait methods added with the lead-gen substrate (touchpoint methods removed)
+    "setDealStateKey",
+    "transitionDeal",
+    "loadDeal"
   ],
   overrides
 );

package/dist/worker/index.js

@@ -4962,6 +4962,7 @@ var acqDb = createAdapter("acqDb", [
   "updateList",
   "deleteList",
   "addContactsToList",
+  "addCompaniesToList",
   "updateCompanyStage",
   "updateContactStage",
   // Company operations
@@ -5004,11 +5005,9 @@ var acqDb = createAdapter("acqDb", [
   "clearDealFields",
   "deleteDeal",
   "recordDealActivity",
-  "recordTouchpoint",
   "setDealStateKey",
   "transitionDeal",
   "loadDeal",
-  "listDealTouchpoints",
   // Deal note operations
   "createDealNote",
   "listDealNotes",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elevasis/sdk",
-  "version": "1.13.2",
+  "version": "1.14.1",
   "description": "SDK for building Elevasis organization resources",
   "type": "module",
   "bin": {
@@ -50,7 +50,7 @@
     "tsup": "^8.0.0",
     "typescript": "5.9.2",
     "zod": "^4.1.0",
-    "@repo/core": "0.13.0",
+    "@repo/core": "0.14.0",
     "@repo/typescript-config": "0.0.0"
   },
   "scripts": {

package/reference/claude-config/rules/ui.md

@@ -119,7 +119,7 @@ The API URL is centralized in `ui/src/lib/constants/api.ts`. In the current temp
 Current top-level app sections:
 
 - `/` -- host-local dashboard entrypoint with quick links derived from `organizationModel.navigation.quickAccessSurfaceIds`
-- `/lead-gen/*` -- lead generation pages (`lists`, `companies`, `contacts`)
+- `/lead-gen/*` -- lead generation pages (`lists`, `companies`, `contacts`)
 - `/crm/*` -- CRM overview, pipeline, and deals
 - `/projects/*` -- delivery feature pages (projects, milestones, tasks, notes)
 - `/operations/*` -- operations overview, resources, command queue, command view, sessions, task scheduler
@@ -193,12 +193,12 @@ Two customization layers are available for every shared feature sidebar:
 
 `manifest.sidebar` accepts any component, so arbitrary customization is always available. The `items` prop is an abstraction barrier for the common case, not a limit.
 
-See `node_modules/@elevasis/sdk/reference/scaffold/ui/customization.md` for the decision tree, page-wrapping pattern, and delivery's three-section variant. For broader CRM extension work across pages, hooks, actions, workflows, and org-model boundaries, start with `node_modules/@elevasis/sdk/reference/scaffold/recipes/extend-crm.md`. For broader lead-gen extension work across pages, hooks, list/member state, artifacts, touchpoints, workflows, and org-model boundaries, start with `node_modules/@elevasis/sdk/reference/scaffold/recipes/extend-lead-gen.md`. See `node_modules/@elevasis/sdk/reference/scaffold/reference/contracts.md` for `NavItem`, `FeatureModule`, CRM platform primitives, Lead Gen platform primitives, and related TypeScript shapes.
-
-For CRM deal action buttons, read `node_modules/@elevasis/sdk/reference/scaffold/recipes/customize-crm-actions.md` before changing `crmActions`, `DealDetailPage`, `DealDrawer`, or custom workflow buttons. Start with the shared `crmActions` provider path for action visibility, labels, ordering, and render-time configuration. In v1, platform-known/default action endpoint behavior is server-constrained; use project-owned UI that calls the workflow directly when a custom key sits outside that server-dispatched set.
-
-## Notes
-
-- `ui/src/routeTree.gen.ts` is generated by TanStack Router tooling. Do not hand-edit it.
+See `node_modules/@elevasis/sdk/reference/scaffold/ui/customization.md` for the decision tree, page-wrapping pattern, and delivery's three-section variant. For broader CRM extension work across pages, hooks, actions, workflows, and org-model boundaries, start with `node_modules/@elevasis/sdk/reference/scaffold/recipes/extend-crm.md`. For broader lead-gen extension work across pages, hooks, list/member state, artifacts, touchpoints, workflows, and org-model boundaries, start with `node_modules/@elevasis/sdk/reference/scaffold/recipes/extend-lead-gen.md`. See `node_modules/@elevasis/sdk/reference/scaffold/reference/contracts.md` for `NavItem`, `FeatureModule`, CRM platform primitives, Lead Gen platform primitives, and related TypeScript shapes.
+
+For CRM deal action buttons, read `node_modules/@elevasis/sdk/reference/scaffold/recipes/customize-crm-actions.md` before changing `crmActions`, `DealDetailPage`, `DealDrawer`, or custom workflow buttons. Start with the shared `crmActions` provider path for action visibility, labels, ordering, and render-time configuration. In v1, platform-known/default action endpoint behavior is server-constrained; use project-owned UI that calls the workflow directly when a custom key sits outside that server-dispatched set.
+
+## Notes
+
+- `ui/src/routeTree.gen.ts` is generated by TanStack Router tooling. Do not hand-edit it.
 - The template ships a broad route surface so downstream projects can trim or reshape features without having to re-derive the shared shell contract from scratch.
 - For package-export discovery, glob `node_modules/@elevasis/sdk/reference/` or `node_modules/@repo/ui/dist/` for the current SDK/UI package surface.

package/reference/claude-config/rules/vibe.md

@@ -119,17 +119,17 @@ This routing applies to both codify levels (decision #21 -- Codify ceremony dele
 - **Level A** (config-only edits to `organization-model.ts`, feature toggles, label renames): delegate to `/configure <domain>` immediately.
 - **Level B** (new Zod extension files in `foundations/config/extensions/`): also delegate to `/configure <domain>`; `/configure` gates Level B to explicit user asks before scaffolding a new TS file.
 
-Vibe detects the intent and delegates in both cases. It does not run either pipeline itself.
-
-For "build/extend the CRM" asks, classify the structural org-model portion as Codify, then read `node_modules/@elevasis/sdk/reference/scaffold/recipes/extend-crm.md` before editing. CRM work often spans org-model sales semantics, shared UI routes, hooks, workflow adapters, and deal actions; do not reduce it to only `sales` config or only UI.
-
-For "build/extend lead gen" / "campaign creator" / "outbound list state" asks, classify the structural org-model portion as Codify, then read `node_modules/@elevasis/sdk/reference/scaffold/recipes/extend-lead-gen.md` before editing. Lead-gen work often spans org-model prospecting semantics, shared UI routes, hooks, list/member state, artifacts, touchpoints, and workflow adapters; do not reduce it to only `prospecting` config or only UI.
-
-For "add a custom CRM action" / "Send Quote button" asks, classify as Codify, then read `node_modules/@elevasis/sdk/reference/scaffold/recipes/customize-crm-actions.md` before editing. Start with the shared `crmActions` provider path for action visibility, labels, ordering, and render-time configuration. In v1, platform-known/default action endpoint behavior is server-constrained; use project-owned UI that calls the workflow directly when a custom key sits outside that server-dispatched set.
-
-Heuristics for when to propose codification (passed to `/configure` as context):
-
-- First mention of a new attribute: note to `resume_context`, do not propose yet
+Vibe detects the intent and delegates in both cases. It does not run either pipeline itself.
+
+For "build/extend the CRM" asks, classify the structural org-model portion as Codify, then read `node_modules/@elevasis/sdk/reference/scaffold/recipes/extend-crm.md` before editing. CRM work often spans org-model sales semantics, shared UI routes, hooks, workflow adapters, and deal actions; do not reduce it to only `sales` config or only UI.
+
+For "build/extend lead gen" / "campaign creator" / "outbound list state" asks, classify the structural org-model portion as Codify, then read `node_modules/@elevasis/sdk/reference/scaffold/recipes/extend-lead-gen.md` before editing. Lead-gen work often spans org-model prospecting semantics, shared UI routes, hooks, list/member state, artifacts, touchpoints, and workflow adapters; do not reduce it to only `prospecting` config or only UI.
+
+For "add a custom CRM action" / "Send Quote button" asks, classify as Codify, then read `node_modules/@elevasis/sdk/reference/scaffold/recipes/customize-crm-actions.md` before editing. Start with the shared `crmActions` provider path for action visibility, labels, ordering, and render-time configuration. In v1, platform-known/default action endpoint behavior is server-constrained; use project-owned UI that calls the workflow directly when a custom key sits outside that server-dispatched set.
+
+Heuristics for when to propose codification (passed to `/configure` as context):
+
+- First mention of a new attribute: note to `resume_context`, do not propose yet
 - Second mention OR explicit declaration ("we're ecom"): propose extension
 - Explicit ask ("track ecom deals separately"): propose immediately with fuller scope
 - Attribute appearing across 3+ tasks: propose adding field to existing extension

package/reference/scaffold/index.mdx

@@ -21,14 +21,14 @@ This scaffold reference contains universal documentation that applies to all Ele
 ### Pathway Recipes
 
 - [Add a Feature](./recipes/add-a-feature.md) -- end-to-end from org model key through manifest, routes, gating
-- [Add a Resource](./recipes/add-a-resource.md) -- author and deploy a workflow or agent
-- [Extend a Base Entity](./recipes/extend-a-base-entity.md) -- add project-specific metadata to canonical entity shapes via the TMeta slot
-- [Gate by Feature or Admin](./recipes/gate-by-feature-or-admin.md) -- decision table for access control patterns
-- [Build and Extend CRM](./recipes/extend-crm.md) -- map CRM UI pages, hooks, actions, workflow adapters, contracts, and org-model boundaries
-- [Build and Extend Lead Gen](./recipes/extend-lead-gen.md) -- map lead-gen UI pages, hooks, list/member state, artifacts, touchpoints, workflow adapters, contracts, and org-model boundaries
-- [Customize CRM Actions](./recipes/customize-crm-actions.md) -- add, hide, or replace CRM deal actions, use the shared `crmActions` provider path, and understand workflow dispatch constraints
-
-### UI Patterns
+- [Add a Resource](./recipes/add-a-resource.md) -- author and deploy a workflow or agent
+- [Extend a Base Entity](./recipes/extend-a-base-entity.md) -- add project-specific metadata to canonical entity shapes via the TMeta slot
+- [Gate by Feature or Admin](./recipes/gate-by-feature-or-admin.md) -- decision table for access control patterns
+- [Build and Extend CRM](./recipes/extend-crm.md) -- map CRM UI pages, hooks, actions, workflow adapters, contracts, and org-model boundaries
+- [Build and Extend Lead Gen](./recipes/extend-lead-gen.md) -- map lead-gen UI pages, hooks, list/member state, artifacts, touchpoints, workflow adapters, contracts, and org-model boundaries
+- [Customize CRM Actions](./recipes/customize-crm-actions.md) -- add, hide, or replace CRM deal actions, use the shared `crmActions` provider path, and understand workflow dispatch constraints
+
+### UI Patterns
 
 - [UI Recipes](./ui/recipes.md) -- copy-paste recipes for pages, nav items, components, theme tokens
 - [Feature Flags & Gating](./ui/feature-flags-and-gating.md) -- three-concept model for feature access