fix(apps): ollama resource type + adguardhome port; gate on collisions

Ollama's embedded manifest failed the typed parse (memory_limit wants a
string) so the catalog overlay was skipped for it; AdGuard Home's
conventional :3000 collided with Grafana's. The release gate now runs
the host-port collision test (repo_app_manifests_have_no_host_port_collisions)
so this class can never ship untested again.

apps/adguardhome/manifest.yml

@@ -28,10 +28,13 @@ app:
     network_policy: isolated
 
   ports:
-    - host: 3000
+    - host: 3030
       container: 3000
       protocol: tcp
       bind: 127.0.0.1
+      # 3030, not AdGuard Home's conventional 3000: Grafana owns :3000 on a
+      # node, and both being installable means the host ports must not
+      # collide (the orchestrator refuses/loads warn on overlap).
       # open: the setup wizard and admin console carry AdGuard Home's own
       # login; the gate fronts the port (TLS, header fixes) without a
       # second cookie challenge.
@@ -67,7 +70,7 @@ app:
 
   health_check:
     type: tcp
-    endpoint: localhost:3000
+    endpoint: localhost:3030
     interval: 30s
     timeout: 5s
     retries: 3
@@ -77,7 +80,7 @@ app:
       name: Admin console
       description: AdGuard Home web console
       type: ui
-      port: 3000
+      port: 3030
       protocol: http
       path: /
 

apps/ollama/manifest.yml

@@ -20,7 +20,8 @@ app:
     - storage: 50Gi
 
   resources:
-    memory_limit: 0
+    # No memory limit: models are sized by the disk allowance below, and a
+    # RAM ceiling would just OOM-kill long inferences.
     disk_limit: 50Gi
 
   security: