@clivly/core 0.11.0-next.0 → 0.11.0

package/dist/adapter.d.cts

@@ -1,4 +1,4 @@
-import { Activity, Company, Contact, ContactFilters, CreateActivityInput, CreateCompanyInput, CreateContactInput, CreateDealInput, CreateTaskInput, Deal, RecordSource, Task, TaskFilters, UpdateContactInput, UpdateDealInput, UpdateTaskInput } from "./types.cjs";
+import { Activity, Company, CompanyFilters, Contact, ContactFilters, CreateActivityInput, CreateCompanyInput, CreateContactInput, CreateDealInput, CreateTaskInput, Deal, RecordSource, Task, TaskFilters, UpdateCompanyInput, UpdateContactInput, UpdateDealInput, UpdateTaskInput } from "./types.cjs";
 //#region src/adapter.d.ts
 /**
  * The contract every ORM implementation fulfils. `packages/drizzle` is the first
@@ -8,7 +8,15 @@ import { Activity, Company, Contact, ContactFilters, CreateActivityInput, Create
  * one place tenant isolation is enforced for CRM data. Implementations only ever
  * read/write Clivly-owned `crm_*` tables; they never mutate host business tables.
  */
-interface CRMAdapter {
+export interface CRMAdapter {
+  /**
+   * Soft-delete: sets `archivedAt` so the row drops out of lists while the
+   * deals, activities and tasks that reference it keep resolving. Mirrors the
+   * sync engine's archive-on-leave doctrine — a contact that disappears from
+   * the host view is archived, never deleted, for exactly this reason.
+   */
+  archiveCompany(orgId: string, id: string): Promise<Company>;
+  archiveContact(orgId: string, id: string): Promise<Contact>;
   archiveTask(orgId: string, id: string): Promise<Task>;
   completeTask(orgId: string, id: string): Promise<Task>;
   createActivity(orgId: string, data: CreateActivityInput): Promise<Activity>;
@@ -18,11 +26,33 @@ interface CRMAdapter {
   createTask(orgId: string, data: CreateTaskInput): Promise<Task>;
   deleteDeal(orgId: string, id: string): Promise<Deal | null>;
   getActivities(orgId: string, contactId: string): Promise<Activity[]>;
-  getCompanies(orgId: string, filters?: {
-    source?: RecordSource;
-  }): Promise<Company[]>;
+  getCompanies(orgId: string, filters?: CompanyFilters): Promise<Company[]>;
+  /**
+   * The companies named by `ids`, for resolving a page of contacts to company
+   * names.
+   *
+   * `contacts.list` used to build that map from `getCompanies(orgId)` — every
+   * company in the org, to label at most one per listed contact. Scoping the
+   * fetch to the ids actually referenced keeps a bounded page of contacts from
+   * dragging an unbounded sibling query behind it.
+   *
+   * Returns only the rows that exist; a missing id is not an error, because a
+   * contact can reference a company archived since the page was built.
+   */
+  getCompaniesByIds(orgId: string, ids: string[]): Promise<Company[]>;
+  getCompany(orgId: string, id: string): Promise<Company | null>;
   getContact(orgId: string, id: string): Promise<Contact | null>;
   getContacts(orgId: string, filters?: ContactFilters): Promise<Contact[]>;
+  /**
+   * The contacts named by `ids`, for resolving a page of deals to contact
+   * names. See {@link CRMAdapter.getCompaniesByIds} — `deals.list` had the
+   * same unbounded-sibling problem.
+   *
+   * Deliberately unfiltered by archive state: a live deal pointing at an
+   * archived contact must still render that contact's name, which is the same
+   * reason `deals.list` never passed `excludeArchived` to `getContacts`.
+   */
+  getContactsByIds(orgId: string, ids: string[]): Promise<Contact[]>;
   getDeal(orgId: string, id: string): Promise<Deal | null>;
   getDeals(orgId: string, filters?: {
     source?: RecordSource;
@@ -35,11 +65,18 @@ interface CRMAdapter {
    */
   moveDeal(orgId: string, id: string, stage: Deal["stage"], afterId: string | null): Promise<Deal>;
   reopenTask(orgId: string, id: string): Promise<Task>;
+  /**
+   * Clear `archivedAt`, putting the row back in the lists. The inverse of
+   * `archiveCompany` / `archiveContact`, and what an "Undo" on an archive
+   * toast calls — archiving is reversible, so the UI should be able to say so.
+   */
+  unarchiveCompany(orgId: string, id: string): Promise<Company>;
+  unarchiveContact(orgId: string, id: string): Promise<Contact>;
+  updateCompany(orgId: string, id: string, data: UpdateCompanyInput): Promise<Company>;
   updateContact(orgId: string, id: string, data: UpdateContactInput): Promise<Contact>;
   updateDeal(orgId: string, id: string, data: UpdateDealInput): Promise<Deal>;
   updateDealStage(orgId: string, id: string, stage: Deal["stage"]): Promise<Deal>;
   updateTask(orgId: string, id: string, data: UpdateTaskInput): Promise<Task>;
   updateTaskStatus(orgId: string, id: string, status: Task["status"]): Promise<Task>;
 }
-//#endregion
-export { CRMAdapter };
+//#endregion

package/dist/adapter.d.mts

@@ -1,4 +1,4 @@
-import { Activity, Company, Contact, ContactFilters, CreateActivityInput, CreateCompanyInput, CreateContactInput, CreateDealInput, CreateTaskInput, Deal, RecordSource, Task, TaskFilters, UpdateContactInput, UpdateDealInput, UpdateTaskInput } from "./types.mjs";
+import { Activity, Company, CompanyFilters, Contact, ContactFilters, CreateActivityInput, CreateCompanyInput, CreateContactInput, CreateDealInput, CreateTaskInput, Deal, RecordSource, Task, TaskFilters, UpdateCompanyInput, UpdateContactInput, UpdateDealInput, UpdateTaskInput } from "./types.mjs";
 //#region src/adapter.d.ts
 /**
  * The contract every ORM implementation fulfils. `packages/drizzle` is the first
@@ -8,7 +8,15 @@ import { Activity, Company, Contact, ContactFilters, CreateActivityInput, Create
  * one place tenant isolation is enforced for CRM data. Implementations only ever
  * read/write Clivly-owned `crm_*` tables; they never mutate host business tables.
  */
-interface CRMAdapter {
+export interface CRMAdapter {
+  /**
+   * Soft-delete: sets `archivedAt` so the row drops out of lists while the
+   * deals, activities and tasks that reference it keep resolving. Mirrors the
+   * sync engine's archive-on-leave doctrine — a contact that disappears from
+   * the host view is archived, never deleted, for exactly this reason.
+   */
+  archiveCompany(orgId: string, id: string): Promise<Company>;
+  archiveContact(orgId: string, id: string): Promise<Contact>;
   archiveTask(orgId: string, id: string): Promise<Task>;
   completeTask(orgId: string, id: string): Promise<Task>;
   createActivity(orgId: string, data: CreateActivityInput): Promise<Activity>;
@@ -18,11 +26,33 @@ interface CRMAdapter {
   createTask(orgId: string, data: CreateTaskInput): Promise<Task>;
   deleteDeal(orgId: string, id: string): Promise<Deal | null>;
   getActivities(orgId: string, contactId: string): Promise<Activity[]>;
-  getCompanies(orgId: string, filters?: {
-    source?: RecordSource;
-  }): Promise<Company[]>;
+  getCompanies(orgId: string, filters?: CompanyFilters): Promise<Company[]>;
+  /**
+   * The companies named by `ids`, for resolving a page of contacts to company
+   * names.
+   *
+   * `contacts.list` used to build that map from `getCompanies(orgId)` — every
+   * company in the org, to label at most one per listed contact. Scoping the
+   * fetch to the ids actually referenced keeps a bounded page of contacts from
+   * dragging an unbounded sibling query behind it.
+   *
+   * Returns only the rows that exist; a missing id is not an error, because a
+   * contact can reference a company archived since the page was built.
+   */
+  getCompaniesByIds(orgId: string, ids: string[]): Promise<Company[]>;
+  getCompany(orgId: string, id: string): Promise<Company | null>;
   getContact(orgId: string, id: string): Promise<Contact | null>;
   getContacts(orgId: string, filters?: ContactFilters): Promise<Contact[]>;
+  /**
+   * The contacts named by `ids`, for resolving a page of deals to contact
+   * names. See {@link CRMAdapter.getCompaniesByIds} — `deals.list` had the
+   * same unbounded-sibling problem.
+   *
+   * Deliberately unfiltered by archive state: a live deal pointing at an
+   * archived contact must still render that contact's name, which is the same
+   * reason `deals.list` never passed `excludeArchived` to `getContacts`.
+   */
+  getContactsByIds(orgId: string, ids: string[]): Promise<Contact[]>;
   getDeal(orgId: string, id: string): Promise<Deal | null>;
   getDeals(orgId: string, filters?: {
     source?: RecordSource;
@@ -35,11 +65,18 @@ interface CRMAdapter {
    */
   moveDeal(orgId: string, id: string, stage: Deal["stage"], afterId: string | null): Promise<Deal>;
   reopenTask(orgId: string, id: string): Promise<Task>;
+  /**
+   * Clear `archivedAt`, putting the row back in the lists. The inverse of
+   * `archiveCompany` / `archiveContact`, and what an "Undo" on an archive
+   * toast calls — archiving is reversible, so the UI should be able to say so.
+   */
+  unarchiveCompany(orgId: string, id: string): Promise<Company>;
+  unarchiveContact(orgId: string, id: string): Promise<Contact>;
+  updateCompany(orgId: string, id: string, data: UpdateCompanyInput): Promise<Company>;
   updateContact(orgId: string, id: string, data: UpdateContactInput): Promise<Contact>;
   updateDeal(orgId: string, id: string, data: UpdateDealInput): Promise<Deal>;
   updateDealStage(orgId: string, id: string, stage: Deal["stage"]): Promise<Deal>;
   updateTask(orgId: string, id: string, data: UpdateTaskInput): Promise<Task>;
   updateTaskStatus(orgId: string, id: string, status: Task["status"]): Promise<Task>;
 }
-//#endregion
-export { CRMAdapter };
+//#endregion

package/dist/auth-adapter.d.cts

@@ -1,6 +1,6 @@
 import { CrmRole } from "./types.cjs";
 //#region src/auth-adapter.d.ts
-interface ClivlyUser {
+export interface ClivlyUser {
   email: string;
   id: string;
   name?: string;
@@ -13,17 +13,16 @@ interface ClivlyUser {
  * This answers "who is this person?" only. Authorization ("what can they do in
  * this org?") is the separate `crm_members` layer — see `MembershipResolver`.
  */
-interface ClivlyAuthAdapter {
+export interface ClivlyAuthAdapter {
   getUser(req: Request): Promise<ClivlyUser | null>;
 }
-declare function authCustom(resolver: (req: Request) => Promise<ClivlyUser | null> | ClivlyUser | null): ClivlyAuthAdapter;
-interface CrmMembership {
+export declare function authCustom(resolver: (req: Request) => Promise<ClivlyUser | null> | ClivlyUser | null): ClivlyAuthAdapter;
+export interface CrmMembership {
   orgId: string;
   role: CrmRole;
   userId: string;
 }
-interface MembershipResolver {
+export interface MembershipResolver {
   getMembership(userId: string, orgId: string): Promise<CrmMembership | null>;
 }
-//#endregion
-export { ClivlyAuthAdapter, ClivlyUser, CrmMembership, MembershipResolver, authCustom };
+//#endregion

package/dist/auth-adapter.d.mts

@@ -1,6 +1,6 @@
 import { CrmRole } from "./types.mjs";
 //#region src/auth-adapter.d.ts
-interface ClivlyUser {
+export interface ClivlyUser {
   email: string;
   id: string;
   name?: string;
@@ -13,17 +13,16 @@ interface ClivlyUser {
  * This answers "who is this person?" only. Authorization ("what can they do in
  * this org?") is the separate `crm_members` layer — see `MembershipResolver`.
  */
-interface ClivlyAuthAdapter {
+export interface ClivlyAuthAdapter {
   getUser(req: Request): Promise<ClivlyUser | null>;
 }
-declare function authCustom(resolver: (req: Request) => Promise<ClivlyUser | null> | ClivlyUser | null): ClivlyAuthAdapter;
-interface CrmMembership {
+export declare function authCustom(resolver: (req: Request) => Promise<ClivlyUser | null> | ClivlyUser | null): ClivlyAuthAdapter;
+export interface CrmMembership {
   orgId: string;
   role: CrmRole;
   userId: string;
 }
-interface MembershipResolver {
+export interface MembershipResolver {
   getMembership(userId: string, orgId: string): Promise<CrmMembership | null>;
 }
-//#endregion
-export { ClivlyAuthAdapter, ClivlyUser, CrmMembership, MembershipResolver, authCustom };
+//#endregion

package/dist/builder.d.cts

@@ -1,4 +1,4 @@
-import { R as ProjectionMapping, m as DiscoveredSchemaTable } from "./entity-config-Ddgukq_E.cjs";
+import { R as ProjectionMapping, m as DiscoveredSchemaTable } from "./entity-config-OhC4Otkz.cjs";
 //#region src/relationship-graph.d.ts
 /**
  * A bidirectional relationship graph derived from discovery metadata.
@@ -82,14 +82,14 @@ interface RelationshipGraph {
   nodes: RelationshipNode[];
 }
 /** Every edge whose `fromTable` is `table`, in either direction. */
-declare function edgesFrom(graph: RelationshipGraph, table: string): RelationshipEdge[];
+export declare function edgesFrom(graph: RelationshipGraph, table: string): RelationshipEdge[];
 /**
  * Build the bidirectional relationship graph for a discovered schema.
  *
  * No table, column, or relationship is ever named in this function — the
  * only input is the schema itself.
  */
-declare function buildRelationshipGraph(schema: DiscoveredSchemaTable[]): RelationshipGraph;
+export declare function buildRelationshipGraph(schema: DiscoveredSchemaTable[]): RelationshipGraph;
 //#endregion
 //#region src/path-enumeration.d.ts
 /**
@@ -120,11 +120,11 @@ declare function buildRelationshipGraph(schema: DiscoveredSchemaTable[]): Relati
  * the graph and the starting table.
  */
 /** Spec-mandated: how many edges deep a path may go. */
-declare const MAX_HOPS = 3;
+export declare const MAX_HOPS = 3;
 /** Spec-mandated: how many candidate paths may be considered before stopping. */
-declare const MAX_CANDIDATES = 200;
+export declare const MAX_CANDIDATES = 200;
 /** Spec-mandated: how many ranked results may be displayed. */
-declare const MAX_RESULTS = 50;
+export declare const MAX_RESULTS = 50;
 /** Which budget stopped the walk. Absent when nothing was cut. */
 type PathTruncationCause = "candidate-budget" | "result-limit";
 interface EnumeratedPath {
@@ -185,7 +185,7 @@ interface EnumeratePathsOptions {
  * defect — and it is precisely why truncation is reported, so the UI can
  * offer a narrower search instead of implying the list is complete.
  */
-declare function enumeratePaths(graph: RelationshipGraph, startTable: string, options?: EnumeratePathsOptions): PathEnumeration;
+export declare function enumeratePaths(graph: RelationshipGraph, startTable: string, options?: EnumeratePathsOptions): PathEnumeration;
 //#endregion
 //#region src/path-compiler.d.ts
 /** A field the user picked, optionally reached through a path. */
@@ -214,7 +214,7 @@ interface CompilePathsOptions {
  * the point: the alternative — emitting a plausible-looking mapping — is the
  * defect class this whole body of work exists to close.
  */
-declare class PathCompileError extends Error {
+export declare class PathCompileError extends Error {
   constructor(message: string);
 }
 /**
@@ -225,7 +225,7 @@ declare class PathCompileError extends Error {
  * mapping it returns satisfies `projectionSchema` and, given a schema whose
  * tables carry rich metadata, `validateProjection`.
  */
-declare function compilePaths(options: CompilePathsOptions): ProjectionMapping;
+export declare function compilePaths(options: CompilePathsOptions): ProjectionMapping;
 //#endregion
 //#region src/starting-record-change.d.ts
 /**
@@ -297,7 +297,7 @@ interface ClassifyStartingRecordChangeOptions {
  * throws, because its caller is a confirmation dialog that must be able to
  * render an answer for any proposed change, including a nonsensical one.
  */
-declare function classifyStartingRecordChange(options: ClassifyStartingRecordChangeOptions): StartingRecordChangeImpact;
+export declare function classifyStartingRecordChange(options: ClassifyStartingRecordChangeOptions): StartingRecordChangeImpact;
 //#endregion
 //#region src/starting-record-eligibility.d.ts
 /**
@@ -331,6 +331,6 @@ interface StartingRecordOption {
  * No table, column, or relationship is ever named in this function — the
  * only input is the schema itself.
  */
-declare function listStartingRecordOptions(schema: DiscoveredSchemaTable[]): StartingRecordOption[];
+export declare function listStartingRecordOptions(schema: DiscoveredSchemaTable[]): StartingRecordOption[];
 //#endregion
-export { type ClassifyStartingRecordChangeOptions, type CompilePathsOptions, type CompositePrimaryKeyReason, type EnumeratePathsOptions, type EnumeratedPath, type IneligibilityReason, MAX_CANDIDATES, MAX_HOPS, MAX_RESULTS, type NoPrimaryKeyReason, type NoRichMetaReason, PathCompileError, type PathEnumeration, type PathTruncationCause, type PickedField, type RelationshipCardinality, type RelationshipDirection, type RelationshipEdge, type RelationshipGraph, type RelationshipNode, type StartingRecordChangeImpact, type StartingRecordOption, buildRelationshipGraph, classifyStartingRecordChange, compilePaths, edgesFrom, enumeratePaths, listStartingRecordOptions };
+export type { ClassifyStartingRecordChangeOptions, CompilePathsOptions, CompositePrimaryKeyReason, EnumeratePathsOptions, EnumeratedPath, IneligibilityReason, NoPrimaryKeyReason, NoRichMetaReason, PathEnumeration, PathTruncationCause, PickedField, RelationshipCardinality, RelationshipDirection, RelationshipEdge, RelationshipGraph, RelationshipNode, StartingRecordChangeImpact, StartingRecordOption };

package/dist/builder.d.mts

@@ -1,4 +1,4 @@
-import { R as ProjectionMapping, m as DiscoveredSchemaTable } from "./entity-config-Ddgukq_E.mjs";
+import { R as ProjectionMapping, m as DiscoveredSchemaTable } from "./entity-config-OhC4Otkz.mjs";
 //#region src/relationship-graph.d.ts
 /**
  * A bidirectional relationship graph derived from discovery metadata.
@@ -82,14 +82,14 @@ interface RelationshipGraph {
   nodes: RelationshipNode[];
 }
 /** Every edge whose `fromTable` is `table`, in either direction. */
-declare function edgesFrom(graph: RelationshipGraph, table: string): RelationshipEdge[];
+export declare function edgesFrom(graph: RelationshipGraph, table: string): RelationshipEdge[];
 /**
  * Build the bidirectional relationship graph for a discovered schema.
  *
  * No table, column, or relationship is ever named in this function — the
  * only input is the schema itself.
  */
-declare function buildRelationshipGraph(schema: DiscoveredSchemaTable[]): RelationshipGraph;
+export declare function buildRelationshipGraph(schema: DiscoveredSchemaTable[]): RelationshipGraph;
 //#endregion
 //#region src/path-enumeration.d.ts
 /**
@@ -120,11 +120,11 @@ declare function buildRelationshipGraph(schema: DiscoveredSchemaTable[]): Relati
  * the graph and the starting table.
  */
 /** Spec-mandated: how many edges deep a path may go. */
-declare const MAX_HOPS = 3;
+export declare const MAX_HOPS = 3;
 /** Spec-mandated: how many candidate paths may be considered before stopping. */
-declare const MAX_CANDIDATES = 200;
+export declare const MAX_CANDIDATES = 200;
 /** Spec-mandated: how many ranked results may be displayed. */
-declare const MAX_RESULTS = 50;
+export declare const MAX_RESULTS = 50;
 /** Which budget stopped the walk. Absent when nothing was cut. */
 type PathTruncationCause = "candidate-budget" | "result-limit";
 interface EnumeratedPath {
@@ -185,7 +185,7 @@ interface EnumeratePathsOptions {
  * defect — and it is precisely why truncation is reported, so the UI can
  * offer a narrower search instead of implying the list is complete.
  */
-declare function enumeratePaths(graph: RelationshipGraph, startTable: string, options?: EnumeratePathsOptions): PathEnumeration;
+export declare function enumeratePaths(graph: RelationshipGraph, startTable: string, options?: EnumeratePathsOptions): PathEnumeration;
 //#endregion
 //#region src/path-compiler.d.ts
 /** A field the user picked, optionally reached through a path. */
@@ -214,7 +214,7 @@ interface CompilePathsOptions {
  * the point: the alternative — emitting a plausible-looking mapping — is the
  * defect class this whole body of work exists to close.
  */
-declare class PathCompileError extends Error {
+export declare class PathCompileError extends Error {
   constructor(message: string);
 }
 /**
@@ -225,7 +225,7 @@ declare class PathCompileError extends Error {
  * mapping it returns satisfies `projectionSchema` and, given a schema whose
  * tables carry rich metadata, `validateProjection`.
  */
-declare function compilePaths(options: CompilePathsOptions): ProjectionMapping;
+export declare function compilePaths(options: CompilePathsOptions): ProjectionMapping;
 //#endregion
 //#region src/starting-record-change.d.ts
 /**
@@ -297,7 +297,7 @@ interface ClassifyStartingRecordChangeOptions {
  * throws, because its caller is a confirmation dialog that must be able to
  * render an answer for any proposed change, including a nonsensical one.
  */
-declare function classifyStartingRecordChange(options: ClassifyStartingRecordChangeOptions): StartingRecordChangeImpact;
+export declare function classifyStartingRecordChange(options: ClassifyStartingRecordChangeOptions): StartingRecordChangeImpact;
 //#endregion
 //#region src/starting-record-eligibility.d.ts
 /**
@@ -331,6 +331,6 @@ interface StartingRecordOption {
  * No table, column, or relationship is ever named in this function — the
  * only input is the schema itself.
  */
-declare function listStartingRecordOptions(schema: DiscoveredSchemaTable[]): StartingRecordOption[];
+export declare function listStartingRecordOptions(schema: DiscoveredSchemaTable[]): StartingRecordOption[];
 //#endregion
-export { type ClassifyStartingRecordChangeOptions, type CompilePathsOptions, type CompositePrimaryKeyReason, type EnumeratePathsOptions, type EnumeratedPath, type IneligibilityReason, MAX_CANDIDATES, MAX_HOPS, MAX_RESULTS, type NoPrimaryKeyReason, type NoRichMetaReason, PathCompileError, type PathEnumeration, type PathTruncationCause, type PickedField, type RelationshipCardinality, type RelationshipDirection, type RelationshipEdge, type RelationshipGraph, type RelationshipNode, type StartingRecordChangeImpact, type StartingRecordOption, buildRelationshipGraph, classifyStartingRecordChange, compilePaths, edgesFrom, enumeratePaths, listStartingRecordOptions };
+export type { ClassifyStartingRecordChangeOptions, CompilePathsOptions, CompositePrimaryKeyReason, EnumeratePathsOptions, EnumeratedPath, IneligibilityReason, NoPrimaryKeyReason, NoRichMetaReason, PathEnumeration, PathTruncationCause, PickedField, RelationshipCardinality, RelationshipDirection, RelationshipEdge, RelationshipGraph, RelationshipNode, StartingRecordChangeImpact, StartingRecordOption };

package/dist/drizzle.d.cts

@@ -1,4 +1,4 @@
-import { m as DiscoveredSchemaTable, p as DiscoveredColumnMeta } from "./entity-config-Ddgukq_E.cjs";
+import { m as DiscoveredSchemaTable, p as DiscoveredColumnMeta } from "./entity-config-OhC4Otkz.cjs";
 import { Table } from "drizzle-orm";
 //#region src/drizzle.d.ts
 /**
@@ -13,14 +13,14 @@ import { Table } from "drizzle-orm";
  * "confirmed no constraints", and projection validation fails closed on the
  * former.
  */
-declare function buildUniqueConstraints(table: unknown): string[][] | undefined;
+export declare function buildUniqueConstraints(table: unknown): string[][] | undefined;
 /**
  * Per-column metadata (type, PK, nullability, FK edges) for a Drizzle table.
  * Structural only — no DB round-trip, so it is safe to recompute on every
  * heartbeat. FK reflection is best-effort; a non-Postgres table still gets
  * name/type/PK/nullable.
  */
-declare function buildColumnsMeta(table: Table): DiscoveredColumnMeta[];
+export declare function buildColumnsMeta(table: Table): DiscoveredColumnMeta[];
 /**
  * Derive Clivly's discovery shape (table + column names) from a Drizzle schema
  * object — the `* as schema` you pass to `drizzle(client, { schema })`. This
@@ -36,8 +36,7 @@ declare function buildColumnsMeta(table: Table): DiscoveredColumnMeta[];
  * when you import this entry (`@clivly/core/drizzle`); the rest of `@clivly/core`
  * stays dependency-free.
  */
-declare function discoverFromDrizzle(schema: Record<string, unknown>, options?: {
+export declare function discoverFromDrizzle(schema: Record<string, unknown>, options?: {
   allowEmpty?: boolean;
 }): DiscoveredSchemaTable[];
-//#endregion
-export { buildColumnsMeta, buildUniqueConstraints, discoverFromDrizzle };
+//#endregion

package/dist/drizzle.d.mts

@@ -1,4 +1,4 @@
-import { m as DiscoveredSchemaTable, p as DiscoveredColumnMeta } from "./entity-config-Ddgukq_E.mjs";
+import { m as DiscoveredSchemaTable, p as DiscoveredColumnMeta } from "./entity-config-OhC4Otkz.mjs";
 import { Table } from "drizzle-orm";
 //#region src/drizzle.d.ts
 /**
@@ -13,14 +13,14 @@ import { Table } from "drizzle-orm";
  * "confirmed no constraints", and projection validation fails closed on the
  * former.
  */
-declare function buildUniqueConstraints(table: unknown): string[][] | undefined;
+export declare function buildUniqueConstraints(table: unknown): string[][] | undefined;
 /**
  * Per-column metadata (type, PK, nullability, FK edges) for a Drizzle table.
  * Structural only — no DB round-trip, so it is safe to recompute on every
  * heartbeat. FK reflection is best-effort; a non-Postgres table still gets
  * name/type/PK/nullable.
  */
-declare function buildColumnsMeta(table: Table): DiscoveredColumnMeta[];
+export declare function buildColumnsMeta(table: Table): DiscoveredColumnMeta[];
 /**
  * Derive Clivly's discovery shape (table + column names) from a Drizzle schema
  * object — the `* as schema` you pass to `drizzle(client, { schema })`. This
@@ -36,8 +36,7 @@ declare function buildColumnsMeta(table: Table): DiscoveredColumnMeta[];
  * when you import this entry (`@clivly/core/drizzle`); the rest of `@clivly/core`
  * stays dependency-free.
  */
-declare function discoverFromDrizzle(schema: Record<string, unknown>, options?: {
+export declare function discoverFromDrizzle(schema: Record<string, unknown>, options?: {
   allowEmpty?: boolean;
 }): DiscoveredSchemaTable[];
-//#endregion
-export { buildColumnsMeta, buildUniqueConstraints, discoverFromDrizzle };
+//#endregion

package/dist/{entity-config-BTAJe1Zj.mjs → entity-config-C0rtu-K_.mjs}

@@ -234,7 +234,8 @@ function checkFanOut(errors, projection, resolver, base, basePk) {
 		});
 		return;
 	}
-	if (!coversUniqueKey(joinTable, identityRefs(projection.identity, basePk).filter((ref) => ref.table === join.key).map((ref) => ref.column))) errors.push({
+	const identityColumns = identityRefs(projection.identity, basePk).filter((ref) => ref.table === join.key).map((ref) => ref.column);
+	if (!coversUniqueKey(joinTable, identityColumns)) errors.push({
 		path: identityPath,
 		message: `identity does not uniquely identify a row of "${joinTable.name}", which fans out — include a unique key of that table`
 	});
@@ -364,7 +365,9 @@ const CANONICAL_FIELDS = {
 		"name",
 		"domain",
 		"industry",
-		"size"
+		"size",
+		"email",
+		"phone"
 	],
 	deal: [
 		"name",
@@ -522,6 +525,20 @@ const entitySchema = z.strictObject({
 	/** Named relationships to other entities in this config. */
 	relationships: z.record(z.string(), relationshipSchema).optional(),
 	/**
+	* Treat rows from this entity as their company's point of contact.
+	*
+	* Opt-in, and only meaningful on a `contact` entity that resolves a company.
+	* Hosts whose schema knows who owns an account (an `owner` role on a
+	* membership table, say) can declare a narrow entity for those rows and have
+	* the CRM keep each company's point of contact current automatically.
+	*
+	* Sync only manages companies nobody has intervened on: the moment a person
+	* picks a point of contact in the CRM, that company is stamped and left
+	* alone. Without that the user's choice would be silently reverted on the
+	* next run — see `syncPrimaryContacts` and `host-owned-fields.ts`.
+	*/
+	isPrimaryContact: z.boolean().optional(),
+	/**
 	* For a "custom" entity, the crm_object_types row this materializes into.
 	* Server-generated, so pasting one into config couples the file to a
 	* specific workspace. Prefer declaring `objectType` and letting

package/dist/{entity-config-CqJknGOn.cjs → entity-config-C2sKAti2.cjs}

@@ -234,7 +234,8 @@ function checkFanOut(errors, projection, resolver, base, basePk) {
 		});
 		return;
 	}
-	if (!require_schema_meta.coversUniqueKey(joinTable, require_projection.identityRefs(projection.identity, basePk).filter((ref) => ref.table === join.key).map((ref) => ref.column))) errors.push({
+	const identityColumns = require_projection.identityRefs(projection.identity, basePk).filter((ref) => ref.table === join.key).map((ref) => ref.column);
+	if (!require_schema_meta.coversUniqueKey(joinTable, identityColumns)) errors.push({
 		path: identityPath,
 		message: `identity does not uniquely identify a row of "${joinTable.name}", which fans out — include a unique key of that table`
 	});
@@ -364,7 +365,9 @@ const CANONICAL_FIELDS = {
 		"name",
 		"domain",
 		"industry",
-		"size"
+		"size",
+		"email",
+		"phone"
 	],
 	deal: [
 		"name",
@@ -522,6 +525,20 @@ const entitySchema = zod.z.strictObject({
 	/** Named relationships to other entities in this config. */
 	relationships: zod.z.record(zod.z.string(), relationshipSchema).optional(),
 	/**
+	* Treat rows from this entity as their company's point of contact.
+	*
+	* Opt-in, and only meaningful on a `contact` entity that resolves a company.
+	* Hosts whose schema knows who owns an account (an `owner` role on a
+	* membership table, say) can declare a narrow entity for those rows and have
+	* the CRM keep each company's point of contact current automatically.
+	*
+	* Sync only manages companies nobody has intervened on: the moment a person
+	* picks a point of contact in the CRM, that company is stamped and left
+	* alone. Without that the user's choice would be silently reverted on the
+	* next run — see `syncPrimaryContacts` and `host-owned-fields.ts`.
+	*/
+	isPrimaryContact: zod.z.boolean().optional(),
+	/**
 	* For a "custom" entity, the crm_object_types row this materializes into.
 	* Server-generated, so pasting one into config couples the file to a
 	* specific workspace. Prefer declaring `objectType` and letting

package/dist/{entity-config-Ddgukq_E.d.cts → entity-config-OhC4Otkz.d.cts}

@@ -169,7 +169,7 @@ type CrmConcept = (typeof CRM_CONCEPTS)[number];
  */
 declare const CANONICAL_FIELDS: {
   readonly contact: readonly ["name", "email", "phone", "title", "status"];
-  readonly company: readonly ["name", "domain", "industry", "size"];
+  readonly company: readonly ["name", "domain", "industry", "size", "email", "phone"];
   readonly deal: readonly ["name", "value", "stage"];
 };
 /**
@@ -354,6 +354,7 @@ declare const entitySchema: z.ZodObject<{
       $raw: z.ZodString;
     }, z.core.$strict>]>;
   }, z.core.$strict>>>;
+  isPrimaryContact: z.ZodOptional<z.ZodBoolean>;
   targetObjectTypeId: z.ZodOptional<z.ZodString>;
   objectType: z.ZodOptional<z.ZodObject<{
     name: z.ZodString;
@@ -454,6 +455,7 @@ declare const entitiesConfigSchema: z.ZodObject<{
         $raw: z.ZodString;
       }, z.core.$strict>]>;
     }, z.core.$strict>>>;
+    isPrimaryContact: z.ZodOptional<z.ZodBoolean>;
     targetObjectTypeId: z.ZodOptional<z.ZodString>;
     objectType: z.ZodOptional<z.ZodObject<{
       name: z.ZodString;

package/dist/{entity-config-Ddgukq_E.d.mts → entity-config-OhC4Otkz.d.mts}

@@ -169,7 +169,7 @@ type CrmConcept = (typeof CRM_CONCEPTS)[number];
  */
 declare const CANONICAL_FIELDS: {
   readonly contact: readonly ["name", "email", "phone", "title", "status"];
-  readonly company: readonly ["name", "domain", "industry", "size"];
+  readonly company: readonly ["name", "domain", "industry", "size", "email", "phone"];
   readonly deal: readonly ["name", "value", "stage"];
 };
 /**
@@ -354,6 +354,7 @@ declare const entitySchema: z.ZodObject<{
       $raw: z.ZodString;
     }, z.core.$strict>]>;
   }, z.core.$strict>>>;
+  isPrimaryContact: z.ZodOptional<z.ZodBoolean>;
   targetObjectTypeId: z.ZodOptional<z.ZodString>;
   objectType: z.ZodOptional<z.ZodObject<{
     name: z.ZodString;
@@ -454,6 +455,7 @@ declare const entitiesConfigSchema: z.ZodObject<{
         $raw: z.ZodString;
       }, z.core.$strict>]>;
     }, z.core.$strict>>>;
+    isPrimaryContact: z.ZodOptional<z.ZodBoolean>;
     targetObjectTypeId: z.ZodOptional<z.ZodString>;
     objectType: z.ZodOptional<z.ZodObject<{
       name: z.ZodString;

package/dist/entity-config.cjs

@@ -1,5 +1,5 @@
 Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
-const require_entity_config = require("./entity-config-CqJknGOn.cjs");
+const require_entity_config = require("./entity-config-C2sKAti2.cjs");
 exports.CANONICAL_FIELDS = require_entity_config.CANONICAL_FIELDS;
 exports.CRM_CONCEPTS = require_entity_config.CRM_CONCEPTS;
 exports.CUSTOM_CONCEPT = require_entity_config.CUSTOM_CONCEPT;

package/dist/entity-config.d.cts

@@ -1,2 +1,2 @@
-import { A as relationshipsSchema, C as customObjectDeclarations, D as missingRequiredFields, E as filterSchema, M as validateEntitiesConfig, O as projectionFields, S as RelationshipsMap, T as entitiesConfigSchema, _ as MATERIALIZING_CONCEPTS, a as ClivlyEntitiesConfig, b as RelationshipSpec, c as ClivlyEntityConfigInput, d as CrmConcept, f as CustomObjectDeclaration, g as FilterValue, h as FilterExpr, i as ClivlyConfigError, j as requiredFieldsFor, k as relationshipSchema, l as ConfigValidationError, m as DiscoveredSchemaTable, n as CRM_CONCEPTS, o as ClivlyEntitiesConfigInput, p as DiscoveredColumnMeta, r as CUSTOM_CONCEPT, s as ClivlyEntityConfig, t as CANONICAL_FIELDS, u as ConfigValidationResult, v as MaterializingConcept, w as defineClivlyConfig, x as RelationshipVia, y as REQUIRED_FIELDS } from "./entity-config-Ddgukq_E.cjs";
+import { A as relationshipsSchema, C as customObjectDeclarations, D as missingRequiredFields, E as filterSchema, M as validateEntitiesConfig, O as projectionFields, S as RelationshipsMap, T as entitiesConfigSchema, _ as MATERIALIZING_CONCEPTS, a as ClivlyEntitiesConfig, b as RelationshipSpec, c as ClivlyEntityConfigInput, d as CrmConcept, f as CustomObjectDeclaration, g as FilterValue, h as FilterExpr, i as ClivlyConfigError, j as requiredFieldsFor, k as relationshipSchema, l as ConfigValidationError, m as DiscoveredSchemaTable, n as CRM_CONCEPTS, o as ClivlyEntitiesConfigInput, p as DiscoveredColumnMeta, r as CUSTOM_CONCEPT, s as ClivlyEntityConfig, t as CANONICAL_FIELDS, u as ConfigValidationResult, v as MaterializingConcept, w as defineClivlyConfig, x as RelationshipVia, y as REQUIRED_FIELDS } from "./entity-config-OhC4Otkz.cjs";
 export { CANONICAL_FIELDS, CRM_CONCEPTS, CUSTOM_CONCEPT, ClivlyConfigError, ClivlyEntitiesConfig, ClivlyEntitiesConfigInput, ClivlyEntityConfig, ClivlyEntityConfigInput, ConfigValidationError, ConfigValidationResult, CrmConcept, CustomObjectDeclaration, DiscoveredColumnMeta, DiscoveredSchemaTable, FilterExpr, FilterValue, MATERIALIZING_CONCEPTS, MaterializingConcept, REQUIRED_FIELDS, RelationshipSpec, RelationshipVia, RelationshipsMap, customObjectDeclarations, defineClivlyConfig, entitiesConfigSchema, filterSchema, missingRequiredFields, projectionFields, relationshipSchema, relationshipsSchema, requiredFieldsFor, validateEntitiesConfig };

package/dist/entity-config.d.mts

@@ -1,2 +1,2 @@
-import { A as relationshipsSchema, C as customObjectDeclarations, D as missingRequiredFields, E as filterSchema, M as validateEntitiesConfig, O as projectionFields, S as RelationshipsMap, T as entitiesConfigSchema, _ as MATERIALIZING_CONCEPTS, a as ClivlyEntitiesConfig, b as RelationshipSpec, c as ClivlyEntityConfigInput, d as CrmConcept, f as CustomObjectDeclaration, g as FilterValue, h as FilterExpr, i as ClivlyConfigError, j as requiredFieldsFor, k as relationshipSchema, l as ConfigValidationError, m as DiscoveredSchemaTable, n as CRM_CONCEPTS, o as ClivlyEntitiesConfigInput, p as DiscoveredColumnMeta, r as CUSTOM_CONCEPT, s as ClivlyEntityConfig, t as CANONICAL_FIELDS, u as ConfigValidationResult, v as MaterializingConcept, w as defineClivlyConfig, x as RelationshipVia, y as REQUIRED_FIELDS } from "./entity-config-Ddgukq_E.mjs";
+import { A as relationshipsSchema, C as customObjectDeclarations, D as missingRequiredFields, E as filterSchema, M as validateEntitiesConfig, O as projectionFields, S as RelationshipsMap, T as entitiesConfigSchema, _ as MATERIALIZING_CONCEPTS, a as ClivlyEntitiesConfig, b as RelationshipSpec, c as ClivlyEntityConfigInput, d as CrmConcept, f as CustomObjectDeclaration, g as FilterValue, h as FilterExpr, i as ClivlyConfigError, j as requiredFieldsFor, k as relationshipSchema, l as ConfigValidationError, m as DiscoveredSchemaTable, n as CRM_CONCEPTS, o as ClivlyEntitiesConfigInput, p as DiscoveredColumnMeta, r as CUSTOM_CONCEPT, s as ClivlyEntityConfig, t as CANONICAL_FIELDS, u as ConfigValidationResult, v as MaterializingConcept, w as defineClivlyConfig, x as RelationshipVia, y as REQUIRED_FIELDS } from "./entity-config-OhC4Otkz.mjs";
 export { CANONICAL_FIELDS, CRM_CONCEPTS, CUSTOM_CONCEPT, ClivlyConfigError, ClivlyEntitiesConfig, ClivlyEntitiesConfigInput, ClivlyEntityConfig, ClivlyEntityConfigInput, ConfigValidationError, ConfigValidationResult, CrmConcept, CustomObjectDeclaration, DiscoveredColumnMeta, DiscoveredSchemaTable, FilterExpr, FilterValue, MATERIALIZING_CONCEPTS, MaterializingConcept, REQUIRED_FIELDS, RelationshipSpec, RelationshipVia, RelationshipsMap, customObjectDeclarations, defineClivlyConfig, entitiesConfigSchema, filterSchema, missingRequiredFields, projectionFields, relationshipSchema, relationshipsSchema, requiredFieldsFor, validateEntitiesConfig };

package/dist/entity-config.mjs

@@ -1,2 +1,2 @@
-import { a as MATERIALIZING_CONCEPTS, c as defineClivlyConfig, d as missingRequiredFields, f as projectionFields, g as validateEntitiesConfig, h as requiredFieldsFor, i as ClivlyConfigError, l as entitiesConfigSchema, m as relationshipsSchema, n as CRM_CONCEPTS, o as REQUIRED_FIELDS, p as relationshipSchema, r as CUSTOM_CONCEPT, s as customObjectDeclarations, t as CANONICAL_FIELDS, u as filterSchema } from "./entity-config-BTAJe1Zj.mjs";
+import { a as MATERIALIZING_CONCEPTS, c as defineClivlyConfig, d as missingRequiredFields, f as projectionFields, g as validateEntitiesConfig, h as requiredFieldsFor, i as ClivlyConfigError, l as entitiesConfigSchema, m as relationshipsSchema, n as CRM_CONCEPTS, o as REQUIRED_FIELDS, p as relationshipSchema, r as CUSTOM_CONCEPT, s as customObjectDeclarations, t as CANONICAL_FIELDS, u as filterSchema } from "./entity-config-C0rtu-K_.mjs";
 export { CANONICAL_FIELDS, CRM_CONCEPTS, CUSTOM_CONCEPT, ClivlyConfigError, MATERIALIZING_CONCEPTS, REQUIRED_FIELDS, customObjectDeclarations, defineClivlyConfig, entitiesConfigSchema, filterSchema, missingRequiredFields, projectionFields, relationshipSchema, relationshipsSchema, requiredFieldsFor, validateEntitiesConfig };