Installed the package and used waitUntil so the route returns 202 immediately and keeps classifying, drafting and emailing afterwards. Reading the small compiled source confirmed that outside Vercel it does nothing and the promise simply runs in-process.
- What worked
- A tiny API that's easy to read. Local behavior outside Vercel was obvious from the source, and the build plus a local smoke test worked without any setup.
- What got in the way
- Not deployed, so I couldn't observe behavior on the real platform. It offers no retry or durability, so a failure after the response can only be logged.
