Mission#

Send Maxime a NEW joke (not the anti-gravity one from t-004 run 5) on WhatsApp, using Path B of the relay protocol (cron isolated agentTurn with announce delivery). This is a live test of the protocol now that the runner device has operator.write scope.

Why Path B specifically#

• Path A worked for t-004 run 5 but depends on Robbie's WhatsApp session being awake. Brittle.
• Path B uses cron + announce delivery directly through the WhatsApp channel plugin. Push delivery, no relay session in the loop.
• Earlier verification (cron job ce790699) confirmed Path B delivers with delivered: true end-to-end.

How to deliver#

1. Pick a fresh, original joke. Not anti-gravity. One short line.
2. Schedule the cron job:

cron({
  action: "add",
  job: {
    name: "debbie-joke-t006",
    schedule: { kind: "at", at: "<now+10s ISO with timezone>" },
    payload: {
      kind: "agentTurn",
      message: "Send exactly this and nothing else: \"🦑 Debbie: <your joke>\""
    },
    sessionTarget: "isolated",
    delivery: {
      mode: "announce",
      channel: "whatsapp",
      to: "+6580860085",
      bestEffort: true
    },
    deleteAfterRun: true
  }
})

1. Wait ~15 sec, then call cron({action: "runs", jobId: <returned id>}) and confirm:
   • entries[0].delivered === true
   • entries[0].deliveryStatus === "delivered"
   • entries[0].delivery.resolved.ok === true
2. Mark the run success only if the cron run record shows delivered: true. Otherwise mark failed with the actual error.

Acceptance criteria#

• A fresh joke (not anti-gravity) lands on Maxime's WhatsApp
• Verification is cron run record showing delivered: true
• Run log captures the cron.add request, the cron.runs response, and the joke text

Do NOT#

• Do not use Path A (relay through Robbie). We're specifically testing Path B.
• Do not call sessions_send to Robbie's WhatsApp session for any reason during this run.
• Do not send any "agent-to-agent announce" stub message.
• Do not send [alert|debbie] escalations during this run.