chore: refresh high-risk route artifact

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a0290b-3241-74c3-b868-6049545af836

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-08-22T18:21:24Z"
+generated_at: "2026-08-22T18:54:51Z"
 source: ops-warden/registry/routing/catalog.yaml
-catalog_revision: "8280c0b7b7f1e134be29d64bf24483247932c661"
-catalog_revision_date: "2026-08-22T19:08:21+02:00"
+catalog_revision: "e3b9b1620c67236d7ba2c53512e7113819ea20a9"
+catalog_revision_date: "2026-08-22T20:54:45+02:00"
 catalog_dirty: false
-high_risk_lane_count: 20
+high_risk_lane_count: 21
 concrete_path_count: 14
 
 # Graded high but not a single KV address -- a routing pattern, a broker
@@ -26,6 +26,7 @@ no_concrete_path:
   - object-storage-sts
   - openbao-api-key
   - openbao-platform-admin-login
+  - openbao-shamir-recovery-ceremony
   - ops-warden-warden-sign-token
 
 paths: