require only bound the lease. A page that timed out on a pod, or a pool that
refused, still sent the whole document to the local pipeline. Live, that was
4 surya processes at ~9 GB each and swap full on a GPU-less orchestrator,
with those pages slower than a retry on a pod. Under require, that case is now
a 503, so the client retries and the page goes back to the cards.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KnfkxBpcZ1v6ypRFFyhrVM