From e9b7f4c85237c60ab0fd192744c2825cc6add496 Mon Sep 17 00:00:00 2001 From: tegwick Date: Mon, 21 Sep 2026 02:16:38 +0200 Subject: [PATCH] Pin the generated high-risk path artifact to the committed catalog Co-Authored-By: Claude Opus 5 Assistant: claude-code Assistant-Model: opus Assistant-Process: 63291@bnt-lap001 Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703 --- registry/generated/high-risk-data-paths.yaml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/registry/generated/high-risk-data-paths.yaml b/registry/generated/high-risk-data-paths.yaml index 84d546d..36b0649 100644 --- a/registry/generated/high-risk-data-paths.yaml +++ b/registry/generated/high-risk-data-paths.yaml @@ -10,11 +10,11 @@ # declares it, and is null where the field set has not been established -- # null means unknown, never 'one field'. -generated_at: "2026-09-21T00:11:00Z" +generated_at: "2026-09-21T00:16:33Z" source: ops-warden/registry/routing/catalog.yaml -catalog_revision: "308409bff1fecb588e4667f7e3db335fde9cbbe6" -catalog_revision_date: "2026-09-15T20:38:47+02:00" -catalog_dirty: true +catalog_revision: "baf53602cac7e83741d749ffc9ff7d2ea459a125" +catalog_revision_date: "2026-09-21T02:16:33+02:00" +catalog_dirty: false high_risk_lane_count: 29 concrete_path_count: 15