chore(registry): regenerate high-risk data paths for catalog 537d551

Assistant: grok
Assistant-Session: 01a1625d-4770-76a0-8dee-7f5c514a47eb

registry/generated/high-risk-data-paths.yaml

@@ -10,12 +10,12 @@
 # declares it, and is null where the field set has not been established --
 # null means unknown, never 'one field'.
 
-generated_at: "2026-10-20T11:46:44Z"
+generated_at: "2026-10-22T06:53:51Z"
 source: ops-warden/registry/routing/catalog.yaml
-catalog_revision: "e62763cba9e432ba54c12c922ff86213e03cb642"
-catalog_revision_date: "2026-10-20T13:46:28+02:00"
+catalog_revision: "537d551ef28c87def9043e65e316ab4f64f5d9d6"
+catalog_revision_date: "2026-10-22T08:53:33+02:00"
 catalog_dirty: false
-high_risk_lane_count: 39
+high_risk_lane_count: 40
 concrete_path_count: 17
 
 # Graded high but not a single KV address -- a routing pattern, a broker
@@ -30,6 +30,7 @@ no_concrete_path:
   - inter-hub-bootstrap-ssh
   - keycape-attended-case-change
   - keycape-client-secret-generate
+  - kubernetes-railiance01-admin
   - net-kingdom-lldap-bind-credential
   - net-kingdom-privacyidea-admin-token
   - object-storage-sts