feat: platform backbone and field capture, first part (checkpoint)

Platform backbone (plan 2026-10-13-plattform-rueckgrat), reviewed tasks:
- run roles api/worker/job/all with shared startup checks (Task 1)
- schema and migration for DomainEvent, deliveries, JobRun, ThrottlerHit (Task 2)
- audit, notifications and domain events written in the same transaction (Task 3)
- dispatcher with SKIP LOCKED claims, retries and stale release (Task 4)
- worker building blocks: tick, LISTEN/NOTIFY wake-up, health (Task 5)
- worker process and entry points (Task 6)
- throttler counters in Postgres (Task 19)
- separate keys per purpose with key ring (Task 20)
- public origin page without exact location (Task 22)
- shop keys split into read and write (Task 23)
- Kustomize base, components, overlay encry, CI validation (Task 26)

Field capture T3 (plan 2026-10-13-t3-erfassung-am-stand), reviewed tasks:
- brood frames, read endpoints, apiary overview and offline pack
- network basics, offline queue v3, navigation sheets, form building blocks
- new inspection with last-time hints and weather, varroa per day,
  treatment prefill, apiary page with round
- inspection photo (Task 10) is implemented, review pending

Not rolled out. Remaining tasks follow in later commits.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

deploy/k8s/base/backend/deployment.yaml

@@ -0,0 +1,88 @@
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: apicore-backend
+  labels:
+    app: apicore-backend
+spec:
+  # Ohne HPA genau ein Pod. components/api-hpa entfernt replicas, dann
+  # steuert der HPA (1-2 Pods).
+  replicas: 1
+  # Erst der neue Pod, dann weg mit dem alten: scheitert die Migration im
+  # initContainer (components/backend-roles), laeuft der alte Pod weiter.
+  strategy:
+    type: RollingUpdate
+    rollingUpdate:
+      maxSurge: 1
+      maxUnavailable: 0
+  selector:
+    matchLabels:
+      app: apicore-backend
+  template:
+    metadata:
+      labels:
+        app: apicore-backend
+    spec:
+      securityContext:
+        runAsNonRoot: true
+        runAsUser: 1000
+        runAsGroup: 1000
+        seccompProfile:
+          type: RuntimeDefault
+      volumes:
+        # Dokumente, Avatare und App-Backups (DOCUMENTS_STORAGE_PATH /
+        # BACKUP_STORAGE_PATH unter /data). Ohne Volume landen sie im
+        # Container und sind beim naechsten Neustart weg.
+        - name: data
+          persistentVolumeClaim:
+            claimName: apicore-data
+      containers:
+        - name: apicore-backend
+          # Ohne Tag: den Digest setzt das Overlay (images in
+          # overlays/encry/kustomization.yaml), nie :latest - sonst gibt es
+          # kein Rollback und jeder Neustart zieht ungeprueft ein neues Image.
+          image: git.encry.de/nick.rosenloecher/apicore-backend
+          imagePullPolicy: IfNotPresent
+          securityContext:
+            allowPrivilegeEscalation: false
+            capabilities:
+              drop: ["ALL"]
+          volumeMounts:
+            - name: data
+              mountPath: /data
+          ports:
+            - containerPort: 3001
+          envFrom:
+            - configMapRef:
+                name: apicore-backend-config
+            - secretRef:
+                name: apicore-backend-secret
+          # startupProbe gibt dem Start bis zu 5 Minuten, ohne dass
+          # liveness/readiness in der Zwischenzeit einen Neustart ausloesen.
+          # Das alte Image fuehrt `prisma migrate deploy` noch im CMD aus, ab
+          # components/backend-roles laeuft die Migration im initContainer.
+          startupProbe:
+            httpGet:
+              path: /health/ready
+              port: 3001
+            failureThreshold: 30
+            periodSeconds: 10
+          livenessProbe:
+            httpGet:
+              path: /health
+              port: 3001
+            initialDelaySeconds: 10
+            periodSeconds: 15
+          readinessProbe:
+            httpGet:
+              path: /health/ready
+              port: 3001
+            initialDelaySeconds: 5
+            periodSeconds: 10
+          resources:
+            requests:
+              cpu: "0"
+              memory: "0"
+            limits:
+              cpu: 500m
+              memory: 512Mi