@elevasis/sdk 1.17.0 → 1.18.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elevasis/sdk",
-  "version": "1.17.0",
+  "version": "1.18.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.17.0",
+    "@repo/core": "0.19.0",
     "@repo/eslint-config": "0.0.0",
     "@repo/typescript-config": "0.0.0"
   },

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

@@ -0,0 +1,33 @@
+# Package Taxonomy (Consumer View)
+
+External projects consume the **published `@elevasis/*` surface only**. The Elevasis monorepo also has workspace-internal `@repo/elevasis-*` packages — those are NOT installable here and should never appear in your imports or `package.json`.
+
+## What You Can Import
+
+| Package          | Subpaths                                     | Where it lives in `node_modules` |
+| ---------------- | -------------------------------------------- | -------------------------------- |
+| `@elevasis/sdk`  | default, `/worker`, `/node`, `/test-utils`   | `node_modules/@elevasis/sdk/`    |
+| `@elevasis/ui`   | default, `/auth`, `/initialization`, etc.    | `node_modules/@elevasis/ui/`     |
+| `@elevasis/core` | `/organization-model`, `/entities`, `/utils` | `node_modules/@elevasis/core/`   |
+
+## What You Will See in Monorepo Docs (and should NOT import)
+
+Monorepo source and docs reference `@repo/elevasis-core` and `@repo/elevasis-operations`. These are workspace-internal packages used by Elevasis as a tenant of its own platform. They are `private: true` and never published. If you see them mentioned:
+
+- Do NOT add them to this project's `package.json`
+- Do NOT try to import from them — they are not in your `node_modules`
+- They are not a substitute for `@elevasis/core` even though the name overlaps
+
+## Confused About Where Something Lives?
+
+Check the import path:
+
+- `@elevasis/...` → published, consumable here
+- `@repo/...` → monorepo-internal, not consumable
+
+This project's own org-model and workflows live in `core/config/organization-model.ts` and `operations/src/**` — those are project-owned, not part of either family above.
+
+## References
+
+- `node_modules/@elevasis/sdk/reference/scaffold/index.mdx` — full SDK scaffold reference
+- Monorepo source rule: `.claude/rules/package-taxonomy.md` in the elevasis-monorepo (when working across both)

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

@@ -66,6 +66,17 @@ The user wants the agent to explain something -- a scope, an entity, a concept w
 
 **Agent action:** read the relevant org-model label, entity, or scope. Narrate in plain language using label fields from the model -- never invent vocabulary not present in the model. Phase-1 scope covers Model, Features, and Foundations layers only.
 
+**Stage/state/catalog sub-routing:** when the noun being described is a stage, state, status
+bucket, catalog entry, progress step, pipeline column, or similarly closed business vocabulary,
+also show the cross-system impact before the normal description:
+
+1. Read `node_modules/@elevasis/sdk/reference/spine/spine-primer.md` for the layering pattern.
+2. Read the relevant domain in `foundations/config/organization-model.ts`.
+3. Explain the impact in vibe-coder language only: the business profile entry, the saved progress
+   on each record, the automations that produce updates, and the dashboard or reports that read it.
+4. Route follow-up changes through `/knowledge <domain>`. Do not mention the technical pattern name
+   unless the user explicitly asks for internals.
+
 ### 4. Transition
 
 The user wants to change the status of a task or entity.
@@ -114,6 +125,18 @@ The user describes organizational reality that is not yet expressed in the model
 
 **Agent action:** delegate immediately to `/knowledge`. Do not attempt the ceremony yourself. Invoke with the relevant domain: `/knowledge crm` for deal/contact changes, `/knowledge projects` for project types, `/knowledge features` for feature toggles. Plain-language summary of what was detected is acceptable before delegating, but the actual draft-confirm-write ceremony belongs to `/knowledge`.
 
