One upload contract for web and mobile capture

Capture clients should not invent their own backend

Mobile capture is useful only if it lands in the same accounting workflow as every other document. A photo taken from Android should create the same kind of intake item as a file uploaded from the web app.

That is why the capture client uses the shared upload API instead of keeping a separate bridge or mock scanner path. The API owns authentication, client context, storage, and intake creation. The mobile app stays focused on scanning, setup, and upload ergonomics.

Why this helps future iOS work

The iOS client can follow the same contract later instead of starting from a different backend shape. Platform-specific scanning can live in React Native modules, while document upload and server-side accounting behavior stay shared.

The result is less duplicated code, easier Android verification, and a clearer path for adding iOS without changing the accounting workflow again.