clivly 0.11.0-next.0 → 0.12.0

package/{entity-config-EZg9BtqD.cjs → entity-config-BI4RYNKL.cjs}

@@ -1,4 +1,4 @@
-const require_projection = require("./projection-Dz6_i1-w.cjs");
+const require_projection = require("./projection-BELgANG2.cjs");
 //#region ../core/src/schema-meta.ts
 /**
 * Accessors over a discovered table's schema-v2 metadata.
@@ -407,7 +407,9 @@ const CANONICAL_FIELDS = {
 		"name",
 		"domain",
 		"industry",
-		"size"
+		"size",
+		"email",
+		"phone"
 	],
 	deal: [
 		"name",
@@ -565,6 +567,20 @@ const entitySchema = require_projection.strictObject({
 	/** Named relationships to other entities in this config. */
 	relationships: require_projection.record(require_projection.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: require_projection.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