Right-size rails workload: 1Gi + capacityAI

Previous commit bumped memory 512Mi → 2Gi matching the marketplace
demo, but cherry-picked only the memory dimension: CPU stayed at 300m
and capacityAI stayed false. Net result was a wasteful fixed 2Gi
allocation with no autoscale — the pattern Justin flagged.

Better right-size for this tutorial (smaller Rails surface than the
marketplace RSC demo):

- memory: 2Gi → 1Gi. Enough headroom for Rails + the Pro Node renderer
  in one container without reserving capacity that won't be used.
- capacityAI: false → true. Adjusts CPU/memory within the single
  replica based on observed usage, so the 1Gi/300m baseline grows if
  actual workload warrants it. Matches the marketplace demo's
  capacityAI posture without copying its oversized static baseline.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: ihabadham

.controlplane/templates/rails.yml

@@ -15,9 +15,11 @@ spec:
       # Inherit other ENV values from GVC
       inheritEnv: true
       image: {{APP_IMAGE_LINK}}
-      # Bumped from 512Mi because the container now runs both Rails and the
-      # Pro Node renderer. Matches the marketplace demo's rails.yml.
-      memory: 2Gi
+      # 1Gi (up from 512Mi) gives the single container enough headroom for
+      # Rails + the Pro Node renderer. Below the marketplace demo's 2Gi
+      # because this tutorial's Rails surface is smaller; capacityAI below
+      # adjusts upward if actual usage warrants it.
+      memory: 1Gi
       ports:
         - number: 3000
           protocol: http
@@ -28,7 +30,9 @@ spec:
     autoscaling:
       # Max of 1 effectively disables autoscaling, so a like a Heroku dyno count of 1
       maxScale: 1
-    capacityAI: false
+    # CapacityAI adjusts CPU/memory within the single replica based on observed
+    # usage, so the 1Gi/300m baseline can grow if Rails + renderer need more.
+    capacityAI: true
   firewallConfig:
     external:
       # Default to allow public access to Rails server