+**Stage/state/catalog impact preview:** if the Codify intent adds, renames, removes, reorders, or
+re-scopes a stage, state, status bucket, catalog member, pipeline step, or progress vocabulary,
+preview the cross-system impact before delegating:
+
+- Which business-profile entry changes.
+- Which saved record progress keys may already exist.
+- Which automations or templates reference the key.
+- Which dashboard, report, queue, or API reads may display or filter by it.
+
+Then delegate to `/knowledge <domain>` with that preview as context. Vibe does not write the
+change and does not expose monorepo-only commands.
+
 This routing applies to both codify levels (decision #21 -- Codify ceremony delegated to `/knowledge`):
 
 - **Level A** (config-only edits to `organization-model.ts`, feature toggles, label renames): delegate to `/knowledge <domain>` immediately.

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

@@ -92,11 +92,38 @@ cannot bypass the write gate.
 | Read     | "what playbooks govern sales.crm?", "show me all reference docs", "list my roles"  | Run CLI read commands (monorepo or external); format result                                                   |
 | Navigate | "what governs this feature?", "where does outreach-cadence apply?"                 | Same CLI; pick mount axis from intent; default to `by-feature` for orientation queries                        |
 | Describe | "what is our identity set to?", "what's our timezone?"                             | Read current values from OM source; narrate                                                                   |
-| Codify   | "we're an e-commerce company", "add a customer segment", "our outreach goal is..." | Run codify ceremony: snapshot -> propose -> confirm -> write -> typecheck -> Zod parse -> rollback on failure |
+| Codify   | "we're an e-commerce company", "add a customer segment", "our outreach goal is..." | Run codify ceremony with shared-layer impact preview: snapshot -> propose -> confirm -> write -> typecheck -> Zod parse -> rollback on failure |
 | Toggle   | "enable the lead-gen feature", "turn off SEO"                                      | Codify ceremony scoped to `features` domain; flip the boolean; same validation/rollback                       |
 
 ---
 
+## Shared Layering Preview
+
+When opening a domain that uses a closed stage, status, or catalog vocabulary -- especially
+prospecting, CRM, outreach, or another pipeline-like domain -- read the scaffold-shipped primer:
+
+```bash
+node_modules/@elevasis/sdk/reference/spine/spine-primer.md
+```
+
+Use it to emit a short domain layering preview before the normal read, describe, or codify flow:
+
+1. **Catalog:** which `organizationModel.<domain>` catalog owns the keys, labels, descriptions,
+   ordering, and entity ownership.
+2. **Runtime state:** where record progress is stored as sparse state keyed by those catalog
+   members.
+3. **Producers:** which templates, automations, or factories write entity-tagged results for those
+   keys.
+4. **Consumers:** which dashboards, queues, reports, filters, or API reads render or aggregate the
+   same keys.
+
+For vibe-coder sessions, translate this into plain language: "business profile", "saved progress",
+"automations", and "dashboard or reports". For technical sessions, it is acceptable to name the
+catalog, state map, producer, and consumer surfaces directly. External tenants route all follow-ups
+through `/knowledge`; do not point them at monorepo-only commands.
+
+---
+
 ## Read Patterns
 
 ### Monorepo (platform defaults)
@@ -156,6 +183,12 @@ Read `foundations/config/organization-model.ts` (external) or the appropriate pl
 Show the diff in chat. Identify which domain and field changes. Present the proposed new value
 in context alongside the current value.
 
+For stage, status, or catalog vocabulary edits, include the shared-layer impact preview before
+asking for confirmation. Name the affected catalog key, whether existing sparse runtime state may
+contain the old key, which producers/templates reference it, and which consumers render or filter by
+it. If the impact cannot be determined from the local project, say which surface is unknown and keep
+the write gated.
+
 ### Step 3: Confirm
 
 Pause for explicit user confirmation. Do not proceed without a clear yes. Permission prompts
@@ -240,13 +273,12 @@ Cross-link: `.claude/skills/knowledge/SKILL.md` (monorepo pointer)
 
 ## Cross-Links
 
-- `/org-os` -- Organization OS architecture overview, seven layers, propagation pipeline,
-  feature/surface management. Use `/org-os` when the question is about the architecture or
-  propagation system rather than reading or editing org-model values. Cross-link:
-  `.claude/skills/org-os/SKILL.md`
 - `/configure` -- Legacy org-model editor (pre-absorption). Absorbed into this skill; all
   Codify and Toggle intents now route here. `/configure` vocabulary still works as a domain
   hint (e.g., "configure identity" is parsed as domain=identity, intent=Describe-or-Codify).
+- `node_modules/@elevasis/sdk/reference/spine/spine-primer.md` -- Scaffold-shipped layering
+  primer for stage/status/catalog vocabularies that coordinate business-profile entries, runtime
+  progress, producers, and consumers in tenant projects.
 
 ---
 

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

@@ -399,6 +399,27 @@ Recent Notes
   2026-04-01 [call_note] Kickoff — confirmed scope and timeline
 ```
 
+#### Tenant Skill Bindings Footer
+
+After the normal status output, append a short footer when the project kind, tags, name,
+description, milestones, or active tasks map to a known tenant domain such as `prospecting`,
+`crm`, `outreach`, `finance`, or `support`.
+
+Resolve the best domain from explicit metadata first (`tags`, `kind`, domain fields), then from
+project/task text. If no clear domain maps, omit the footer.
+
+Footer shape:
+
+```text
+Related skill bindings
+- Domain: <domain>
+- Read or change business profile: /knowledge <domain>
+- Layering primer: node_modules/@elevasis/sdk/reference/spine/spine-primer.md
+```
+
+External projects do not expose monorepo-only architecture commands. Never suggest `/org-os`,
+`/om-spine`, or monorepo paths in this footer.
+
 ### `create` — Guided Project Creation (QnA Flow)
 
 Interactive walkthrough that collects project details step by step using `AskUserQuestion`,

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

@@ -29,6 +29,15 @@ This router does not enforce that tone -- it only writes profile.md and loads th
 file. The project-wide tone effect is handled by the rules layer reading profile.md on each
 session start.
 
+Track separation is explicit:
+
+- The vibe-coder track teaches the underlying coordination idea through business language only:
+  business profile, saved progress, automations, dashboard, and reports. Do not name the technical
+  pattern in vibe-coder menus, lessons, prompts, or progress labels.
+- The technical track may name OM spine vocabulary and can point developers at
+  `node_modules/@elevasis/sdk/reference/spine/spine-primer.md` when lessons discuss shared stage,
+  status, or catalog vocabularies.
+
 ---
 
 ## Step 1: Parse the Argument
@@ -111,8 +120,9 @@ In this project, always:
 
 ## Tone Implications
 
-Code-first communication. Use current command names and SDK terminology without hand-holding.
-No vocabulary substitutions. Slash commands may be surfaced directly. Full technical depth.
+Code-first communication. Use current command names, SDK terminology, and OM spine vocabulary
+without hand-holding. No vocabulary substitutions. Slash commands may be surfaced directly. Full
+technical depth.
 ```
 
 ### Initialize Progress File
@@ -156,7 +166,7 @@ Read `.claude/memory/tutorial-progress.md`.
 - [ ] 15 Error handling
 - [ ] 16 LLM and agents
 - [ ] 17 Composition
-- [ ] 18 Rules, memory, scaffold registry
+- [ ] 18 Rules, memory, scaffold registry, OM spine
 - [ ] 19 Template lifecycle and /git-sync
 ```
 

package/reference/claude-config/sync-notes/2026-05-05-list-builder.md

@@ -0,0 +1,42 @@
+# 2026-05-05 — List Builder UX + Schema-Driven Step Config
+
+## Why this note exists
+
+The list-builder ship train publishes a coordinated `@elevasis/core` + `@elevasis/ui` release that:
+
+- Replaces every per-integration bespoke step-config component (and the `SerializedExecutionFormSchema` middle tier) with one generic `<StepConfigForm>` driven by the workflow's `contract.inputSchema` (Zod) plus a small `StepConfigLayout` hints object per integration.
+- Standardizes the BuildTab step-detail right column on a `Configuration | Advanced | Runs` tab shell (`StepDetailRightColumn`).
+- Makes `schema + layout` REQUIRED on `ListBuilderWorkflow`. The legacy `configSchema?` / `ConfigurationFields?` / `AdvancedFields?` / `inputForm?` fields are gone.
+- Removes several `@elevasis/core` execution-form types (`SerializedFormField`, `SerializedFormSchema`, `SerializedExecutionFormSchema`, `SerializedExecutionInterface`, `ExecutionRunnerCatalogItem`, `ExecutionRunnerCatalogResponse`, plus `interface?` from definition types), the `ResourceExecuteForm` / `ResourceExecuteDialog` / `ExecutionRunner` surfaces from `@elevasis/ui`, and the API `execution/runner/` runtime.
+
+If a derived project authors its own list-builder step actions or imported any of the deleted types, it will not compile against the new `@elevasis/ui` / `@elevasis/core` baselines without the migration below.
+
+## Applies to
+
+- All template-derived projects whose `ui/` consumes `@elevasis/ui` and registers list-builder actions.
+- Any project whose `core/` or `operations/` imports the removed execution-form types from `@elevasis/core`.
+- Any project rendering the list-builder Build tab via `LeadGenListDetailPage` or its `RunWorkflowModal`.
+
+## Required actions
+
+1. Bump `@elevasis/core` and `@elevasis/ui` to the versions published by this train (see `external/_template/{core,ui}/package.json` baselines).
+2. For every `ListBuilderWorkflow` registry entry the project authors locally, swap to the `schema + layout` contract:
+   - Add a browser-safe sibling schema export (split-file pattern: keep Node-only deps out of `ui/`).
+   - Provide a `StepConfigLayout<T>` describing field hints (no React, no validation logic).
+   - Drop any `ConfigurationFields` / `AdvancedFields` / `configSchema` / `inputForm` references.
+3. Delete any imports of the removed core types: `SerializedFormField`, `SerializedFormSchema`, `SerializedExecutionFormSchema`, `SerializedExecutionInterface`, `ExecutionRunnerCatalogItem`, `ExecutionRunnerCatalogResponse`, and the `interface?` field on workflow definitions.
+4. If the project rendered the deleted `ResourceExecuteForm` / `ResourceExecuteDialog` / `ExecutionRunner` surfaces, replace with `<StepConfigForm>` (curated UX) or `<ZodFormRenderer>` (auto-derived from Zod) as appropriate. `renderExecuteDialog` is now REQUIRED on `ResourceDetailPage`.
+5. Re-run `pnpm -C ui check-types` and `pnpm -C operations check-types` to confirm the schema sibling files resolve and no removed types remain referenced.
+
+## Verification
+
+- `pnpm -C ui check-types` — no references to `SerializedFormField`, `SerializedExecutionFormSchema`, `ResourceExecuteForm`, etc.
+- `pnpm -C ui build` — clean build with the new `@elevasis/ui` baseline.
+- `pnpm -C operations check` and `check-types` — clean.
+- BuildTab smoke (manual): open a list under `/lead-gen/lists/{listId}`, select a step, confirm the right column renders the `Configuration | Advanced | Runs` tabs and the schema-driven form (defaults populate, validation Alert fires + clears on edit, conditional `when:` predicates toggle, `recentRuns[0]` auto-load works).
+
+## Not handled by /git-sync
+
+- Project-authored `ListBuilderWorkflow` registrations are project-owned code; `/git-sync` does not migrate them. Each project must port its action entries to `schema + layout` by hand following the `apolloImportLayout` pattern in the template's `apps/command-center/src/main.tsx`.
+- Browser dev-smoke for each migrated step type is operator-driven; not automatable through sync.
+- Any local re-implementations or extensions of the deleted `ResourceExecuteForm` / `ExecutionRunner` surfaces must be removed manually before this baseline can be adopted.

package/reference/claude-config/sync-notes/2026-05-06-sdk-changes-release-train.md

@@ -0,0 +1,37 @@
+# 2026-05-06 -- SDK Changes Release Train
+
+## Why this note exists
+
+This train coordinates the Google Calendar integration, list-builder OM Spine cleanup, and OM Spine documentation/skill surfaces into one package and external-sync release. It publishes updated `@elevasis/core`, `@elevasis/ui`, and `@elevasis/sdk` baselines, then syncs template Claude guidance and package versions to derived projects.
+
+## Applies to
+
+- Template-derived projects consuming `@elevasis/core`, `@elevasis/ui`, or `@elevasis/sdk`.
+- Projects using the list-builder workflow factory or custom lead-gen build-state UI.
+- Projects relying on tenant Claude guidance for `/knowledge`, `/project`, `/tutorial`, or ambient `vibe` behavior.
+
+## Required actions
+
+1. Pull the synced template changes through `/git-sync`.
+2. Accept the package baseline bumps published by this train:
+   - `core/package.json`: `@elevasis/core`
+   - `ui/package.json`: `@elevasis/ui`
+   - `operations/package.json`: `@elevasis/core` and `@elevasis/sdk`
+3. Review local list-builder customizations against the OM-owned stage vocabulary and SDK `listBuilderWorkflow(...)` factory.
+4. Review any local tenant guidance overrides before accepting the synced `.claude/rules/vibe.md` and `.claude/skills/{knowledge,project,tutorial}/SKILL.md` changes.
+
+## Verification
+
+- `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`
+- `pnpm -C core test`
+
+## Not handled by /git-sync
+
+- Project-authored list-builder workflow registrations remain project-owned code.
+- Google Calendar OAuth configuration remains an Elevasis platform/admin responsibility, not a tenant scaffold migration.
+- Manual browser smoke for authenticated calendar views is not automated by template sync.

package/reference/scaffold/reference/contracts.md

@@ -198,6 +198,18 @@ export type OrgKnowledgeNode = z.infer<typeof OrgKnowledgeNodeSchema>
 export type OrgKnowledgeKind = z.infer<typeof OrgKnowledgeKindSchema>
 ```
 
+### `KnowledgeSkillBinding`
+
+```typescript
+export type KnowledgeSkillBinding = z.infer<typeof KnowledgeSkillBindingSchema>
+```
+
+### `KnowledgeDomainBinding`
+
+```typescript
+export type KnowledgeDomainBinding = z.infer<typeof KnowledgeDomainBindingSchema>
+```
+
 ### `OrganizationModelIconToken`
 
 ```typescript
@@ -869,7 +881,9 @@ export interface AcqCompany {
   category: string | null
   categoryPain: string | null
   segment: string | null
-  pipelineStatus: CompanyPipelineStatus | null
+  processingState: CompanyProcessingState | null
+  /** @deprecated Use `processingState`. This legacy DB column has been removed; responses return null. */
+  pipelineStatus?: LegacyPipelineStatus | null
   enrichmentData: CompanyEnrichmentData | null
   source: string | null
   batchId: string | null
@@ -909,7 +923,9 @@ export interface AcqContact {
   openingLine: string | null
   source: string | null
   sourceId: string | null
-  pipelineStatus: ContactPipelineStatus | null
+  processingState: ContactProcessingState | null
+  /** @deprecated Use `processingState`. This legacy DB column has been removed; responses return null. */
+  pipelineStatus?: LegacyPipelineStatus | null
   enrichmentData: ContactEnrichmentData | null
   /** Attio Person record ID - set when contact responds and is added to CRM */
   attioPersonId: string | null
@@ -972,7 +988,7 @@ export interface DealContact {
   title: string | null
   headline: string | null
   linkedin_url: string | null
-  pipeline_status: Record<string, unknown> | null
+  processing_state: Record<string, unknown> | null
   enrichment_data: Record<string, unknown> | null
   company: {
     id: string
@@ -1245,7 +1261,7 @@ export const DealContactSummarySchema = z.object({
   title: z.string().nullable(),
   headline: z.string().nullable(),
   linkedin_url: z.string().nullable(),
-  pipeline_status: z.record(z.string(), z.unknown()).nullable(),
+  processing_state: ProcessingStateSchema.nullable(),
   enrichment_data: z.record(z.string(), z.unknown()).nullable(),
   company: z
     .object({
@@ -1573,51 +1589,6 @@ export interface WebPost {
 }
 ```
 
-### `CompanyPipelineStatus`
-
-```typescript
-/**
- * Tracks pipeline status for a company across all processing stages.
- */
-export interface CompanyPipelineStatus {
-  acquired: boolean
-  enrichment: {
-    [source: string]: {
-      status: 'pending' | 'complete' | 'failed' | 'skipped'
-      completedAt?: string
-      error?: string
-    }
-  }
-}
-```
-
-### `ContactPipelineStatus`
-
-```typescript
-/**
- * Tracks pipeline status for a contact across all processing stages.
- */
-export interface ContactPipelineStatus {
-  enrichment: {
-    [source: string]: {
-      status: 'pending' | 'complete' | 'failed' | 'skipped'
-      completedAt?: string
-      error?: string
-    }
-  }
-  personalization: {
-    status: 'pending' | 'complete' | 'failed' | 'skipped'
-    completedAt?: string
-  }
-  outreach: {
-    status: 'pending' | 'sent' | 'replied' | 'bounced' | 'opted-out'
-    sentAt?: string
-    channel?: string
-    campaignId?: string
-  }
-}
-```
-
 ### `CompanyEnrichmentData`
 
 ```typescript
@@ -1733,7 +1704,9 @@ export interface AcqCompany {
   category: string | null
   categoryPain: string | null
   segment: string | null
-  pipelineStatus: CompanyPipelineStatus | null
+  processingState: CompanyProcessingState | null
+  /** @deprecated Use `processingState`. This legacy DB column has been removed; responses return null. */
+  pipelineStatus?: LegacyPipelineStatus | null
   enrichmentData: CompanyEnrichmentData | null
   source: string | null
   batchId: string | null
@@ -1773,7 +1746,9 @@ export interface AcqContact {
   openingLine: string | null
   source: string | null
   sourceId: string | null
-  pipelineStatus: ContactPipelineStatus | null
+  processingState: ContactProcessingState | null
+  /** @deprecated Use `processingState`. This legacy DB column has been removed; responses return null. */
+  pipelineStatus?: LegacyPipelineStatus | null
   enrichmentData: ContactEnrichmentData | null
   /** Attio Person record ID - set when contact responds and is added to CRM */
   attioPersonId: string | null
@@ -2084,6 +2059,7 @@ export const ListCompaniesQuerySchema = z
     website: z.string().trim().min(1).max(2048).optional(),
     segment: z.string().trim().min(1).max(255).optional(),
     category: z.string().trim().min(1).max(255).optional(),
+    pipelineStatus: z.unknown().optional(),
     batchId: z.string().trim().min(1).max(255).optional(),
     status: AcqCompanyStatusSchema.optional(),
     includeAll: QueryBooleanSchema.optional(),
@@ -2125,6 +2101,7 @@ export const CreateCompanyRequestSchema = z
     category: z.string().trim().min(1).max(255).optional(),
     source: z.string().trim().min(1).max(255).optional(),
     batchId: z.string().trim().min(1).max(255).optional(),
+    pipelineStatus: z.unknown().optional(),
     verticalResearch: z.string().trim().min(1).max(5000).optional()
   })
   .strict()
@@ -2145,7 +2122,8 @@ export const UpdateCompanyRequestSchema = z
     locationState: z.string().trim().min(1).max(255).optional(),
     category: z.string().trim().min(1).max(255).optional(),
     segment: z.string().trim().min(1).max(255).optional(),
-    pipelineStatus: z.record(z.string(), z.unknown()).optional(),
+    processingState: CompanyProcessingStateSchema.optional(),
+    pipelineStatus: z.unknown().optional(),
     enrichmentData: z.record(z.string(), z.unknown()).optional(),
     source: z.string().trim().min(1).max(255).optional(),
     batchId: z.string().trim().min(1).max(255).optional(),
@@ -2165,6 +2143,7 @@ export const UpdateCompanyRequestSchema = z
       data.locationState !== undefined ||
       data.category !== undefined ||
       data.segment !== undefined ||
+      data.processingState !== undefined ||
       data.pipelineStatus !== undefined ||
       data.enrichmentData !== undefined ||
       data.source !== undefined ||
@@ -2190,7 +2169,8 @@ export const CreateContactRequestSchema = z
     title: z.string().trim().min(1).max(255).optional(),
     source: z.string().trim().min(1).max(255).optional(),
     sourceId: z.string().trim().min(1).max(255).optional(),
-    batchId: z.string().trim().min(1).max(255).optional()
+    batchId: z.string().trim().min(1).max(255).optional(),
+    pipelineStatus: z.unknown().optional()
   })
   .strict()
 ```
@@ -2209,7 +2189,8 @@ export const UpdateContactRequestSchema = z
     headline: z.string().trim().min(1).max(5000).optional(),
     filterReason: z.string().trim().min(1).max(5000).optional(),
     openingLine: z.string().trim().min(1).max(5000).optional(),
-    pipelineStatus: z.record(z.string(), z.unknown()).optional(),
+    processingState: ContactProcessingStateSchema.optional(),
+    pipelineStatus: z.unknown().optional(),
     enrichmentData: z.record(z.string(), z.unknown()).optional(),
     status: AcqContactStatusSchema.optional()
   })
@@ -2225,6 +2206,7 @@ export const UpdateContactRequestSchema = z
       data.headline !== undefined ||
       data.filterReason !== undefined ||
       data.openingLine !== undefined ||
+      data.processingState !== undefined ||
       data.pipelineStatus !== undefined ||
       data.enrichmentData !== undefined ||
       data.status !== undefined,
@@ -2251,7 +2233,8 @@ export const AcqCompanyResponseSchema = z.object({
   category: z.string().nullable(),
   categoryPain: z.string().nullable(),
   segment: z.string().nullable(),
-  pipelineStatus: z.record(z.string(), z.unknown()).nullable(),
+  processingState: CompanyProcessingStateSchema.nullable(),
+  pipelineStatus: z.unknown().nullable().optional(),
   enrichmentData: z.record(z.string(), z.unknown()).nullable(),
   source: z.string().nullable(),
   batchId: z.string().nullable(),
@@ -2317,7 +2300,8 @@ export const AcqContactResponseSchema = z.object({
   openingLine: z.string().nullable(),
   source: z.string().nullable(),
   sourceId: z.string().nullable(),
-  pipelineStatus: z.record(z.string(), z.unknown()).nullable(),
+  processingState: ContactProcessingStateSchema.nullable(),
+  pipelineStatus: z.unknown().nullable().optional(),
   enrichmentData: z.record(z.string(), z.unknown()).nullable(),
   attioPersonId: z.string().nullable(),
   batchId: z.string().nullable(),
@@ -2483,6 +2467,7 @@ export const AcqListCompanyResponseSchema = z.object({
 
 ```typescript
 export const AcqCompanySchemas = {
+  CompanyProcessingState: CompanyProcessingStateSchema,
   CompanyIdParams: CompanyIdParamsSchema,
   ListCompaniesQuery: ListCompaniesQuerySchema,
   CreateCompanyRequest: CreateCompanyRequestSchema,
@@ -2497,6 +2482,7 @@ export const AcqCompanySchemas = {
 
 ```typescript
 export const AcqContactSchemas = {
+  ContactProcessingState: ContactProcessingStateSchema,
   ContactIdParams: ContactIdParamsSchema,
   ListContactsQuery: ListContactsQuerySchema,
   CreateContactRequest: CreateContactRequestSchema,
@@ -2522,7 +2508,10 @@ export const AcqListSchemas = {
   BuildPlanSnapshot: BuildPlanSnapshotSchema,
   BuildPlanSnapshotStep: BuildPlanSnapshotStepSchema,
   AcqListMetadata: AcqListMetadataSchema,
+  LeadGenStageKey: LeadGenStageKeySchema,
+  LeadGenCapabilityKey: LeadGenCapabilityKeySchema,
   ProcessingStageStatus: ProcessingStageStatusSchema,
+  ProcessingState: ProcessingStateSchema,
   ListStageCounts: ListStageCountsSchema,
   ListTelemetry: ListTelemetrySchema,
 
@@ -2815,6 +2804,8 @@ export interface CreateCompanyParams {
   source?: string
   batchId?: string
   verticalResearch?: string
+  /** @deprecated Use processingState. Accepted as a no-op compatibility bridge for external tenants. */
+  pipelineStatus?: unknown
 }
 ```
 
@@ -2832,7 +2823,9 @@ export interface UpdateCompanyParams {
   locationState?: string
   category?: string
   segment?: string
-  pipelineStatus?: Record<string, unknown>
+  processingState?: ProcessingState
+  /** @deprecated Use processingState. Accepted as a no-op compatibility bridge for external tenants. */
+  pipelineStatus?: unknown
   enrichmentData?: Record<string, unknown>
   source?: string
   batchId?: string
@@ -2840,7 +2833,7 @@ export interface UpdateCompanyParams {
   verticalResearch?: string | null
   /** Track A: flat qualification score column (null until a scoring rubric is defined) */
   qualificationScore?: number | null
-  /** Track A: flat qualification signals jsonb — mirrors the former pipeline_status.qualification shape */
+  /** Track A: flat qualification signals jsonb */
   qualificationSignals?: Record<string, unknown> | null
   /** Track A: key identifying the rubric used for qualification */
   qualificationRubricKey?: string | null
@@ -2863,13 +2856,15 @@ export interface CompanyFilters {
   website?: string
   segment?: string
   category?: string
-  pipelineStatus?: Record<string, unknown>
-  /** Exclude companies whose pipeline_status contains this value (PostgREST NOT contains) */
-  pipelineStatusNot?: Record<string, unknown>
+  processingState?: ProcessingState
+  /** @deprecated Use processingState. Accepted as a no-op compatibility bridge for external tenants. */
+  pipelineStatus?: unknown
+  /** Exclude companies whose processing state contains this value (PostgREST NOT contains) */
+  processingStateNot?: ProcessingState
   batchId?: string
   status?: 'active' | 'invalid'
   includeAll?: boolean
-  excludeColumns?: Array<'enrichmentData' | 'pipelineStatus'>
+  excludeColumns?: Array<'enrichmentData' | 'processingState'>
   limit?: number
 }
 ```
@@ -2888,6 +2883,8 @@ export interface CreateContactParams {
   source?: string
   sourceId?: string
   batchId?: string
+  /** @deprecated Use processingState. Accepted as a no-op compatibility bridge for external tenants. */
+  pipelineStatus?: unknown
 }
 ```
 
@@ -2904,7 +2901,9 @@ export interface UpdateContactParams {
   headline?: string
   filterReason?: string
   openingLine?: string
-  pipelineStatus?: Record<string, unknown>
+  processingState?: ProcessingState
+  /** @deprecated Use processingState. Accepted as a no-op compatibility bridge for external tenants. */
+  pipelineStatus?: unknown
   enrichmentData?: Record<string, unknown>
   status?: 'active' | 'invalid'
 }
@@ -2923,7 +2922,9 @@ export interface ContactFilters {
   listId?: string // Filter to contacts in a specific list (via acq_list_members)
   search?: string
   openingLineIsNull?: boolean // Filter to contacts without personalization
-  pipelineStatus?: Record<string, unknown>
+  processingState?: ProcessingState
+  /** @deprecated Use processingState. Accepted as a no-op compatibility bridge for external tenants. */
+  pipelineStatus?: unknown
   batchId?: string
   contactStatus?: 'active' | 'invalid' // Filter by contact status (soft-delete flag)
 }
@@ -3122,7 +3123,7 @@ export interface BulkImportCompanyEntry {
   category?: string
   source?: string
   enrichmentData?: Record<string, unknown>
-  pipelineStatus?: Record<string, unknown>
+  processingState?: ProcessingState
 }
 ```
 
@@ -3303,6 +3304,14 @@ export type ListToolMap = {
     params: Omit<UpdateContactStageParams, 'organizationId'>
     result: void
   }
+  listPendingCompanyIds: {
+    params: Omit<ListPendingCompanyIdsParams, 'organizationId'>
+    result: string[]
+  }
+  listPendingContactIds: {
+    params: Omit<ListPendingContactIdsParams, 'organizationId'>
+    result: string[]
+  }
 }
 ```
 
@@ -3338,6 +3347,10 @@ export const OrgKnowledgeNodeSchema = z.object({
    * Each link emits a `governs` edge: knowledge-node -> target node.
    */
   links: z.array(KnowledgeLinkSchema).default([]),
+  /** Operator skill or command bindings relevant to this node. */
+  skills: z.array(KnowledgeSkillBindingSchema).optional(),
+  /** Domain key used to derive fast graph->skill registries. */
+  domain: KnowledgeDomainBindingSchema.optional(),
   /** Identifiers of the roles or members who own this knowledge node. */
   ownerIds: z.array(ModelIdSchema).default([]),
   /** ISO date string (YYYY-MM-DD or full ISO 8601) of last meaningful update. */