chore(registry): regenerate high-risk data paths for catalog 207d29e

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 903097@bnt-lap001
Assistant-Session: aa320c8f-c3fa-46e7-8541-0b58e1e45d23

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

@@ -10,17 +10,18 @@
 # declares it, and is null where the field set has not been established --
 # null means unknown, never 'one field'.
 
-generated_at: "2026-10-17T10:08:52Z"
+generated_at: "2026-10-17T10:13:49Z"
 source: ops-warden/registry/routing/catalog.yaml
-catalog_revision: "a14376cf62945b7df619e81c8d59d0208dec7a3f"
-catalog_revision_date: "2026-10-17T12:08:49+02:00"
+catalog_revision: "207d29e8d1d613ca2bdee4ab7628ccc5ca2ec0fb"
+catalog_revision_date: "2026-10-17T12:13:49+02:00"
 catalog_dirty: false
-high_risk_lane_count: 38
+high_risk_lane_count: 39
 concrete_path_count: 17
 
 # Graded high but not a single KV address -- a routing pattern, a broker
 # grant, or a non-KV lane. Nothing here for a policy to deny.
 no_concrete_path:
+  - apps-consumer-handover
   - consumer-owner-deployment
   - database-dynamic-credentials
   - flex-auth-decision-envelope-signing-key