gramps-web: raise memory 384M -> 1024M (OOM proven during validation)

v25.6.0 could not stay up under the 384M limit. Live evidence from the demo box:

  [ERROR] Worker (pid:559) was sent SIGKILL! Perhaps out of memory?
  [ERROR] Worker (pid:556) was sent SIGKILL! Perhaps out of memory?

gunicorn kept booting replacement workers that were killed in turn, so the
container never reached healthy and Traefik returned 404. mem_limit in
.felhom.yml raised to match the compose limit; mem_request 100M -> 384M.

Campaign 7 catalog sweep.

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

templates/gramps-web/.felhom.yml

@@ -11,8 +11,8 @@ slug: "gramps-web"
 
 # --- Resource hints (displayed on deploy screen) ---
 resources:
-  mem_request: "100M"
-  mem_limit: "384M"
+  mem_request: "384M"
+  mem_limit: "1024M"
   pi_compatible: true
   needs_hdd: false
 

templates/gramps-web/docker-compose.yml

@@ -25,7 +25,7 @@ services:
     deploy:
       resources:
         limits:
-          memory: 384M
+          memory: 1024M
     healthcheck:
       test: ["CMD", "wget", "--spider", "-q", "http://127.0.0.1:5000"]
       interval: 30s

templates/homebox/docker-compose.yml

@@ -11,7 +11,7 @@
 
 services:
   homebox:
-    image: ghcr.io/sysadminsmedia/homebox:v0.26.2
+    image: ghcr.io/sysadminsmedia/homebox:0.26.2
     container_name: homebox
     restart: unless-stopped
     environment: