komga: 1.25.0 -> 1.27.1 and 768M (proven on the bench AND on 9202, with its test record)

Bench at 512M: proven but memory_tight (its own memory 94.6 %); per the
bar the limit is raised in the same commit and the watch re-run once:
at 768M 60 %, 0 kills, 11 940 requests all 200; abort starts-and-serves.
Box (9202, guarded Update, at 512M): done, read back, R-626 clean.
The komga fixture was fixed tonight (users/me lives at /api/v2).
09 decision 21.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS

templates/komga/.felhom.yml

@@ -10,12 +10,12 @@ subdomain: "comics"
 slug: "komga"
 # catalog_since: the date THIS repo last changed this app's pinned images. Any commit that
 # changes an image: line must set this to the same day (see CLAUDE.md).
-catalog_since: "2026-07-18"
+catalog_since: "2026-09-23"
 
 # --- Resource hints (displayed on deploy screen) ---
 resources:
   mem_request: "200M"
-  mem_limit: "512M"
+  mem_limit: "768M"
   pi_compatible: true
   needs_hdd: true
 
@@ -116,3 +116,9 @@ i18n:
         label: 'Comic library path'
         description: 'The path to the external hard drive'
         placeholder: '/mnt/felhom-drives/hdd_1'
+
+# update_ladder — the test record: one tested step per line, oldest first (JSON flow mappings,
+# `09-update-architecture.md` §6.4 part 4). WRITTEN BY scripts/upgrade-test.py, never by hand;
+# gated by scripts/check-test-record.py. An image: move without a proven entry here is refused.
+update_ladder:
+  - {"from": {"komga": "gotson/komga:1.25.0"}, "to": {"komga": "gotson/komga:1.27.1"}, "digest": {"komga": "sha256:9cf102f5fb78e2e020700c53eca757e4f4d4e347121b0a16380822760337cca9"}, "verdict": "proven", "tested_at": "2026-09-23T19:46:46Z", "harness_version": 3, "evidence": "felhom.eu/documentation/audits/night-2026-09-23/apps/komga/bench/evidence/MV-komga/verdict.json", "box_evidence": "felhom.eu/documentation/audits/night-2026-09-23/apps/komga/verdict.json", "memory_peak_pct": 60.0, "marks": {"files_may_change": false, "needs_person": null, "memory_tight": false}, "memory_basis": "anon", "memory_cgroup_peak_pct": 76.8}

templates/komga/docker-compose.yml

@@ -1,7 +1,7 @@
 # Komga - Képregény és manga szerver OPDS támogatással
 # Domain: ${SUBDOMAIN}.${DOMAIN}
 # Database: None (file-based)
-# RAM: ~200M (mem_limit: 512M) | Pi-compatible: Yes
+# RAM: ~460M under load on 1.27 (mem_limit: 768M) | Pi-compatible: Yes
 #
 # Environment variables:
 #   DOMAIN          - Your domain (e.g., demo-felhom.eu)
@@ -16,7 +16,7 @@
 
 services:
   komga:
-    image: gotson/komga:1.25.0
+    image: gotson/komga:1.27.1
     container_name: komga
     restart: unless-stopped
     # Runs as root (see note above). Restore an escalation boundary: block SUID-based privilege
@@ -34,7 +34,9 @@ services:
     deploy:
       resources:
         limits:
-          memory: 512M
+          # 768M, MEASURED 2026-09-23 night: 1.27.1 used 94.6 % of 512M (its own memory, anon) under ten
+          # minutes of light load — memory_tight; at 768M 60 %, 0 kills. The JVM grows into what it is given.
+          memory: 768M
     # HC override: komga's actuator lives at /actuator/health (unauthenticated, 200), NOT under the
     # auth-gated /api/v1 API prefix — the old /api/v1/actuator/health returns 401 so `curl -f` failed
     # (exit 22) and the container reported "unhealthy" despite serving fine. The gotson/komga image