evo360-types 1.3.446 → 1.3.448

package/dist/apps/evo-crm/lead/zod-schemas.d.ts

@@ -161,6 +161,31 @@ export declare const zLeadSchema: z.ZodObject<{
     }, z.ZodTypeAny, "passthrough">>>>;
     chat_contact_id: z.ZodOptional<z.ZodNullable<z.ZodUnion<[z.ZodString, z.ZodNumber]>>>;
     notes: z.ZodOptional<z.ZodNullable<z.ZodString>>;
+    /**
+     * Vínculos com outros objetos do sistema. O par lead↔paciente é gravado nos
+     * DOIS lados: aqui entram `{ type: 'med_patient', id, label: display_name do
+     * paciente }` e, no paciente, `{ type: 'crm_lead', id, label: display_name do
+     * lead }`. É N↔N: um lead pode ter vários pacientes (ex.: mãe que agenda para
+     * a família inteira) e um paciente pode responder a vários leads. feat-095.
+     */
+    externalLinks: z.ZodOptional<z.ZodArray<z.ZodObject<{
+        type: z.ZodEnum<["crm_lead", "med_patient", "med_professional", "med_appointment", "chat_contact", "evo_task", "campaign"]>;
+        id: z.ZodString;
+        label: z.ZodOptional<z.ZodString>;
+        ref: z.ZodOptional<z.ZodAny>;
+    }, "passthrough", z.ZodTypeAny, z.objectOutputType<{
+        type: z.ZodEnum<["crm_lead", "med_patient", "med_professional", "med_appointment", "chat_contact", "evo_task", "campaign"]>;
+        id: z.ZodString;
+        label: z.ZodOptional<z.ZodString>;
+        ref: z.ZodOptional<z.ZodAny>;
+    }, z.ZodTypeAny, "passthrough">, z.objectInputType<{
+        type: z.ZodEnum<["crm_lead", "med_patient", "med_professional", "med_appointment", "chat_contact", "evo_task", "campaign"]>;
+        id: z.ZodString;
+        label: z.ZodOptional<z.ZodString>;
+        ref: z.ZodOptional<z.ZodAny>;
+    }, z.ZodTypeAny, "passthrough">>, "many">>;
+    /** Derivado de `externalLinks` (`"type:id"`) pelo model — habilita `array-contains`. */
+    externalLinkKeys: z.ZodOptional<z.ZodArray<z.ZodString, "many">>;
     tags: z.ZodOptional<z.ZodNullable<z.ZodArray<z.ZodObject<{
         name: z.ZodString;
         color: z.ZodOptional<z.ZodString>;
@@ -307,6 +332,31 @@ export declare const zLeadSchema: z.ZodObject<{
     }, z.ZodTypeAny, "passthrough">>>>;
     chat_contact_id: z.ZodOptional<z.ZodNullable<z.ZodUnion<[z.ZodString, z.ZodNumber]>>>;
     notes: z.ZodOptional<z.ZodNullable<z.ZodString>>;
+    /**
+     * Vínculos com outros objetos do sistema. O par lead↔paciente é gravado nos
+     * DOIS lados: aqui entram `{ type: 'med_patient', id, label: display_name do
+     * paciente }` e, no paciente, `{ type: 'crm_lead', id, label: display_name do
+     * lead }`. É N↔N: um lead pode ter vários pacientes (ex.: mãe que agenda para
+     * a família inteira) e um paciente pode responder a vários leads. feat-095.
+     */
+    externalLinks: z.ZodOptional<z.ZodArray<z.ZodObject<{
+        type: z.ZodEnum<["crm_lead", "med_patient", "med_professional", "med_appointment", "chat_contact", "evo_task", "campaign"]>;
+        id: z.ZodString;
+        label: z.ZodOptional<z.ZodString>;
+        ref: z.ZodOptional<z.ZodAny>;
+    }, "passthrough", z.ZodTypeAny, z.objectOutputType<{
+        type: z.ZodEnum<["crm_lead", "med_patient", "med_professional", "med_appointment", "chat_contact", "evo_task", "campaign"]>;
+        id: z.ZodString;
+        label: z.ZodOptional<z.ZodString>;
+        ref: z.ZodOptional<z.ZodAny>;
+    }, z.ZodTypeAny, "passthrough">, z.objectInputType<{
+        type: z.ZodEnum<["crm_lead", "med_patient", "med_professional", "med_appointment", "chat_contact", "evo_task", "campaign"]>;
+        id: z.ZodString;
+        label: z.ZodOptional<z.ZodString>;
+        ref: z.ZodOptional<z.ZodAny>;
+    }, z.ZodTypeAny, "passthrough">>, "many">>;
+    /** Derivado de `externalLinks` (`"type:id"`) pelo model — habilita `array-contains`. */
+    externalLinkKeys: z.ZodOptional<z.ZodArray<z.ZodString, "many">>;
     tags: z.ZodOptional<z.ZodNullable<z.ZodArray<z.ZodObject<{
         name: z.ZodString;
         color: z.ZodOptional<z.ZodString>;
@@ -453,6 +503,31 @@ export declare const zLeadSchema: z.ZodObject<{
     }, z.ZodTypeAny, "passthrough">>>>;
     chat_contact_id: z.ZodOptional<z.ZodNullable<z.ZodUnion<[z.ZodString, z.ZodNumber]>>>;
     notes: z.ZodOptional<z.ZodNullable<z.ZodString>>;
+    /**
+     * Vínculos com outros objetos do sistema. O par lead↔paciente é gravado nos
+     * DOIS lados: aqui entram `{ type: 'med_patient', id, label: display_name do
+     * paciente }` e, no paciente, `{ type: 'crm_lead', id, label: display_name do
+     * lead }`. É N↔N: um lead pode ter vários pacientes (ex.: mãe que agenda para
+     * a família inteira) e um paciente pode responder a vários leads. feat-095.
+     */
+    externalLinks: z.ZodOptional<z.ZodArray<z.ZodObject<{
+        type: z.ZodEnum<["crm_lead", "med_patient", "med_professional", "med_appointment", "chat_contact", "evo_task", "campaign"]>;
+        id: z.ZodString;
+        label: z.ZodOptional<z.ZodString>;
+        ref: z.ZodOptional<z.ZodAny>;
+    }, "passthrough", z.ZodTypeAny, z.objectOutputType<{
+        type: z.ZodEnum<["crm_lead", "med_patient", "med_professional", "med_appointment", "chat_contact", "evo_task", "campaign"]>;
+        id: z.ZodString;
+        label: z.ZodOptional<z.ZodString>;
+        ref: z.ZodOptional<z.ZodAny>;
+    }, z.ZodTypeAny, "passthrough">, z.objectInputType<{
+        type: z.ZodEnum<["crm_lead", "med_patient", "med_professional", "med_appointment", "chat_contact", "evo_task", "campaign"]>;
+        id: z.ZodString;
+        label: z.ZodOptional<z.ZodString>;
+        ref: z.ZodOptional<z.ZodAny>;
+    }, z.ZodTypeAny, "passthrough">>, "many">>;
+    /** Derivado de `externalLinks` (`"type:id"`) pelo model — habilita `array-contains`. */
+    externalLinkKeys: z.ZodOptional<z.ZodArray<z.ZodString, "many">>;
     tags: z.ZodOptional<z.ZodNullable<z.ZodArray<z.ZodObject<{
         name: z.ZodString;
         color: z.ZodOptional<z.ZodString>;

package/dist/apps/evo-crm/lead/zod-schemas.js

@@ -4,12 +4,13 @@ exports.zLeadSchema = exports.zLeadReactivationSchema = exports.zLeadDistChannel
 const zod_1 = require("zod");
 const zod_schemas_1 = require("../../shared/zod-schemas");
 const zod_schemas_2 = require("../../evo-people/zod-schemas");
-const zod_schemas_3 = require("../dic/zod-schemas");
+const zod_schemas_3 = require("../../evo-task/zod-schemas");
+const zod_schemas_4 = require("../dic/zod-schemas");
 exports.zLeadStatusSchema = zod_1.z.enum(["active", "inactive", "draft"]);
 exports.zLeadQualificationSchema = zod_1.z.object({
     code: zod_1.z.string().min(1).max(20),
     name: zod_1.z.string().min(1).max(255),
-    funnelLevel: zod_schemas_3.zQualificationFunnelLevelSchema,
+    funnelLevel: zod_schemas_4.zQualificationFunnelLevelSchema,
     ref: zod_1.z.any(),
     updated_at: zod_1.z.coerce.date().nullable().optional(),
 });
@@ -38,6 +39,16 @@ exports.zLeadSchema = zod_schemas_2.zProfileSchema // Extend from ProfileSchema
     contact: zod_schemas_1.zContactSchema.nullable().optional(),
     chat_contact_id: zod_1.z.string().or(zod_1.z.number()).nullable().optional(),
     notes: zod_1.z.string().nullable().optional(),
+    /**
+     * Vínculos com outros objetos do sistema. O par lead↔paciente é gravado nos
+     * DOIS lados: aqui entram `{ type: 'med_patient', id, label: display_name do
+     * paciente }` e, no paciente, `{ type: 'crm_lead', id, label: display_name do
+     * lead }`. É N↔N: um lead pode ter vários pacientes (ex.: mãe que agenda para
+     * a família inteira) e um paciente pode responder a vários leads. feat-095.
+     */
+    externalLinks: zod_1.z.array(zod_schemas_3.zExternalLinkSchema).optional(),
+    /** Derivado de `externalLinks` (`"type:id"`) pelo model — habilita `array-contains`. */
+    externalLinkKeys: zod_1.z.array(zod_1.z.string()).optional(),
     tags: zod_1.z.array(zod_schemas_1.zTagSchema).nullable().optional(),
     userRef: zod_1.z.any(),
     reactivation: exports.zLeadReactivationSchema.nullable().optional(),

package/dist/apps/evo-crm/lead/zod-schemas.ts

@@ -5,6 +5,7 @@ import {
   zTagSchema,
 } from "../../shared/zod-schemas";
 import { zProfileSchema } from "../../evo-people/zod-schemas";
+import { zExternalLinkSchema } from "../../evo-task/zod-schemas";
 import { zQualificationFunnelLevelSchema } from "../dic/zod-schemas";
 
 export const zLeadStatusSchema = z.enum(["active", "inactive", "draft"]);
@@ -44,6 +45,16 @@ export const zLeadSchema = zProfileSchema // Extend from ProfileSchema
     contact: zContactSchema.nullable().optional(),
     chat_contact_id: z.string().or(z.number()).nullable().optional(),
     notes: z.string().nullable().optional(),
+    /**
+     * Vínculos com outros objetos do sistema. O par lead↔paciente é gravado nos
+     * DOIS lados: aqui entram `{ type: 'med_patient', id, label: display_name do
+     * paciente }` e, no paciente, `{ type: 'crm_lead', id, label: display_name do
+     * lead }`. É N↔N: um lead pode ter vários pacientes (ex.: mãe que agenda para
+     * a família inteira) e um paciente pode responder a vários leads. feat-095.
+     */
+    externalLinks: z.array(zExternalLinkSchema).optional(),
+    /** Derivado de `externalLinks` (`"type:id"`) pelo model — habilita `array-contains`. */
+    externalLinkKeys: z.array(z.string()).optional(),
     tags: z.array(zTagSchema).nullable().optional(),
     userRef: z.any(),
     reactivation: zLeadReactivationSchema.nullable().optional(),

package/dist/types/evo-crm/lead/index.d.ts

@@ -1,5 +1,5 @@
 export * from "../fb_collections";
-import { FirestoreDocumentReference, IAddress, IContact, ITag } from "../../shared";
+import { FirestoreDocumentReference, IAddress, IContact, IExternalLink, ITag } from "../../shared";
 import { IProfile } from "../../evo-people";
 import { QualificationFunnelLevel } from "../dic";
 export declare const EvoCrmLeadPermissions: {
@@ -101,6 +101,16 @@ export interface ILead extends IProfile {
     contact?: IContact | null;
     chat_contact_id?: string | number | null;
     notes?: string | null;
+    /**
+     * Vínculos com outros objetos do sistema. O par lead↔paciente é gravado nos
+     * DOIS lados: aqui entram `{ type: 'med_patient', id, label: display_name do
+     * paciente }` e, no paciente, `{ type: 'crm_lead', id, label: display_name do
+     * lead }`. É N↔N: um lead pode ter vários pacientes (ex.: mãe que agenda para
+     * a família inteira) e um paciente pode responder a vários leads. feat-095.
+     */
+    externalLinks?: IExternalLink[];
+    /** Derivado de `externalLinks` (`"type:id"`) pelo model — habilita `array-contains`. */
+    externalLinkKeys?: string[];
     tags?: ITag[] | null;
     userRef?: FirestoreDocumentReference;
     ctwa_clid?: string | null;

package/dist/types/evo-crm/lead/index.ts

@@ -4,6 +4,7 @@ import {
   FirestoreDocumentReference,
   IAddress,
   IContact,
+  IExternalLink,
   ITag,
 } from "../../shared";
 import { IProfile } from "../../evo-people";
@@ -142,6 +143,16 @@ export interface ILead extends IProfile {
   contact?: IContact | null;
   chat_contact_id?: string | number | null;
   notes?: string | null; // Anotações sobre o lead
+  /**
+   * Vínculos com outros objetos do sistema. O par lead↔paciente é gravado nos
+   * DOIS lados: aqui entram `{ type: 'med_patient', id, label: display_name do
+   * paciente }` e, no paciente, `{ type: 'crm_lead', id, label: display_name do
+   * lead }`. É N↔N: um lead pode ter vários pacientes (ex.: mãe que agenda para
+   * a família inteira) e um paciente pode responder a vários leads. feat-095.
+   */
+  externalLinks?: IExternalLink[];
+  /** Derivado de `externalLinks` (`"type:id"`) pelo model — habilita `array-contains`. */
+  externalLinkKeys?: string[];
   tags?: ITag[] | null;
   userRef?: FirestoreDocumentReference;
   // CTWA attribution (feat-034) — capturado do referral do 1º inbound vindo de anúncio Click-to-WhatsApp.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "evo360-types",
-  "version": "1.3.446",
+  "version": "1.3.448",
   "description": "HREVO360 Shared Types",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",