feat: secure DevAI OCR API test console

[Sam123ben]

Goal

Provide a DevAI-only, authenticated test console for the reusable OCR v1 API without exposing storage credentials, Langfuse secrets, tenant identity, or raw documents in telemetry.

Scope

• audit the canonical OpenAPI against running Axum routes and add contract tests for any gap
• document endpoint authz, idempotency, limits, state transitions, and safe error semantics
• add a DevAI console that obtains product/tenant identity only from the verified DevAI session, follows the upload-intent → signed PUT → complete → job → status/result flow, and redacts all uploaded content from traces/logs
• use only DevAI sandbox/dev product telemetry; no Kora production Langfuse credentials in the shared OCR service
• add API/UI tests and a local disposable integration path
• create GitOps deployment changes only after the documented design review gates and DevAI target discovery are complete

Security acceptance

• UI never accepts tenant/product identity or bearer credentials from browser form input
• no arbitrary URL ingestion, no client-side secrets, no raw document/result payload in logs or traces
• per-object tenant/product authorization gives 404 on foreign resources
• body/file/page/time limits and idempotency are enforced end-to-end

Delivery gates

• OpenAPI-route parity test; Rust and DevAI test/build/lint gates pass
• local real API exercise using an isolated disposable environment
• read-only GKE/Argo discovery identifies target namespace, ingress, workload identity and GitOps owner before any deploy
• dev deployment is canaried and verified with synthetic, non-sensitive fixtures

[Sam123ben]

Runtime validation update

Read-only production discovery confirms that the DevAI dashboard/API and sandbox-operator applications are healthy, and the document-sandbox UI/proxy changes are present in the deployed DevAI release. Their merged build and secret-scan checks are green.

The console is correctly not capable of a live OCR upload test today: there is no document-intelligence API/worker Service or sandbox Argo application, and no Sandbox Freight has been promoted. Do not use the DevAI UI to substitute a direct bucket or provider path.

When deployment gates close, the first live test must use synthetic/non-sensitive data, verified DevAI session-derived identity, the documented upload-intent flow, and the disposable sandbox retention policy. This issue remains open until that real endpoint exercise, foreign-tenant denial, malware rejection, and trace-redaction verification complete.

[Sam123ben]

DevAI upload hardening follow-up: the OCR console route uses FastAPI multipart parsing, and a local clean-environment verification exposed that python-multipart was only transitive. PR tesserix/devai#401 declares and locks it directly. Focused OCR tests (14) and the full DevAI unit suite (2,135 passed, 1 skipped) pass locally; no document content, credential, deployment, retention, or service endpoint changed.