fix(observability): schedule pyroscope on frankfurt as intended

platform/cluster/flux/apps/observability/pyroscope/release.yaml

@@ -33,8 +33,11 @@ spec:
         limits:
           cpu: 1000m
           memory: 2Gi
-    nodeSelector:
-      personal-stack/site: frankfurt
+      # The chart reads scheduling keys under `pyroscope`, not at the top
+      # level of values. A top-level `nodeSelector` is silently discarded,
+      # which is how this landed on enschede-gtx-960m-1 instead.
+      nodeSelector:
+        personal-stack/site: frankfurt
     # No public ingress; Grafana datasource talks to it over the cluster
     # service URL. Profiles never leave the cluster.
     minio:

platform/inventory/fleet.yaml

@@ -285,6 +285,7 @@ placement_intent:
     - headlamp
     - obsidian-sync
     - knowledge-api
+    - pyroscope
 
   enschede_only:
     - downloads