From df7bd459ed424cc84e31bd8b086a17f55aea8d50 Mon Sep 17 00:00:00 2001 From: Mathias Date: Sat, 3 Oct 2026 16:29:32 +0200 Subject: [PATCH] docs(adr): the ingress body-size item is resolved, and uploads are on in production (infra#520) Co-Authored-By: Claude Sonnet 5.5 --- DECISIONS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/DECISIONS.md b/DECISIONS.md index dae1596..2db1b68 100644 --- a/DECISIONS.md +++ b/DECISIONS.md @@ -1531,7 +1531,7 @@ deferred. The scope cut — chat first, no rich analysis, no video — is what k #33 specifies, with the serving endpoint shown **(recommended, matches the issue)**; (B) disabled by default, a failed iguana job fails honestly and the user retries. *Blocks:* the production default only; the adapter ships either way. -- Verify Tapir's ingress `proxy-body-size` against the 200 MB cap (`infra`). +- ~~Verify Tapir's ingress `proxy-body-size` against the 200 MB cap (`infra`).~~ **Resolved 2026-10-03:** real unauthenticated bodies of 2, 30, 120 and 210 MiB all pass NPM (TLS, piguard) and Traefik to tapir (a 302 to login); there is no body limit in that range. Uploads were enabled in production the same day, local engines only (infra#520). - Per-transcript deletion is not built; account deletion cascades. A private-content store without a delete button is a gap worth a ticket, not a silent omission.