@elevasis/sdk 1.18.0 → 1.19.0

package/dist/worker/index.js

@@ -4742,6 +4742,63 @@ z.object({
   defaultPipelineId: ModelIdSchema,
   pipelines: z.array(SalesPipelineSchema).min(1)
 });
+var CRM_DISCOVERY_REPLIED_STATE = {
+  stateKey: "discovery_replied",
+  label: "Discovery Replied"
+};
+var CRM_DISCOVERY_LINK_SENT_STATE = {
+  stateKey: "discovery_link_sent",
+  label: "Discovery Link Sent"
+};
+var CRM_DISCOVERY_NUDGING_STATE = {
+  stateKey: "discovery_nudging",
+  label: "Discovery Nudging"
+};
+var CRM_DISCOVERY_BOOKING_CANCELLED_STATE = {
+  stateKey: "discovery_booking_cancelled",
+  label: "Discovery Booking Cancelled"
+};
+var CRM_REPLY_SENT_STATE = {
+  stateKey: "reply_sent",
+  label: "Reply Sent"
+};
+var CRM_FOLLOWUP_1_SENT_STATE = {
+  stateKey: "followup_1_sent",
+  label: "Follow-up 1 Sent"
+};
+var CRM_FOLLOWUP_2_SENT_STATE = {
+  stateKey: "followup_2_sent",
+  label: "Follow-up 2 Sent"
+};
+var CRM_FOLLOWUP_3_SENT_STATE = {
+  stateKey: "followup_3_sent",
+  label: "Follow-up 3 Sent"
+};
+var CRM_PIPELINE_DEFINITION = {
+  pipelineKey: "crm",
+  stages: [
+    {
+      stageKey: "interested",
+      label: "Interested",
+      color: "blue",
+      states: [
+        CRM_DISCOVERY_REPLIED_STATE,
+        CRM_DISCOVERY_LINK_SENT_STATE,
+        CRM_DISCOVERY_NUDGING_STATE,
+        CRM_DISCOVERY_BOOKING_CANCELLED_STATE,
+        CRM_REPLY_SENT_STATE,
+        CRM_FOLLOWUP_1_SENT_STATE,
+        CRM_FOLLOWUP_2_SENT_STATE,
+        CRM_FOLLOWUP_3_SENT_STATE
+      ]
+    },
+    { stageKey: "proposal", label: "Proposal", color: "yellow", states: [] },
+    { stageKey: "closing", label: "Closing", color: "orange", states: [] },
+    { stageKey: "closed_won", label: "Closed Won", color: "green", states: [] },
+    { stageKey: "closed_lost", label: "Closed Lost", color: "red", states: [] },
+    { stageKey: "nurturing", label: "Nurturing", color: "grape", states: [] }
+  ]
+};
 var LEAD_GEN_STAGE_CATALOG = {
   // Prospecting — company population
   scraped: {
@@ -4849,20 +4906,86 @@ var ProspectingBuildTemplateSchema = DisplayMetadataSchema.extend({
   id: ModelIdSchema,
   steps: z.array(ProspectingBuildTemplateStepSchema).min(1)
 });
-var CAPABILITY_REGISTRY = {
-  "lead-gen.company.source": "lgn-import-workflow",
-  "lead-gen.company.apollo-import": "lgn-01c-apollo-import-workflow",
-  "lead-gen.contact.discover": "lgn-04-email-discovery-workflow",
-  "lead-gen.contact.verify-email": "lgn-05-email-verification-workflow",
-  "lead-gen.company.website-extract": "lgn-02-website-extract-workflow",
-  "lead-gen.company.qualify": "lgn-03-company-qualification-workflow",
-  "lead-gen.company.dtc-subscription-qualify": "lgn-03b-dtc-subscription-score-workflow",
-  "lead-gen.contact.apollo-decision-maker-enrich": "lgn-04b-apollo-decision-maker-enrich-workflow",
-  "lead-gen.contact.personalize": "ist-personalization-workflow",
-  "lead-gen.review.outreach-ready": "ist-upload-contacts-workflow",
-  "lead-gen.export.list": "lgn-06-export-list-workflow",
-  "lead-gen.company.cleanup": "lgn-company-cleanup-workflow"
-};
+z.object({
+  id: ModelIdSchema,
+  label: z.string(),
+  description: z.string(),
+  resourceId: ModelIdSchema
+});
+var CAPABILITY_REGISTRY = [
+  {
+    id: "lead-gen.company.source",
+    label: "Source companies",
+    description: "Import source companies from a list provider.",
+    resourceId: "lgn-import-workflow"
+  },
+  {
+    id: "lead-gen.company.apollo-import",
+    label: "Import from Apollo",
+    description: "Pull companies and seed contact data from an Apollo search or list.",
+    resourceId: "lgn-01c-apollo-import-workflow"
+  },
+  {
+    id: "lead-gen.contact.discover",
+    label: "Discover contact emails",
+    description: "Find email addresses for contacts at qualified companies.",
+    resourceId: "lgn-04-email-discovery-workflow"
+  },
+  {
+    id: "lead-gen.contact.verify-email",
+    label: "Verify emails",
+    description: "Check email deliverability before outreach.",
+    resourceId: "lgn-05-email-verification-workflow"
+  },
+  {
+    id: "lead-gen.company.website-extract",
+    label: "Extract website signals",
+    description: "Scrape and analyze company websites for qualification signals.",
+    resourceId: "lgn-02-website-extract-workflow"
+  },
+  {
+    id: "lead-gen.company.qualify",
+    label: "Qualify companies",
+    description: "Score and filter companies against the ICP rubric.",
+    resourceId: "lgn-03-company-qualification-workflow"
+  },
+  {
+    id: "lead-gen.company.dtc-subscription-qualify",
+    label: "Qualify DTC subscription fit",
+    description: "Classify subscription potential and consumable-product fit for DTC brands.",
+    resourceId: "lgn-03b-dtc-subscription-score-workflow"
+  },
+  {
+    id: "lead-gen.contact.apollo-decision-maker-enrich",
+    label: "Enrich decision-makers",
+    description: "Find and enrich qualified contacts at qualified companies via Apollo.",
+    resourceId: "lgn-04b-apollo-decision-maker-enrich-workflow"
+  },
+  {
+    id: "lead-gen.contact.personalize",
+    label: "Personalize outreach",
+    description: "Generate personalized opening lines for each contact.",
+    resourceId: "ist-personalization-workflow"
+  },
+  {
+    id: "lead-gen.review.outreach-ready",
+    label: "Upload to outreach",
+    description: "Upload approved contacts to the outreach sequence after QC review.",
+    resourceId: "ist-upload-contacts-workflow"
+  },
+  {
+    id: "lead-gen.export.list",
+    label: "Export lead list",
+    description: "Export approved leads as a downloadable lead list.",
+    resourceId: "lgn-06-export-list-workflow"
+  },
+  {
+    id: "lead-gen.company.cleanup",
+    label: "Clean up companies",
+    description: "Remove disqualified or duplicate companies from the list.",
+    resourceId: "lgn-company-cleanup-workflow"
+  }
+];
 var PROSPECTING_STEPS = {
   localServices: {
     sourceCompanies: {
@@ -5098,9 +5221,13 @@ var ProcessingStageStatusSchema = z.enum(["success", "no_result", "skipped", "er
 var LeadGenStageKeySchema = z.string().refine((value) => Object.prototype.hasOwnProperty.call(LEAD_GEN_STAGE_CATALOG, value), {
   message: "processing state key must match LEAD_GEN_STAGE_CATALOG"
 });
-var LeadGenCapabilityKeySchema = z.string().refine((value) => Object.prototype.hasOwnProperty.call(CAPABILITY_REGISTRY, value), {
+var LeadGenCapabilityKeySchema = z.string().refine((value) => CAPABILITY_REGISTRY.some((c) => c.id === value), {
   message: "capabilityKey must match CAPABILITY_REGISTRY"
 });
+var crmStageKeys = CRM_PIPELINE_DEFINITION.stages.map((stage) => stage.stageKey);
+var crmStateKeys = CRM_PIPELINE_DEFINITION.stages.flatMap((stage) => stage.states.map((state) => state.stateKey));
+var CrmStageKeySchema = z.enum(crmStageKeys);
+var CrmStateKeySchema = z.enum(crmStateKeys);
 var ProcessingStateEntrySchema = z.object({
   status: ProcessingStageStatusSchema,
   data: z.unknown().optional()
@@ -5108,7 +5235,7 @@ var ProcessingStateEntrySchema = z.object({
 var ProcessingStateSchema = z.record(LeadGenStageKeySchema, ProcessingStateEntrySchema);
 var CompanyProcessingStateSchema = ProcessingStateSchema;
 var ContactProcessingStateSchema = ProcessingStateSchema;
-var DealStageSchema = z.enum(["interested", "proposal", "closing", "closed_won", "closed_lost", "nurturing"]);
+var DealStageSchema = CrmStageKeySchema;
 var AcqDealTaskKindSchema = z.enum(["call", "email", "meeting", "other"]);
 z.object({
   dealId: UuidSchema
@@ -5144,12 +5271,19 @@ z.object({
 z.object({
   pipelineKey: z.string().min(1),
   stageKey: z.string().min(1),
-  stateKey: z.string().nullable().optional(),
+  stateKey: z.string().min(1).nullable().optional(),
+  reason: z.string().optional(),
+  expectedUpdatedAt: z.string().datetime().optional()
+}).strict();
+z.object({
+  pipelineKey: z.literal(CRM_PIPELINE_DEFINITION.pipelineKey),
+  stageKey: CrmStageKeySchema,
+  stateKey: CrmStateKeySchema.nullable().optional(),
   reason: z.string().optional(),
   expectedUpdatedAt: z.string().datetime().optional()
 }).strict();
 z.object({
-  stateKey: z.string().min(1),
+  stateKey: CrmStateKeySchema,
   reason: z.string().optional(),
   expectedUpdatedAt: z.string().datetime().optional()
 }).strict();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elevasis/sdk",
-  "version": "1.18.0",
+  "version": "1.19.0",
   "description": "SDK for building Elevasis organization resources",
   "type": "module",
   "bin": {
@@ -57,7 +57,7 @@
     "tsup": "^8.0.0",
     "typescript": "5.9.2",
     "zod": "^4.1.0",
-    "@repo/core": "0.19.0",
+    "@repo/core": "0.20.0",
     "@repo/eslint-config": "0.0.0",
     "@repo/typescript-config": "0.0.0"
   },

package/reference/claude-config/registries/graph-skills.json

@@ -0,0 +1,4 @@
+{
+  "generatedBy": "generate-knowledge-nodes",
+  "domains": {}
+}

package/reference/claude-config/skills/knowledge/SKILL.md

@@ -131,9 +131,9 @@ through `/knowledge`; do not point them at monorepo-only commands.
 ```bash
 pnpm exec elevasis knowledge:ls
 pnpm exec elevasis knowledge:cat <node-id>
-pnpm exec elevasis knowledge:graph --axis by-feature
-pnpm exec elevasis knowledge:graph --axis by-domain
-pnpm exec elevasis knowledge:graph --mount <mount-id>
+pnpm exec elevasis knowledge:ls /by-feature/<feature-id>
+pnpm exec elevasis knowledge:ls /by-owner/<owner-id>
+pnpm exec elevasis knowledge:graph <node-id>
 ```
 
 ### External projects (org instance)
@@ -141,14 +141,15 @@ pnpm exec elevasis knowledge:graph --mount <mount-id>
 ```bash
 pnpm exec elevasis-sdk knowledge:ls
 pnpm exec elevasis-sdk knowledge:cat <node-id>
-pnpm exec elevasis-sdk knowledge:graph --axis by-feature
-pnpm exec elevasis-sdk knowledge:graph --axis by-domain
-pnpm exec elevasis-sdk knowledge:graph --mount <mount-id>
+pnpm exec elevasis-sdk knowledge:ls /by-feature/<feature-id>
+pnpm exec elevasis-sdk knowledge:ls /by-owner/<owner-id>
+pnpm exec elevasis-sdk knowledge:graph <node-id>
 ```
 
 Use `knowledge:ls` to enumerate all knowledge nodes. Use `knowledge:cat` to read a specific
-node's content. Use `knowledge:graph` to navigate the governance graph -- `by-feature` is the
-default axis for "what governs X?" queries; `by-domain` for domain-wide surveys.
+node's content. Use `knowledge:ls /by-feature/<feature-id>` or
+`knowledge:ls /by-owner/<owner-id>` to navigate feature and owner groupings. Use
+`knowledge:graph <node-id>` to inspect incoming and outgoing graph edges for a specific node.
 
 ### `/knowledge read-folder` (chat shorthand from the Knowledge Browser)
 

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

@@ -570,12 +570,12 @@ the user what happens if they omit the `default` route (runtime failure for unma
 
 ### Item 8: Going to production
 
-**Goal:** The user knows the dev/prod split, version bumping flags, and the `cli-cwd-invariant`
-rule for `--prod` flag placement.
+**Goal:** The user knows the dev/prod split, version bumping flags, and the SDK CLI CWD
+guidance in the deployment rule.
 
 **Estimated time:** 15 min
 
-**Files referenced:** `.claude/rules/deployment.md`, `.claude/rules/cli-cwd-invariant.md`
+**Files referenced:** `.claude/rules/deployment.md`
 
 **Commands:** `pnpm -C operations deploy:prod`
 
@@ -606,19 +606,17 @@ pnpm elevasis-sdk deploy --prod --major   # 1.0.0 -> 2.0.0
 Bump rules: `--patch` for bug fixes, `--minor` for new features (no breaking schema changes),
 `--major` for breaking input/output schema changes.
 
-**The `cli-cwd-invariant`.** Read `.claude/rules/cli-cwd-invariant.md`. Two critical rules:
+**SDK CLI CWD guidance.** Read `.claude/rules/deployment.md`. Two critical rules:
 
-1. The `--prod` flag on the `elevasis-sdk` binary MUST come before the subcommand name:
+1. The `--prod` flag belongs to the `deploy` command:
 
    ```bash
    # Correct
-   pnpm elevasis-sdk --prod deploy
-   # Wrong -- --prod after deploy is silently ignored
    pnpm elevasis-sdk deploy --prod
    ```
 
    The `pnpm -C operations deploy:prod` script in `package.json` handles this correctly.
-   Prefer the script over a raw CLI call to avoid the pitfall.
+   Prefer the script over a raw CLI call for production deploys.
 
 2. Never use bare `cd <dir> && elevasis-sdk ...` -- use a subshell `(cd <dir> && ...)` or
    `pnpm -C <dir> ...` to avoid CWD drift that causes env resolution failures.

package/reference/claude-config/sync-notes/2026-05-06-crm-spine.md

@@ -0,0 +1,60 @@
+# 2026-05-06 -- CRM OM Spine Migration
+
+## Why this note exists
+
+The CRM deal vocabulary (`stage_key`, `state_key`, `pipeline_key`) is now a fully-realized OM Spine matching the lead-gen list-builder pattern. `CRM_PIPELINE_DEFINITION` becomes the single source of truth: `@elevasis/core` derives `CrmStageKeySchema` and `CrmStateKeySchema` from the catalog, the catalog gains optional `color?` metadata on each stage, and `@elevasis/sdk` re-exports both schemas plus the catalog so external SDK consumers see the same vocabulary as monorepo callers. `@elevasis/ui` rewires the CRM page helpers (`DEAL_STAGE_COLORS`, `DEAL_STAGE_OPTIONS`, `formatDealStageLabel`, `formatDealStateLabel`) to read from the catalog instead of hardcoded maps -- public exports are preserved, behavior is now catalog-driven.
+
+The platform side also closed a long-standing data drift: `pipeline_key='default'` in `acq_deals` is gone; live writers now use `pipeline_key='crm'` matching the catalog's `pipelineKey: 'crm'`. The Elevasis backfill applied directly to prod and dev on 2026-05-06; tenant deal rows are not affected by that backfill and continue to use whatever value tenant code wrote.
+
+## Applies to
+
+- All template-derived projects that consume `@elevasis/core`, `@elevasis/ui`, or `@elevasis/sdk`.
+- Projects that customize CRM stages or states in `core/config/organization-model.ts` under the `sales` domain.
+- Projects that read or write CRM transitions through `@elevasis/sdk` worker adapters (`acqDb.transitionDeal`, `acqDb.transitionItem`).
+- Projects that render CRM pipeline UI from `@elevasis/ui/features/crm`.
+
+## Required actions
+
+1. Pull synced template package baselines through `/git-sync`:
+   - `core/package.json`: `@elevasis/core` -> 0.20.0
+   - `ui/package.json`: `@elevasis/ui` -> 2.29.0
+   - `operations/package.json`: `@elevasis/core` -> 0.20.0 and `@elevasis/sdk` -> 1.19.0
+
+2. Run `pnpm install` and rebuild the project:
+
+   ```bash
+   pnpm install
+   pnpm -C ui build
+   pnpm -C ui exec tsc --noEmit
+   pnpm -C operations exec tsc --noEmit
+   ```
+
+3. **Optional: adopt `color?` on customized CRM stages.** If `core/config/organization-model.ts` overrides `sales.stages` with custom labels, you may now add an optional `color` field per stage (any Mantine palette key: `blue`, `yellow`, `orange`, `green`, `red`, `grape`, etc.). The shipped `DEAL_STAGE_COLORS` map and CRM kanban UI will read it. Stages without a `color` fall back to the platform default mapping in the catalog.
+
+4. **Optional: tighten project-owned CRM workflow inputs.** New schemas are available from `@elevasis/sdk`:
+
+   ```ts
+   import { CrmStageKeySchema, CrmStateKeySchema, CRM_PIPELINE_DEFINITION } from '@elevasis/sdk'
+   ```
+
+   Project-authored CRM action workflows that previously used `z.string()` for `toStage` / `toState` can now validate against the catalog-derived enum. The `transitionItem` / `transitionDeal` worker adapters still accept strings, but unknown stage/state keys are rejected at the platform writer layer for `pipelineKey: 'crm'` writers.
+
+5. **No tenant data backfill required.** The `pipeline_key='default'` -> `'crm'` backfill was applied to Elevasis databases only. Tenant `acq_deals` rows are unaffected. If tenant code writes `pipelineKey: 'default'` to `acqDb.transitionDeal`, that behavior is unchanged; only the published catalog declares `'crm'` as canonical and the published schemas validate `'crm'` exclusively for CRM-shaped transitions.
+
+## Verification
+
+After applying the actions above:
+
+- `pnpm -C ui check-types`
+- `pnpm -C ui build`
+- `pnpm -C ui test`
+- `pnpm -C operations check`
+- `pnpm -C operations check-types`
+- `pnpm -C operations test`
+- Browser smoke: open `/crm/pipeline` (or the project's CRM kanban surface) and verify stage labels and column colors render from the catalog. Custom-labeled stages should show the override label; default stages show the platform palette.
+
+## Not handled by /git-sync
+
+- **Tenant CRM action workflows.** If a project authored its own CRM action workflows in `operations/` that import `transitionDeal` / `syncDealStateKeyToDb` directly (rather than `emitCrmTransition`), `/git-sync` does NOT refactor them. The platform-side `emitCrmTransition` factory is internal to `@repo/elevasis-operations` (workspace-internal) and is not part of the published SDK surface. Project-owned workflows continue to call the worker adapters directly; the new validation guard rejects unknown stage/state keys but does not require migration.
+- **Customized stage colors.** Existing tenant overrides under `sales.stages[].label` and `sales.stages[].states[]` continue to work unchanged. Adopting the new optional `color` field is a project-by-project decision; `/git-sync` will not infer colors for custom stages.
+- **`pipeline_key` data in tenant databases.** If a project has historic `acq_deals` rows with `pipeline_key='default'` and wants to align with the new canonical `'crm'` identity, that is a tenant-managed migration -- not part of this train.

package/reference/scaffold/reference/contracts.md

@@ -1126,7 +1126,7 @@ export const DEFAULT_CRM_PRIORITY_RULE_CONFIG: CrmPriorityRuleConfig = {
 ### `DealStageSchema`
 
 ```typescript
-export const DealStageSchema = z.enum(['interested', 'proposal', 'closing', 'closed_won', 'closed_lost', 'nurturing'])
+export const DealStageSchema = CrmStageKeySchema
 ```
 
 ### `AcqDealTaskKindSchema`
@@ -1218,7 +1218,7 @@ export const TransitionItemRequestSchema = z
   .object({
     pipelineKey: z.string().min(1),
     stageKey: z.string().min(1),
-    stateKey: z.string().nullable().optional(),
+    stateKey: z.string().min(1).nullable().optional(),
     reason: z.string().optional(),
     expectedUpdatedAt: z.string().datetime().optional()
   })
@@ -1412,6 +1412,11 @@ export const DealTaskListResponseSchema = z.array(DealTaskResponseSchema)
 
 ```typescript
 export const DealSchemas = {
+  // Primitives
+  CrmStageKey: CrmStageKeySchema,
+  CrmStateKey: CrmStateKeySchema,
+  DealStage: DealStageSchema,
+
   // Params
   DealIdParams: DealIdParamsSchema,
   DealTaskIdParams: DealTaskIdParamsSchema,
@@ -1424,7 +1429,7 @@ export const DealSchemas = {
   // Request bodies
   CreateDealNoteRequest: CreateDealNoteRequestSchema,
   CreateDealTaskRequest: CreateDealTaskRequestSchema,
-  TransitionItemRequest: TransitionItemRequestSchema,
+  TransitionItemRequest: CrmTransitionItemRequestSchema,
   TransitionDealStateRequest: TransitionDealStateRequestSchema,
   ExecuteActionParams: ExecuteActionParamsSchema,
   ExecuteActionRequest: ExecuteActionRequestSchema,
@@ -2555,7 +2560,7 @@ export const AcqSubstrateSchemas = {
   ListCompanyIdParams: ListCompanyIdParamsSchema,
   AcqListCompanyResponse: AcqListCompanyResponseSchema,
 
-  // Transition (shared with deals — TransitionItemRequestSchema)
+  // Transition (generic stateful substrate)
   TransitionItemRequest: TransitionItemRequestSchema
 }
 ```
@@ -2623,6 +2628,8 @@ export interface StatefulStageDefinition {
   /** Matches stage_key values written by workflow steps. */
   stageKey: string
   label: string
+  /** UI color token. Consumers may map this to their design system. */
+  color?: string
   states: StatefulStateDefinition[]
 }
 ```