evo360-types 1.3.463 → 1.3.467

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -55,6 +55,7 @@ export declare const TaskAutoHandlerEnum: {
55
55
  readonly LeadReactivation: "lead_reactivation";
56
56
  readonly AppointmentAction: "appointment_action";
57
57
  readonly AppointmentReminder: "appointment_reminder";
58
+ readonly AppointmentConfirmation: "appointment_confirmation";
58
59
  readonly IntegrationsSyncRun: "evo-integrations.sync-run";
59
60
  readonly CampaignMaterialize: "campaign.materialize";
60
61
  readonly CampaignDispatchBatch: "campaign.dispatch_batch";
@@ -98,6 +98,11 @@ exports.TaskAutoHandlerEnum = {
98
98
  // por canal habilitado (WhatsApp/e-mail), com quick-reply de confirmar/remarcar.
99
99
  // Tópico PubSub do executor: `appointment_reminder.execute_requests`.
100
100
  AppointmentReminder: "appointment_reminder",
101
+ // feat-102: PEDIDO de confirmação de consulta — mesmo fan-out do lembrete, mas
102
+ // lendo `notification_config.configs.appointment_confirmation` (feat-100). Envia o
103
+ // HSM com CTAs de confirmar/remarcar. Tópico: `appointment_confirmation.execute_requests`.
104
+ // Espelhado à mão em `zTaskAutoHandlerSchema` — sem lá, criar a task estoura ZodError.
105
+ AppointmentConfirmation: "appointment_confirmation",
101
106
  // feat-078: handler que roda um sync de agenda do evo-integrations. O valor
102
107
  // é o nome do handler COM ponto de propósito — `resolveHandlerTopic` faz
103
108
  // `${handler}.execute_requests`, e a CF `integrations_sync` já escuta
@@ -109,6 +109,11 @@ export const TaskAutoHandlerEnum = {
109
109
  // por canal habilitado (WhatsApp/e-mail), com quick-reply de confirmar/remarcar.
110
110
  // Tópico PubSub do executor: `appointment_reminder.execute_requests`.
111
111
  AppointmentReminder: "appointment_reminder",
112
+ // feat-102: PEDIDO de confirmação de consulta — mesmo fan-out do lembrete, mas
113
+ // lendo `notification_config.configs.appointment_confirmation` (feat-100). Envia o
114
+ // HSM com CTAs de confirmar/remarcar. Tópico: `appointment_confirmation.execute_requests`.
115
+ // Espelhado à mão em `zTaskAutoHandlerSchema` — sem lá, criar a task estoura ZodError.
116
+ AppointmentConfirmation: "appointment_confirmation",
112
117
  // feat-078: handler que roda um sync de agenda do evo-integrations. O valor
113
118
  // é o nome do handler COM ponto de propósito — `resolveHandlerTopic` faz
114
119
  // `${handler}.execute_requests`, e a CF `integrations_sync` já escuta
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "evo360-types",
3
- "version": "1.3.463",
3
+ "version": "1.3.467",
4
4
  "description": "HREVO360 Shared Types",
5
5
  "main": "./dist/index.js",
6
6
  "types": "./dist/index.d.ts",