rallly: raise app memory 256M -> 768M (OOM-killed at 256M)

rallly 4.11.1 (Next.js 16) booted and was immediately killed by the cgroup OOM
killer, 14 times in 420s:

  ▲ Next.js 16.2.6
  - Local:  http://localhost:3000
  ✓ Ready in 0ms
  Killed

Migrations applied fine; it simply cannot live in 256M any more. App limit
256M -> 768M; sidecar Postgres left at 256M; .felhom.yml mem_limit updated to
the new sum (768+256 = 1024M) per the REUSE.md rule.

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/rallly/.felhom.yml

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

templates/rallly/docker-compose.yml

@@ -41,7 +41,7 @@ services:
     deploy:
       resources:
         limits:
-          memory: 256M
+          memory: 768M
     # The rallly image has NO wget/curl — the old wget healthcheck always failed (exit 127), marking the
     # container unhealthy, which made Traefik refuse to publish a route to it. Use Node (always present).
     # rallly's "/" returns 307 → /login, so accept any status < 500.