Based on that diagnosis, we changed the packaging configuration to isolate the OCR/Tesseract runtime assets instead of broadly tracing them across API routes.

The packaging correction was committed as:

0834b94

Local validation after that change passed:

• 3,440 tests passed
• 40 existing skips
• TypeScript passed
• production build passed
• ESLint: 0 errors
• two clean 205-migration database replays passed
• a 77-manifest trace audit passed
• OCR/Tesseract tracing was isolated from unrelated API routes

However, the first and only Preview deployment of the corrected commit still failed at exactly the same point:

Build Completed in /vercel/output → Deploying outputs... → internal Vercel error

We intentionally did not keep retrying or make additional speculative source changes.

At this point we would really appreciate help from someone at Vercel who can inspect the backend/internal publish trace.

Specifically, could you help determine whether the failure is occurring during:

• Serverless Function packaging/serialization
• artifact upload/storage
• /vercel/output validation
• WASM/native asset processing
• function registration
• or another internal publication step?

The public deployment logs do not expose the failing sub-stage, so we cannot safely determine what to change next.

Importantly, we are not asking for a redeploy or a generic troubleshooting checklist. The builds consistently succeed; we are trying to identify the exact post-build publication failure before making any further source changes.

Thank you very much for taking a look.