Enviar fuera del horario de los despachos

docs://recipes/send-outside-court-hours — enviar fuera del horario de los despachos: read the two dates and propose when a send leaves

Use when a send is being prepared after the reference court hours (business days, 08:00 to
16:00 America/Bogota) or on a non-business day, or when the lawyer asks on which date the
notification would be deemed made. You READ the dates and may PROPOSE when the message leaves.
The lawyer decides in the panel. Nothing is sent or scheduled by a proposal.
Every firm tool runs through manage_resource; only whoami and docs are called by name.
No draft yet? Prepare one first: docs://recipes/send-an-article-8-notification (steps 1 to 8).

1. manage_resource({resource:"notifications", action:"sendTiming", params:{orgId:"<orgId>", notificationId:"<notification.id>"}})
   → now, nextOpen, divergent, reason, standard.surtidaOn, conservative, policy, scheduling, holdMs
   now and nextOpen are UTC instants: show them in America/Bogota.
   surtidaOn and deemedSentOn are calendar days in Bogotá (YYYY-MM-DD).
   The answer moves with the clock: read it again right before step 3.

2. Tell the lawyer what the answer says, as dates, never as a rule:
   divergent false → both readings agree: one date, standard.surtidaOn.
   divergent true  → two readings of the same send:
     standard.surtidaOn       counted from the day the message leaves
     conservative.surtidaOn   counted from the next business day (conservative.deemedSentOn)
   reason says why they differ: "after_hours" or "non_business_day".
   The reference hours are the service's own reference for a more cautious reading of the date.
   They are not a legal rule. Both dates are estimates: the judge decides.
   Do not tell the lawyer that an hour is forbidden or required. Give the two dates and let them choose.

3. manage_resource({resource:"sends", action:"sendNotification", params:{orgId:"<orgId>", notificationId:"<notification.id>", confirm:true, when:"now|next_business_open"}})
   → status "awaiting_confirmation", confirmUrl      (or "awaiting_approval", approvalUrl)
   when is OPTIONAL and is a proposal:
     "now"                 propose that it leaves when the lawyer confirms
     "next_business_open"  propose that it leaves at nextOpen
   The lawyer sees the proposal preselected on confirmUrl (or approvalUrl) and can change it.
   Only their confirmation sends or schedules. Leave when out when the lawyer expressed no preference.
   scheduling "off" in step 1? Do not send when:"next_business_open": it is refused with
   X_SEND_SCHEDULING_OFF and nothing is requested. Propose "now", or leave when out.
   holdMs above 259200000 (72 hours)? Say how many days the wait is (a vacancia judicial can
   make it weeks) before proposing "next_business_open".

4. After the lawyer confirms:
   manage_resource({resource:"notifications", action:"getNotification", params:{orgId:"<orgId>", notificationId:"<notification.id>"}})
   → status, scheduledFor, recipients[], timeline[]
   Report what is recorded, never what should have happened by now:
   status "scheduled" → confirmed, not sent. Nothing was frozen, timestamped or charged. The
     send is due to START at scheduledFor; credits are charged then. Its content cannot change
     while it waits (X_NOTIFICATION_SCHEDULED on a draft write).
   status "freezing", "frozen" or "sending" → in progress, NOT sent yet: the message is being
     frozen, timestamped and handed to the mail transport. A send.released event means the
     schedule ended, not that anything left. Say "in progress" and read again in a minute.
   status "sent" → say a message left ONLY for a recipient with a transport.sent event on the
     timeline. A recipient with sendUnconfirmed true: say the outcome is unknown (it may or may
     not have left; it is being checked and is never re-sent). A recipient with a failure: it
     did not leave. transport.sent is not delivery: docs://recipes/check-a-notification-status.
   status "failed" → nothing left; say so and quote the timeline's last event.
   status "draft" again → the schedule was cancelled: by a person, or because the send's checks
     refused it at its instant (credits, a suspended firm, an archived case). Only after such
     a refusal is a mail sent, once, to the lawyer who scheduled it.

Done when the lawyer has the dates and the link to confirm, or you have told them the status
and scheduledFor of a scheduled send.

Tips
- Cancelling a schedule and "send now" are the lawyer's, in the panel, on
  https://www.notificado.co/notificaciones/<notification.id>. There is no tool for either:
  cancelScheduledSend and sendScheduledNow are human-only. "Send now" is only for the lawyer who
  scheduled it; anyone who may send for the firm can cancel.
- A scheduled notification is not sent, and a released one is not sent yet. The term dates are
  computed from the recorded send (transport.sent), never from the confirmation or from
  scheduledFor: read them with docs://recipes/track-deadlines once it is sent. listDeadlines rows carry `conservative` when the
  two readings differ.
- Scheduling is for the next opening of a business day only. There is no free-form instant.
- What the evidence records for a scheduled send: https://www.notificado.co/metodo-de-evidencia#envios-programados