chore: regenerate high-risk data paths for keycape-client-secret-generate

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 427672@bnt-lap001
Assistant-Session: a0a2367e-4697-440c-a4e5-9713c009f6d8

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-09T17:59:49Z"
+generated_at: "2026-10-10T08:24:51Z"
 source: ops-warden/registry/routing/catalog.yaml
-catalog_revision: "23ba584ccde5ff126dd366805e9dee71e04e4535"
-catalog_revision_date: "2026-10-09T19:59:49+02:00"
+catalog_revision: "0ae8a0e46703719ab4d8d5ad264faddb9f05d641"
+catalog_revision_date: "2026-10-10T10:24:51+02:00"
 catalog_dirty: false
-high_risk_lane_count: 34
+high_risk_lane_count: 35
 concrete_path_count: 17
 
 # Graded high but not a single KV address -- a routing pattern, a broker
@@ -26,6 +26,7 @@ no_concrete_path:
   - fluid-telegram-operator
   - informed-decision-sitting-requester-login
   - inter-hub-bootstrap-ssh
+  - keycape-client-secret-generate
   - net-kingdom-lldap-bind-credential
   - net-kingdom-privacyidea-admin-token
   - object-storage-sts