chore: regenerate high-risk data paths for fluid-telegram-operator

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-08T22:12:56Z"
+generated_at: "2026-10-09T17:59:49Z"
 source: ops-warden/registry/routing/catalog.yaml
-catalog_revision: "d470f2e5a7443db04119eb4d369687abb922e777"
-catalog_revision_date: "2026-10-08T23:25:22+02:00"
+catalog_revision: "23ba584ccde5ff126dd366805e9dee71e04e4535"
+catalog_revision_date: "2026-10-09T19:59:49+02:00"
 catalog_dirty: false
-high_risk_lane_count: 33
+high_risk_lane_count: 34
 concrete_path_count: 17
 
 # Graded high but not a single KV address -- a routing pattern, a broker
@@ -23,6 +23,7 @@ concrete_path_count: 17
 no_concrete_path:
   - database-dynamic-credentials
   - flex-auth-decision-envelope-signing-key
+  - fluid-telegram-operator
   - informed-decision-sitting-requester-login
   - inter-hub-bootstrap-ssh
   - net-kingdom-lldap-bind-credential