Sync the self-hosting stack

kubernetes/06b-ingress-uploads.yaml

@@ -22,11 +22,12 @@ metadata:
     argocd.argoproj.io/sync-wave: "2"
     # 13376k is 13 MiB and 64 KiB: exactly the most the API itself reads on this path — a workspace
     # image of up to 10 MiB, the copy of it prepared for the model (at most 3 MiB), and 64 KiB for
-    # the multipart framing and the name (`BODY_MAX_BYTES.documents` + `MULTIPART_OVERHEAD`, in
-    # apps/api/src/files/upload-gate.interceptor.ts; both refuse strictly above). Not less: a body
-    # the API would take would meet this ceiling first, and the controller's answer is an HTML page
-    # the client cannot translate. Not more: the API refuses anything larger unread. A composer
-    # attachment over 10 MiB still gets through here, and meets the API's own JSON 413.
+    # the multipart framing and the name (`UploadGate.BodyMaxBytes(UploadRoute.Documents)` +
+    # `UploadGate.MultipartOverhead`, in src/Jarvis.Api/Files/UploadEndpoint.cs; both refuse
+    # strictly above). Not less: a body the API would take would meet this ceiling first, and the
+    # controller's answer is an HTML page the client cannot translate. Not more: the API refuses
+    # anything larger unread. A composer attachment over 10 MiB still gets through here, and meets
+    # the API's own JSON 413.
     nginx.ingress.kubernetes.io/proxy-body-size: "13376k"
     # Everything the API does with a file happens before it answers: a wait for an upload slot, a
     # PDF's text extraction (capped at 20s), a 13 MB row write. Two minutes is headroom over that,