Drain the queue inside the request instead of buying Vercel Pro

The decision

Move the retry cron to daily and have the inbound webhook drain up to five pending messages via `after()`, once the 200 is already on its way back.

Why, at the time

Restoring sub-daily schedules costs money. That is a spend decision, and it should not be made by accident to work around an engineering constraint.

What happened

The channel stayed responsive on the free plan. A stuck message no longer waits a full day while mail is still arriving, and the runbook records the constraint so the next person does not rediscover it.

Every entry in this ledger is real and was checked against the commit or migration that carries it. Want to keep your own this way? Start with the free decision log template.