@vitrina/api 15.16.0 → 15.18.0

package/dist/index.d.cts

@@ -22035,7 +22035,7 @@ interface paths {
         put?: never;
         /**
          * Submit a website buyer inquiry (dealer-website write API)
-         * @description Creates a CRM lead with `website` origin, attaching the inquired Vehículo when `vehicle_id` is given. A proyecto form (Módulo Proyectos) sends `project_id` and/or `unit_model_id` (a tipología names its proyecto): the lead lands on the proyecto, is routed to its ejecutivos, and `message` becomes optional. `attribution` carries the visitor's `first_touch` and `last_touch` (utm_*, gclid, fbclid, anonymous_id); both are kept on the lead. Requires the write-only `leads:intake` scope (never `leads:write`). Returns a minimized `{ status }` ack — `received` on create, `duplicate` on dedup — and echoes no internal ids. Rate-limited like every authenticated endpoint; a hidden `hp_website` honeypot field silently drops spam.
+         * @description Creates a CRM lead with `website` origin, attaching the inquired Vehículo when `vehicle_id` is given. A proyecto form (Módulo Proyectos) sends `project_id` and/or `unit_model_id` (a tipología names its proyecto): the lead lands on the proyecto, is routed to its ejecutivos, and `message` becomes optional. `attribution` carries the visitor's `first_touch` and `last_touch` (utm_*, gclid, fbclid, anonymous_id); both are kept on the lead. `value_amount` is the lead's value; `quote_amount` is a figure the site quoted that is not the deal (a trade-in quote): it only fills the first-touch template's amount and the inbox card when `value_amount` is absent, and is never stored as the lead's value. Requires the write-only `leads:intake` scope (never `leads:write`). Returns a minimized `{ status }` ack — `received` on create, `duplicate` on dedup — and echoes no internal ids. Rate-limited like every authenticated endpoint; a hidden `hp_website` honeypot field silently drops spam.
          */
         post: {
             parameters: {
@@ -22101,6 +22101,7 @@ interface paths {
                         stage_id?: string;
                         value_amount?: number;
                         value_currency?: string;
+                        quote_amount?: number;
                         item_label?: string;
                         source_ref?: string;
                         fields?: {
@@ -88530,6 +88531,272 @@ interface paths {
         patch?: never;
         trace?: never;
     };
+    "/finanzas/contador-export": {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        /**
+         * Download the Contador package for a month (zip)
+         * @description One zip, `paquete-contador-<period>.zip`, with seven xlsx: `01-libro-de-compras`, `02-libro-de-ventas`, `03-honorarios`, `04-movimientos-por-cuenta` (one sheet per bank account), `05-clasificaciones-por-cuenta` (net, as the Resultado counts), `06-resultado` and `07-ajustes-posteriores-al-cierre`, each `<name>-<period>.xlsx`, built by the same code as each screen and its export. Read-only. A caller without the patient register (the Contador) sees a patient as «Paciente A. P.» with no RUT; the libro de ventas keeps the patient RUT on facturas and on notas de crédito or débito that cite one, and boletas carry neither RUT nor name. Requires the `finanzas` add-on — without it every Finanzas operation answers `402 ENTITLEMENT_NOT_ACTIVE` (`details.required = ["finanzas"]`). Requires `finanzas:read`, `finanzas_reports:read` and `finanzas:export` (the Contador seat, owners and admins).
+         */
+        get: {
+            parameters: {
+                query?: {
+                    period?: string;
+                };
+                header?: never;
+                path?: never;
+                cookie?: never;
+            };
+            requestBody?: never;
+            responses: {
+                /** @description The package, as an attachment */
+                200: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/zip": string;
+                    };
+                };
+                /** @description Validation error */
+                400: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+                /** @description Unauthorized */
+                401: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+                /** @description Forbidden */
+                403: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+                /** @description Not found */
+                404: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+                /** @description Conflict (incl. Idempotency-Key reuse with different body) */
+                409: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+                /** @description Rate limited */
+                429: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+            };
+        };
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
+    "/finanzas/contador-export/manifest": {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        /**
+         * What the Contador package for a month holds
+         * @description The same package as the download, without the bytes: the period, the zip name and each file (key, label, name, rows, size). Over MCP this is the read that generates and checks the package; the zip itself downloads over HTTPS. A caller without the patient register (the Contador) sees a patient as «Paciente A. P.» with no RUT; the libro de ventas keeps the patient RUT on facturas and on notas de crédito or débito that cite one, and boletas carry neither RUT nor name. Requires the `finanzas` add-on — without it every Finanzas operation answers `402 ENTITLEMENT_NOT_ACTIVE` (`details.required = ["finanzas"]`). Requires `finanzas:read`, `finanzas_reports:read` and `finanzas:export` (the Contador seat, owners and admins).
+         */
+        get: {
+            parameters: {
+                query?: {
+                    period?: string;
+                };
+                header?: never;
+                path?: never;
+                cookie?: never;
+            };
+            requestBody?: never;
+            responses: {
+                /** @description The manifest */
+                200: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        /**
+                         * @example {
+                         *       "data": {
+                         *         "period": "2026-09",
+                         *         "filename": "paquete-contador-2026-09.zip",
+                         *         "files": [
+                         *           {
+                         *             "key": "libro_compras",
+                         *             "label": "Libro de compras",
+                         *             "filename": "01-libro-de-compras-2026-09.xlsx",
+                         *             "rows": 84,
+                         *             "size_bytes": 14210
+                         *           },
+                         *           {
+                         *             "key": "libro_ventas",
+                         *             "label": "Libro de ventas",
+                         *             "filename": "02-libro-de-ventas-2026-09.xlsx",
+                         *             "rows": 1312,
+                         *             "size_bytes": 61904
+                         *           },
+                         *           {
+                         *             "key": "honorarios",
+                         *             "label": "Honorarios",
+                         *             "filename": "03-honorarios-2026-09.xlsx",
+                         *             "rows": 12,
+                         *             "size_bytes": 7480
+                         *           },
+                         *           {
+                         *             "key": "movimientos",
+                         *             "label": "Movimientos por cuenta",
+                         *             "filename": "04-movimientos-por-cuenta-2026-09.xlsx",
+                         *             "rows": 640,
+                         *             "size_bytes": 38112
+                         *           },
+                         *           {
+                         *             "key": "clasificaciones",
+                         *             "label": "Clasificaciones por cuenta",
+                         *             "filename": "05-clasificaciones-por-cuenta-2026-09.xlsx",
+                         *             "rows": 702,
+                         *             "size_bytes": 40356
+                         *           },
+                         *           {
+                         *             "key": "resultado",
+                         *             "label": "Resultado",
+                         *             "filename": "06-resultado-2026-09.xlsx",
+                         *             "rows": 1398,
+                         *             "size_bytes": 52018
+                         *           },
+                         *           {
+                         *             "key": "ajustes",
+                         *             "label": "Ajustes posteriores al cierre",
+                         *             "filename": "07-ajustes-posteriores-al-cierre-2026-09.xlsx",
+                         *             "rows": 3,
+                         *             "size_bytes": 6920
+                         *           }
+                         *         ]
+                         *       }
+                         *     }
+                         */
+                        "application/json": {
+                            data: {
+                                /** @description The month, `YYYY-MM`. */
+                                period: string;
+                                /** @description The zip the download serves. */
+                                filename: string;
+                                files: {
+                                    /** @enum {string} */
+                                    key: "libro_compras" | "libro_ventas" | "honorarios" | "movimientos" | "clasificaciones" | "resultado" | "ajustes";
+                                    label: string;
+                                    /** @description The xlsx inside the zip. */
+                                    filename: string;
+                                    /** @description Rows of its «Detalle» sheet (documents, items) when it has one, else of its first sheet (movements, adjustments). */
+                                    rows: number;
+                                    size_bytes: number;
+                                }[];
+                            };
+                        };
+                    };
+                };
+                /** @description Validation error */
+                400: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+                /** @description Unauthorized */
+                401: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+                /** @description Forbidden */
+                403: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+                /** @description Not found */
+                404: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+                /** @description Conflict (incl. Idempotency-Key reuse with different body) */
+                409: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+                /** @description Rate limited */
+                429: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+            };
+        };
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
     "/clinic/evidence-cards": {
         parameters: {
             query?: never;
@@ -139133,6 +139400,8 @@ interface paths {
          *
          *     Each row also carries `campaign_origin` — the newest campaign send stored in the thread (`null` when none): its campaign, when it left, whether the send created the thread, and whether it is still the newest message (`awaiting_reply`). `fromCampaign=true` lists every such thread, closed ones included.
          *
+         *     Each row also carries `waiting_since` — when its customer started waiting on a human, `null` when nobody waits (the «Esperando respuesta» rule; see the `waiting` parameter). `waiting=true` lists only waiting conversations, team-wide; `sort=wait` orders urgent first, then the longest wait.
+         *
          *     Rows here do NOT carry `ad_origin_nudge` — that field is single-conversation-read only, to avoid a per-row integration lookup on every page of the inbox.
          *
          *     `fields=summary` answers the SAME page with only the identifying and funnel scalars per row — `id`, `display_id`, `channel`, `source`, `status`, `handler`, `assignee_user_id`, `contact_id`, `ticket_id`, `awaiting_human_since`, `first_ai_message_at`, `last_message_date`, `created_at`, `ad_origin` — plus `contact_name`, `ticket_status` and `current_stage_id` off the embeds, and `assignee_name` / `unread` when the list computed them (an api_key has no read markers, so no `unread`). No `contact`, `ticket`, `lastMessage`, `tags`, `marketplaceWindow` or `last_call`. `meta` and `counts` are unchanged. A 20-row page is ~147k characters at `full` (the default, byte-identical to omitting the parameter) and a fraction of that at `summary`; page with `summary` to choose, then `GET /conversations/{id}` for one thread whole.
@@ -139164,7 +139433,10 @@ interface paths {
                     aiReplied?: boolean | null;
                     fromAd?: boolean | null;
                     fromCampaign?: boolean | null;
-                    sort?: "created_at" | "updated_at" | "last_message_date";
+                    /** @description true: only conversations where a customer is waiting on a human («Esperando respuesta»), team-wide. Waiting = open or pending, not filtered, on a channel you can reply in, and either an AI handoff nobody on the team has answered yet (a reply from ANY teammate clears it, including WhatsApp Business / Instagram app replies; a silent «Visita acordada» notice needs no answer) or a human-handled thread whose last message is the customer’s; waits older than 7 days are left out. Each row carries `waiting_since`. Pair with `sort=wait` for the queue order. */
+                    waiting?: boolean | null;
+                    /** @description `wait`: urgent (`handoff_urgent`) first, then by `waiting_since` — `order=desc` (default) is the longest wait first, `asc` the newest; conversations that are not waiting go last. */
+                    sort?: "created_at" | "updated_at" | "last_message_date" | "wait";
                     order?: "asc" | "desc";
                     include?: "counts";
                     /** @description `full` (default): the inbox row with its `contact`, `ticket`, `lastMessage`, `tags`, `marketplaceWindow`, `ad_origin` and `last_call`, exactly as without the parameter. `summary`: only the identifying and funnel scalars — `id`, `display_id`, `channel`, `source`, `status`, `handler`, `assignee_user_id`, `contact_id`, `ticket_id`, `awaiting_human_since`, `first_ai_message_at`, `last_message_date`, `created_at`, `ad_origin`, plus `contact_name`, `ticket_status`, `current_stage_id` off the embeds and `assignee_name` / `unread` when the list computed them. Pagination, `meta` and `counts` are unchanged. Use `summary` to page the inbox cheaply, then `GET /conversations/{id}` for one thread in full. */
@@ -139303,7 +139575,8 @@ interface paths {
                          *             }
                          *           ],
                          *           "last_call": null,
-                         *           "handoff_urgent": false
+                         *           "handoff_urgent": false,
+                         *           "waiting_since": null
                          *         },
                          *         {
                          *           "id": "bbbbbbbb-0000-4000-8000-000000000002",
@@ -139440,7 +139713,8 @@ interface paths {
                          *           },
                          *           "tags": [],
                          *           "last_call": null,
-                         *           "handoff_urgent": false
+                         *           "handoff_urgent": false,
+                         *           "waiting_since": null
                          *         }
                          *       ],
                          *       "meta": {
@@ -139729,9 +140003,11 @@ interface paths {
             cookie?: never;
         };
         /**
-         * Inbox badge counts (my open / unread / mentions / unassigned)
+         * Inbox badge counts (my open / unread / mentions / unassigned / waiting)
          * @description The four badge counts on their own, scoped to the calling principal: `myOpen` and `myUnread` are the conversations assigned to the member behind the credential, `myMentions` the ones that @-mention them, `unassigned` the whole workspace’s unowned queue. An API key has no member behind it, so its three "my" counts read 0 and only `unassigned` is meaningful — use a personal token to get a person’s badges.
          *
+         *     «Esperando respuesta» (the waiting queue): `waiting` is how many conversations have a customer waiting on a human, team-wide (the list `GET /conversations?waiting=true` returns exactly these); `waitingUrgent` how many of them are flagged urgent; `waitingMine` how many are assigned to the caller (0 for an API key); `waitingOldestSince` when the longest wait started (ISO, `null` when nobody waits) — render it as «el más antiguo 2 h».
+         *
          *     `GET /conversations?include=counts` returns the same payload beside a page of conversations; this route exists for the caller that wants the badges without one.
          */
         get: {
@@ -139755,7 +140031,11 @@ interface paths {
                          *         "myOpen": 3,
                          *         "myUnread": 1,
                          *         "unassigned": 2,
-                         *         "myMentions": 0
+                         *         "myMentions": 0,
+                         *         "waiting": 3,
+                         *         "waitingUrgent": 1,
+                         *         "waitingMine": 1,
+                         *         "waitingOldestSince": "2026-10-31T13:05:00.000Z"
                          *       }
                          *     }
                          */
@@ -139994,6 +140274,7 @@ interface paths {
                          *         ],
                          *         "last_call": null,
                          *         "handoff_urgent": false,
+                         *         "waiting_since": null,
                          *         "ad_origin_nudge": null,
                          *         "handoff_resolved_suggested": false,
                          *         "message": [
@@ -237685,6 +237966,8 @@ interface paths {
          * This car’s lead timeline
          * @description Every named lead that asked about this vehicle, merged with its anonymous Yapo phone-reveals, newest first. This is the car’s HISTORY, so unlike `/interest` a sold vehicle keeps its timeline.
          *
+         *     Each lead row carries `conversation_id`: the chat to open for that person (the lead's own conversation, else the contact's most recent one, e.g. the first-touch WhatsApp after a portal inquiry). Null when there is none.
+         *
          *     The Stock detail screen merges this with `/vehicles/{id}/history` (the change log) into one "Leads y cambios" feed — they are two endpoints because they are two different kinds of event. Automotive-vertical only: a workspace on another vertical gets 403 here however its scopes are set.
          */
         get: {
@@ -237713,6 +237996,7 @@ interface paths {
                          *           "kind": "lead",
                          *           "contact_id": "22222222-0000-4000-8000-000000000001",
                          *           "lead_id": "99999999-0000-4000-8000-000000000002",
+                         *           "conversation_id": "99999999-0000-4000-8000-000000000003",
                          *           "portal": "website",
                          *           "at": "2026-09-19T15:30:00.000Z"
                          *         }
@@ -254580,7 +254864,7 @@ interface components {
                 perfect_battery_pct?: number;
                 currency?: string;
             };
-            /** @description Workspace notification rails. The staff WhatsApp rails (`staff_whatsapp`, `unanswered_supervisor_whatsapp`, `booking_whatsapp`) are opt-in: arming one (`enabled: true` with an `account_id`) submits its template to Meta on that number and wires it on approval. Each rail sent replaces that rail whole; rails not sent are kept. */
+            /** @description Workspace notification rails. The staff WhatsApp rails (`staff_whatsapp`, `unanswered_supervisor_whatsapp`, `booking_whatsapp`, `reminder_whatsapp`) are opt-in: arming one (`enabled: true` with an `account_id`) submits its template to Meta on that number and wires it on approval. Each rail sent replaces that rail whole; rails not sent are kept. */
             notifications?: {
                 staff_whatsapp?: {
                     enabled?: boolean;
@@ -254596,6 +254880,16 @@ interface components {
                     template_name?: string;
                     template_language?: string;
                     user_ids?: string[];
+                    /** @description Minutes of open time a conversation waits on the team before the supervisors get the WhatsApp, once per episode. Unset = 60. */
+                    delay_minutes?: number;
+                };
+                /** @description Staff WhatsApp on every «sin respuesta» reminder, to the assignee (template aviso_sigue_esperando_v1). Opt-in: each send costs a WhatsApp conversation. */
+                reminder_whatsapp?: {
+                    enabled?: boolean;
+                    /** Format: uuid */
+                    account_id?: string;
+                    template_name?: string;
+                    template_language?: string;
                 };
                 booking_whatsapp?: {
                     enabled?: boolean;
@@ -254672,6 +254966,26 @@ interface components {
                         rejection_reason: string | null;
                     }[];
                 };
+                reminder_whatsapp: {
+                    /** @description The rail is switched on (`enabled: true`). */
+                    armed: boolean;
+                    /**
+                     * @description Worst state across the rail templates (blocked, rejected, missing, pending, approved); `off` when not armed or nothing to provision; `no_number` when armed without a sending number.
+                     * @enum {string}
+                     */
+                    template_state: "off" | "no_number" | "missing" | "pending" | "approved" | "rejected" | "blocked";
+                    reason: string | null;
+                    /** @description The rail has its template name set (by an admin or on approval). */
+                    wired: boolean;
+                    templates: {
+                        key: string;
+                        name: string;
+                        language: string;
+                        /** @enum {string} */
+                        state: "missing" | "pending" | "approved" | "rejected" | "blocked";
+                        rejection_reason: string | null;
+                    }[];
+                };
             };
             /** @description Workspace display name. */
             name?: string;
@@ -254884,6 +255198,16 @@ interface components {
                     template_name?: string;
                     template_language?: string;
                     user_ids?: string[];
+                    /** @description Minutes of open time a conversation waits on the team before the supervisors get the WhatsApp, once per episode. Unset = 60. */
+                    delay_minutes?: number;
+                };
+                /** @description Staff WhatsApp on every «sin respuesta» reminder, to the assignee (template aviso_sigue_esperando_v1). Opt-in: each send costs a WhatsApp conversation. */
+                reminder_whatsapp?: {
+                    enabled?: boolean;
+                    /** Format: uuid */
+                    account_id?: string;
+                    template_name?: string;
+                    template_language?: string;
                 };
                 booking_whatsapp?: {
                     enabled?: boolean;

package/dist/index.d.ts

@@ -22035,7 +22035,7 @@ interface paths {
         put?: never;
         /**
          * Submit a website buyer inquiry (dealer-website write API)
-         * @description Creates a CRM lead with `website` origin, attaching the inquired Vehículo when `vehicle_id` is given. A proyecto form (Módulo Proyectos) sends `project_id` and/or `unit_model_id` (a tipología names its proyecto): the lead lands on the proyecto, is routed to its ejecutivos, and `message` becomes optional. `attribution` carries the visitor's `first_touch` and `last_touch` (utm_*, gclid, fbclid, anonymous_id); both are kept on the lead. Requires the write-only `leads:intake` scope (never `leads:write`). Returns a minimized `{ status }` ack — `received` on create, `duplicate` on dedup — and echoes no internal ids. Rate-limited like every authenticated endpoint; a hidden `hp_website` honeypot field silently drops spam.
+         * @description Creates a CRM lead with `website` origin, attaching the inquired Vehículo when `vehicle_id` is given. A proyecto form (Módulo Proyectos) sends `project_id` and/or `unit_model_id` (a tipología names its proyecto): the lead lands on the proyecto, is routed to its ejecutivos, and `message` becomes optional. `attribution` carries the visitor's `first_touch` and `last_touch` (utm_*, gclid, fbclid, anonymous_id); both are kept on the lead. `value_amount` is the lead's value; `quote_amount` is a figure the site quoted that is not the deal (a trade-in quote): it only fills the first-touch template's amount and the inbox card when `value_amount` is absent, and is never stored as the lead's value. Requires the write-only `leads:intake` scope (never `leads:write`). Returns a minimized `{ status }` ack — `received` on create, `duplicate` on dedup — and echoes no internal ids. Rate-limited like every authenticated endpoint; a hidden `hp_website` honeypot field silently drops spam.
          */
         post: {
             parameters: {
@@ -22101,6 +22101,7 @@ interface paths {
                         stage_id?: string;
                         value_amount?: number;
                         value_currency?: string;
+                        quote_amount?: number;
                         item_label?: string;
                         source_ref?: string;
                         fields?: {
@@ -88530,6 +88531,272 @@ interface paths {
         patch?: never;
         trace?: never;
     };
+    "/finanzas/contador-export": {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        /**
+         * Download the Contador package for a month (zip)
+         * @description One zip, `paquete-contador-<period>.zip`, with seven xlsx: `01-libro-de-compras`, `02-libro-de-ventas`, `03-honorarios`, `04-movimientos-por-cuenta` (one sheet per bank account), `05-clasificaciones-por-cuenta` (net, as the Resultado counts), `06-resultado` and `07-ajustes-posteriores-al-cierre`, each `<name>-<period>.xlsx`, built by the same code as each screen and its export. Read-only. A caller without the patient register (the Contador) sees a patient as «Paciente A. P.» with no RUT; the libro de ventas keeps the patient RUT on facturas and on notas de crédito or débito that cite one, and boletas carry neither RUT nor name. Requires the `finanzas` add-on — without it every Finanzas operation answers `402 ENTITLEMENT_NOT_ACTIVE` (`details.required = ["finanzas"]`). Requires `finanzas:read`, `finanzas_reports:read` and `finanzas:export` (the Contador seat, owners and admins).
+         */
+        get: {
+            parameters: {
+                query?: {
+                    period?: string;
+                };
+                header?: never;
+                path?: never;
+                cookie?: never;
+            };
+            requestBody?: never;
+            responses: {
+                /** @description The package, as an attachment */
+                200: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/zip": string;
+                    };
+                };
+                /** @description Validation error */
+                400: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+                /** @description Unauthorized */
+                401: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+                /** @description Forbidden */
+                403: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+                /** @description Not found */
+                404: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+                /** @description Conflict (incl. Idempotency-Key reuse with different body) */
+                409: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+                /** @description Rate limited */
+                429: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+            };
+        };
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
+    "/finanzas/contador-export/manifest": {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        /**
+         * What the Contador package for a month holds
+         * @description The same package as the download, without the bytes: the period, the zip name and each file (key, label, name, rows, size). Over MCP this is the read that generates and checks the package; the zip itself downloads over HTTPS. A caller without the patient register (the Contador) sees a patient as «Paciente A. P.» with no RUT; the libro de ventas keeps the patient RUT on facturas and on notas de crédito or débito that cite one, and boletas carry neither RUT nor name. Requires the `finanzas` add-on — without it every Finanzas operation answers `402 ENTITLEMENT_NOT_ACTIVE` (`details.required = ["finanzas"]`). Requires `finanzas:read`, `finanzas_reports:read` and `finanzas:export` (the Contador seat, owners and admins).
+         */
+        get: {
+            parameters: {
+                query?: {
+                    period?: string;
+                };
+                header?: never;
+                path?: never;
+                cookie?: never;
+            };
+            requestBody?: never;
+            responses: {
+                /** @description The manifest */
+                200: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        /**
+                         * @example {
+                         *       "data": {
+                         *         "period": "2026-09",
+                         *         "filename": "paquete-contador-2026-09.zip",
+                         *         "files": [
+                         *           {
+                         *             "key": "libro_compras",
+                         *             "label": "Libro de compras",
+                         *             "filename": "01-libro-de-compras-2026-09.xlsx",
+                         *             "rows": 84,
+                         *             "size_bytes": 14210
+                         *           },
+                         *           {
+                         *             "key": "libro_ventas",
+                         *             "label": "Libro de ventas",
+                         *             "filename": "02-libro-de-ventas-2026-09.xlsx",
+                         *             "rows": 1312,
+                         *             "size_bytes": 61904
+                         *           },
+                         *           {
+                         *             "key": "honorarios",
+                         *             "label": "Honorarios",
+                         *             "filename": "03-honorarios-2026-09.xlsx",
+                         *             "rows": 12,
+                         *             "size_bytes": 7480
+                         *           },
+                         *           {
+                         *             "key": "movimientos",
+                         *             "label": "Movimientos por cuenta",
+                         *             "filename": "04-movimientos-por-cuenta-2026-09.xlsx",
+                         *             "rows": 640,
+                         *             "size_bytes": 38112
+                         *           },
+                         *           {
+                         *             "key": "clasificaciones",
+                         *             "label": "Clasificaciones por cuenta",
+                         *             "filename": "05-clasificaciones-por-cuenta-2026-09.xlsx",
+                         *             "rows": 702,
+                         *             "size_bytes": 40356
+                         *           },
+                         *           {
+                         *             "key": "resultado",
+                         *             "label": "Resultado",
+                         *             "filename": "06-resultado-2026-09.xlsx",
+                         *             "rows": 1398,
+                         *             "size_bytes": 52018
+                         *           },
+                         *           {
+                         *             "key": "ajustes",
+                         *             "label": "Ajustes posteriores al cierre",
+                         *             "filename": "07-ajustes-posteriores-al-cierre-2026-09.xlsx",
+                         *             "rows": 3,
+                         *             "size_bytes": 6920
+                         *           }
+                         *         ]
+                         *       }
+                         *     }
+                         */
+                        "application/json": {
+                            data: {
+                                /** @description The month, `YYYY-MM`. */
+                                period: string;
+                                /** @description The zip the download serves. */
+                                filename: string;
+                                files: {
+                                    /** @enum {string} */
+                                    key: "libro_compras" | "libro_ventas" | "honorarios" | "movimientos" | "clasificaciones" | "resultado" | "ajustes";
+                                    label: string;
+                                    /** @description The xlsx inside the zip. */
+                                    filename: string;
+                                    /** @description Rows of its «Detalle» sheet (documents, items) when it has one, else of its first sheet (movements, adjustments). */
+                                    rows: number;
+                                    size_bytes: number;
+                                }[];
+                            };
+                        };
+                    };
+                };
+                /** @description Validation error */
+                400: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+                /** @description Unauthorized */
+                401: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+                /** @description Forbidden */
+                403: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+                /** @description Not found */
+                404: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+                /** @description Conflict (incl. Idempotency-Key reuse with different body) */
+                409: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+                /** @description Rate limited */
+                429: {
+                    headers: {
+                        [name: string]: unknown;
+                    };
+                    content: {
+                        "application/json": components["schemas"]["Error"];
+                    };
+                };
+            };
+        };
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
     "/clinic/evidence-cards": {
         parameters: {
             query?: never;
@@ -139133,6 +139400,8 @@ interface paths {
          *
          *     Each row also carries `campaign_origin` — the newest campaign send stored in the thread (`null` when none): its campaign, when it left, whether the send created the thread, and whether it is still the newest message (`awaiting_reply`). `fromCampaign=true` lists every such thread, closed ones included.
          *
+         *     Each row also carries `waiting_since` — when its customer started waiting on a human, `null` when nobody waits (the «Esperando respuesta» rule; see the `waiting` parameter). `waiting=true` lists only waiting conversations, team-wide; `sort=wait` orders urgent first, then the longest wait.
+         *
          *     Rows here do NOT carry `ad_origin_nudge` — that field is single-conversation-read only, to avoid a per-row integration lookup on every page of the inbox.
          *
          *     `fields=summary` answers the SAME page with only the identifying and funnel scalars per row — `id`, `display_id`, `channel`, `source`, `status`, `handler`, `assignee_user_id`, `contact_id`, `ticket_id`, `awaiting_human_since`, `first_ai_message_at`, `last_message_date`, `created_at`, `ad_origin` — plus `contact_name`, `ticket_status` and `current_stage_id` off the embeds, and `assignee_name` / `unread` when the list computed them (an api_key has no read markers, so no `unread`). No `contact`, `ticket`, `lastMessage`, `tags`, `marketplaceWindow` or `last_call`. `meta` and `counts` are unchanged. A 20-row page is ~147k characters at `full` (the default, byte-identical to omitting the parameter) and a fraction of that at `summary`; page with `summary` to choose, then `GET /conversations/{id}` for one thread whole.
@@ -139164,7 +139433,10 @@ interface paths {
                     aiReplied?: boolean | null;
                     fromAd?: boolean | null;
                     fromCampaign?: boolean | null;
-                    sort?: "created_at" | "updated_at" | "last_message_date";
+                    /** @description true: only conversations where a customer is waiting on a human («Esperando respuesta»), team-wide. Waiting = open or pending, not filtered, on a channel you can reply in, and either an AI handoff nobody on the team has answered yet (a reply from ANY teammate clears it, including WhatsApp Business / Instagram app replies; a silent «Visita acordada» notice needs no answer) or a human-handled thread whose last message is the customer’s; waits older than 7 days are left out. Each row carries `waiting_since`. Pair with `sort=wait` for the queue order. */
+                    waiting?: boolean | null;
+                    /** @description `wait`: urgent (`handoff_urgent`) first, then by `waiting_since` — `order=desc` (default) is the longest wait first, `asc` the newest; conversations that are not waiting go last. */
+                    sort?: "created_at" | "updated_at" | "last_message_date" | "wait";
                     order?: "asc" | "desc";
                     include?: "counts";
                     /** @description `full` (default): the inbox row with its `contact`, `ticket`, `lastMessage`, `tags`, `marketplaceWindow`, `ad_origin` and `last_call`, exactly as without the parameter. `summary`: only the identifying and funnel scalars — `id`, `display_id`, `channel`, `source`, `status`, `handler`, `assignee_user_id`, `contact_id`, `ticket_id`, `awaiting_human_since`, `first_ai_message_at`, `last_message_date`, `created_at`, `ad_origin`, plus `contact_name`, `ticket_status`, `current_stage_id` off the embeds and `assignee_name` / `unread` when the list computed them. Pagination, `meta` and `counts` are unchanged. Use `summary` to page the inbox cheaply, then `GET /conversations/{id}` for one thread in full. */
@@ -139303,7 +139575,8 @@ interface paths {
                          *             }
                          *           ],
                          *           "last_call": null,
-                         *           "handoff_urgent": false
+                         *           "handoff_urgent": false,
+                         *           "waiting_since": null
                          *         },
                          *         {
                          *           "id": "bbbbbbbb-0000-4000-8000-000000000002",
@@ -139440,7 +139713,8 @@ interface paths {
                          *           },
                          *           "tags": [],
                          *           "last_call": null,
-                         *           "handoff_urgent": false
+                         *           "handoff_urgent": false,
+                         *           "waiting_since": null
                          *         }
                          *       ],
                          *       "meta": {
@@ -139729,9 +140003,11 @@ interface paths {
             cookie?: never;
         };
         /**
-         * Inbox badge counts (my open / unread / mentions / unassigned)
+         * Inbox badge counts (my open / unread / mentions / unassigned / waiting)
          * @description The four badge counts on their own, scoped to the calling principal: `myOpen` and `myUnread` are the conversations assigned to the member behind the credential, `myMentions` the ones that @-mention them, `unassigned` the whole workspace’s unowned queue. An API key has no member behind it, so its three "my" counts read 0 and only `unassigned` is meaningful — use a personal token to get a person’s badges.
          *
+         *     «Esperando respuesta» (the waiting queue): `waiting` is how many conversations have a customer waiting on a human, team-wide (the list `GET /conversations?waiting=true` returns exactly these); `waitingUrgent` how many of them are flagged urgent; `waitingMine` how many are assigned to the caller (0 for an API key); `waitingOldestSince` when the longest wait started (ISO, `null` when nobody waits) — render it as «el más antiguo 2 h».
+         *
          *     `GET /conversations?include=counts` returns the same payload beside a page of conversations; this route exists for the caller that wants the badges without one.
          */
         get: {
@@ -139755,7 +140031,11 @@ interface paths {
                          *         "myOpen": 3,
                          *         "myUnread": 1,
                          *         "unassigned": 2,
-                         *         "myMentions": 0
+                         *         "myMentions": 0,
+                         *         "waiting": 3,
+                         *         "waitingUrgent": 1,
+                         *         "waitingMine": 1,
+                         *         "waitingOldestSince": "2026-10-31T13:05:00.000Z"
                          *       }
                          *     }
                          */
@@ -139994,6 +140274,7 @@ interface paths {
                          *         ],
                          *         "last_call": null,
                          *         "handoff_urgent": false,
+                         *         "waiting_since": null,
                          *         "ad_origin_nudge": null,
                          *         "handoff_resolved_suggested": false,
                          *         "message": [
@@ -237685,6 +237966,8 @@ interface paths {
          * This car’s lead timeline
          * @description Every named lead that asked about this vehicle, merged with its anonymous Yapo phone-reveals, newest first. This is the car’s HISTORY, so unlike `/interest` a sold vehicle keeps its timeline.
          *
+         *     Each lead row carries `conversation_id`: the chat to open for that person (the lead's own conversation, else the contact's most recent one, e.g. the first-touch WhatsApp after a portal inquiry). Null when there is none.
+         *
          *     The Stock detail screen merges this with `/vehicles/{id}/history` (the change log) into one "Leads y cambios" feed — they are two endpoints because they are two different kinds of event. Automotive-vertical only: a workspace on another vertical gets 403 here however its scopes are set.
          */
         get: {
@@ -237713,6 +237996,7 @@ interface paths {
                          *           "kind": "lead",
                          *           "contact_id": "22222222-0000-4000-8000-000000000001",
                          *           "lead_id": "99999999-0000-4000-8000-000000000002",
+                         *           "conversation_id": "99999999-0000-4000-8000-000000000003",
                          *           "portal": "website",
                          *           "at": "2026-09-19T15:30:00.000Z"
                          *         }
@@ -254580,7 +254864,7 @@ interface components {
                 perfect_battery_pct?: number;
                 currency?: string;
             };
-            /** @description Workspace notification rails. The staff WhatsApp rails (`staff_whatsapp`, `unanswered_supervisor_whatsapp`, `booking_whatsapp`) are opt-in: arming one (`enabled: true` with an `account_id`) submits its template to Meta on that number and wires it on approval. Each rail sent replaces that rail whole; rails not sent are kept. */
+            /** @description Workspace notification rails. The staff WhatsApp rails (`staff_whatsapp`, `unanswered_supervisor_whatsapp`, `booking_whatsapp`, `reminder_whatsapp`) are opt-in: arming one (`enabled: true` with an `account_id`) submits its template to Meta on that number and wires it on approval. Each rail sent replaces that rail whole; rails not sent are kept. */
             notifications?: {
                 staff_whatsapp?: {
                     enabled?: boolean;
@@ -254596,6 +254880,16 @@ interface components {
                     template_name?: string;
                     template_language?: string;
                     user_ids?: string[];
+                    /** @description Minutes of open time a conversation waits on the team before the supervisors get the WhatsApp, once per episode. Unset = 60. */
+                    delay_minutes?: number;
+                };
+                /** @description Staff WhatsApp on every «sin respuesta» reminder, to the assignee (template aviso_sigue_esperando_v1). Opt-in: each send costs a WhatsApp conversation. */
+                reminder_whatsapp?: {
+                    enabled?: boolean;
+                    /** Format: uuid */
+                    account_id?: string;
+                    template_name?: string;
+                    template_language?: string;
                 };
                 booking_whatsapp?: {
                     enabled?: boolean;
@@ -254672,6 +254966,26 @@ interface components {
                         rejection_reason: string | null;
                     }[];
                 };
+                reminder_whatsapp: {
+                    /** @description The rail is switched on (`enabled: true`). */
+                    armed: boolean;
+                    /**
+                     * @description Worst state across the rail templates (blocked, rejected, missing, pending, approved); `off` when not armed or nothing to provision; `no_number` when armed without a sending number.
+                     * @enum {string}
+                     */
+                    template_state: "off" | "no_number" | "missing" | "pending" | "approved" | "rejected" | "blocked";
+                    reason: string | null;
+                    /** @description The rail has its template name set (by an admin or on approval). */
+                    wired: boolean;
+                    templates: {
+                        key: string;
+                        name: string;
+                        language: string;
+                        /** @enum {string} */
+                        state: "missing" | "pending" | "approved" | "rejected" | "blocked";
+                        rejection_reason: string | null;
+                    }[];
+                };
             };
             /** @description Workspace display name. */
             name?: string;
@@ -254884,6 +255198,16 @@ interface components {
                     template_name?: string;
                     template_language?: string;
                     user_ids?: string[];
+                    /** @description Minutes of open time a conversation waits on the team before the supervisors get the WhatsApp, once per episode. Unset = 60. */
+                    delay_minutes?: number;
+                };
+                /** @description Staff WhatsApp on every «sin respuesta» reminder, to the assignee (template aviso_sigue_esperando_v1). Opt-in: each send costs a WhatsApp conversation. */
+                reminder_whatsapp?: {
+                    enabled?: boolean;
+                    /** Format: uuid */
+                    account_id?: string;
+                    template_name?: string;
+                    template_language?: string;
                 };
                 booking_whatsapp?: {
                     enabled?: boolean;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vitrina/api",
-  "version": "15.16.0",
+  "version": "15.18.0",
   "description": "Typed TypeScript SDK for the Vitrina API pública — generated from the committed openapi.public.json (ADR 0106).",
   "type": "module",
   "license": "MIT",