fc-desktop: add phase 1 capacity guards

apps/fc-desktop/resourcequota.yaml

@@ -0,0 +1,36 @@
+# FlowerCore Remote Desktop - namespace ResourceQuota (GitOps-managed)
+#
+# Adopts the live fc-desktop-session-cap object created during the
+# 2026-05-19 prewarm-cascade triage. Sprint 44 Phase 1 keeps the pod,
+# CPU, and memory guard unchanged, then adds storage/PVC backstops from
+# the fc-desktop CPU expansion substrate.
+#
+# Two-phase deploy note:
+#   Phase A: apply this ResourceQuota and limitrange.yaml with the current
+#   FlowerCore.RemoteDesktop image.
+#   Phase B: bump the service image only after the RemoteDesktop service
+#   admission/fair-share code lands in that repo.
+apiVersion: v1
+kind: ResourceQuota
+metadata:
+  name: fc-desktop-session-cap
+  namespace: fc-desktop
+  labels:
+    app.kubernetes.io/name: fc-desktop
+    app.kubernetes.io/part-of: remotedesktop
+    app.kubernetes.io/component: capacity-guard
+    app.kubernetes.io/managed-by: argocd
+    flowercore.io/owner: infra
+  annotations:
+    flowercore.io/rationale: |
+      Operator-requested limit 2026-05-19: cluster CPU exhausted by RD
+      pool prewarm cascade. Preserve count/pods=15 plus requests.cpu=8
+      and requests.memory=16Gi until capacity expansion lands.
+    flowercore.io/phase: sprint-44-cx-9-phase-a
+spec:
+  hard:
+    count/pods: "15"
+    requests.cpu: "8"
+    requests.memory: "16Gi"
+    requests.storage: "500Gi"
+    persistentvolumeclaims: "30"