From d21f8d97b834ac8bbab305094a08f1473c860a0a Mon Sep 17 00:00:00 2001 From: tegwick Date: Fri, 21 Aug 2026 10:29:29 +0200 Subject: [PATCH] Record federation and registrar escalation --- workplans/EBIND-WP-0002-capability-index-repair.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/workplans/EBIND-WP-0002-capability-index-repair.md b/workplans/EBIND-WP-0002-capability-index-repair.md index 6fd36bf..bee103f 100644 --- a/workplans/EBIND-WP-0002-capability-index-repair.md +++ b/workplans/EBIND-WP-0002-capability-index-repair.md @@ -43,7 +43,7 @@ Acceptance: id: EBIND-WP-0002-T02 status: wait priority: high -blocking_reason: awaiting federation refresh confirmation and production registrar indexing +blocking_reason: awaiting railiance-platform federation action and repo-manager registrar indexing ``` Run the reuse-surface validator and the repository quality checks, synchronize @@ -70,3 +70,12 @@ refresh the source in State Hub message `9c857277-f0e9-4f29-9def-896bdba1fcc3`. Closeout is waiting on two external-state confirmations: the capabilities appearing in the federated API, and production-registrar assignment of State Hub identifiers for this new workplan and its tasks. + +Rechecked 2026-08-21: the hosted registration still reports `enabled: false` +and the federated API omits both capability IDs. The approved +`reuse-surface-hub-write-token` route was attempted without exposing or +persisting the credential, but OpenBao denied the proxy caller on the owning +runtime lane. The enable-and-compose action is escalated to the lane owner in +State Hub message `ad3221d0-ccd5-4f90-89b3-8bfec24a1f49`. The unread registrar +request was also rerouted to `repo-manager` in message +`5c74f09d-6ee6-4bac-b02f-18e6ab9ad173`.