evo360-types 1.3.465 → 1.3.469

package/dist/types/evo-med/calendar/index.d.ts

@@ -97,6 +97,19 @@ export declare const MedCalendarNotificationConfigKeys: {
     readonly AppointmentCreated: "appointment_created";
     readonly AppointmentRescheduled: "appointment_rescheduled";
     readonly AppointmentCancelled: "appointment_cancelled";
+    /**
+     * feat-107 — ciclo FINANCEIRO da consulta, na ordem em que acontece:
+     *
+     * `appointment_payment` ...... cobrança: manda o LINK de pagamento; o paciente
+     *                              ainda vai pagar.
+     * `appointment_payment_done` . agradecimento/confirmação, disparado depois que o
+     *                              sistema DETECTA o pagamento.
+     * `appointment_invoice` ...... nota fiscal já EMITIDA: manda o PDF da NF ao
+     *                              paciente (template com header de documento).
+     */
+    readonly AppointmentPayment: "appointment_payment";
+    readonly AppointmentPaymentDone: "appointment_payment_done";
+    readonly AppointmentInvoice: "appointment_invoice";
 };
 export type MedCalendarNotificationConfigKey = (typeof MedCalendarNotificationConfigKeys)[keyof typeof MedCalendarNotificationConfigKeys];
 export interface IMedCalendar extends IFireDoc {

package/dist/types/evo-med/calendar/index.js

@@ -40,4 +40,17 @@ exports.MedCalendarNotificationConfigKeys = {
     AppointmentCreated: "appointment_created",
     AppointmentRescheduled: "appointment_rescheduled",
     AppointmentCancelled: "appointment_cancelled",
+    /**
+     * feat-107 — ciclo FINANCEIRO da consulta, na ordem em que acontece:
+     *
+     * `appointment_payment` ...... cobrança: manda o LINK de pagamento; o paciente
+     *                              ainda vai pagar.
+     * `appointment_payment_done` . agradecimento/confirmação, disparado depois que o
+     *                              sistema DETECTA o pagamento.
+     * `appointment_invoice` ...... nota fiscal já EMITIDA: manda o PDF da NF ao
+     *                              paciente (template com header de documento).
+     */
+    AppointmentPayment: "appointment_payment",
+    AppointmentPaymentDone: "appointment_payment_done",
+    AppointmentInvoice: "appointment_invoice",
 };

package/dist/types/evo-med/calendar/index.ts

@@ -115,6 +115,19 @@ export const MedCalendarNotificationConfigKeys = {
   AppointmentCreated: "appointment_created",
   AppointmentRescheduled: "appointment_rescheduled",
   AppointmentCancelled: "appointment_cancelled",
+  /**
+   * feat-107 — ciclo FINANCEIRO da consulta, na ordem em que acontece:
+   *
+   * `appointment_payment` ...... cobrança: manda o LINK de pagamento; o paciente
+   *                              ainda vai pagar.
+   * `appointment_payment_done` . agradecimento/confirmação, disparado depois que o
+   *                              sistema DETECTA o pagamento.
+   * `appointment_invoice` ...... nota fiscal já EMITIDA: manda o PDF da NF ao
+   *                              paciente (template com header de documento).
+   */
+  AppointmentPayment: "appointment_payment",
+  AppointmentPaymentDone: "appointment_payment_done",
+  AppointmentInvoice: "appointment_invoice",
 } as const;
 
 export type MedCalendarNotificationConfigKey =

package/dist/types/evo-task/index.d.ts

@@ -55,6 +55,7 @@ export declare const TaskAutoHandlerEnum: {
     readonly LeadReactivation: "lead_reactivation";
     readonly AppointmentAction: "appointment_action";
     readonly AppointmentReminder: "appointment_reminder";
+    readonly AppointmentConfirmation: "appointment_confirmation";
     readonly IntegrationsSyncRun: "evo-integrations.sync-run";
     readonly CampaignMaterialize: "campaign.materialize";
     readonly CampaignDispatchBatch: "campaign.dispatch_batch";

package/dist/types/evo-task/index.js

@@ -98,6 +98,11 @@ exports.TaskAutoHandlerEnum = {
     // por canal habilitado (WhatsApp/e-mail), com quick-reply de confirmar/remarcar.
     // Tópico PubSub do executor: `appointment_reminder.execute_requests`.
     AppointmentReminder: "appointment_reminder",
+    // feat-102: PEDIDO de confirmação de consulta — mesmo fan-out do lembrete, mas
+    // lendo `notification_config.configs.appointment_confirmation` (feat-100). Envia o
+    // HSM com CTAs de confirmar/remarcar. Tópico: `appointment_confirmation.execute_requests`.
+    // Espelhado à mão em `zTaskAutoHandlerSchema` — sem lá, criar a task estoura ZodError.
+    AppointmentConfirmation: "appointment_confirmation",
     // feat-078: handler que roda um sync de agenda do evo-integrations. O valor
     // é o nome do handler COM ponto de propósito — `resolveHandlerTopic` faz
     // `${handler}.execute_requests`, e a CF `integrations_sync` já escuta

package/dist/types/evo-task/index.ts

@@ -109,6 +109,11 @@ export const TaskAutoHandlerEnum = {
   // por canal habilitado (WhatsApp/e-mail), com quick-reply de confirmar/remarcar.
   // Tópico PubSub do executor: `appointment_reminder.execute_requests`.
   AppointmentReminder: "appointment_reminder",
+  // feat-102: PEDIDO de confirmação de consulta — mesmo fan-out do lembrete, mas
+  // lendo `notification_config.configs.appointment_confirmation` (feat-100). Envia o
+  // HSM com CTAs de confirmar/remarcar. Tópico: `appointment_confirmation.execute_requests`.
+  // Espelhado à mão em `zTaskAutoHandlerSchema` — sem lá, criar a task estoura ZodError.
+  AppointmentConfirmation: "appointment_confirmation",
   // feat-078: handler que roda um sync de agenda do evo-integrations. O valor
   // é o nome do handler COM ponto de propósito — `resolveHandlerTopic` faz
   // `${handler}.execute_requests`, e a CF `integrations_sync` já escuta

package/package.json

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