docs: record rename blocker after loose-end review

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e727-aa41-7f30-9e9e-6a29dc61d998

WORK-RECORDS.md

@@ -8,6 +8,6 @@
 
 | Kind | ID | Status | Lane | Source |
 | --- | --- | --- | --- | --- |
-| workplan | REUSE-WP-0023 | active | — | workplans/REUSE-WP-0023-access-engine-source-rename.md |
+| workplan | REUSE-WP-0023 | blocked | — | workplans/REUSE-WP-0023-access-engine-source-rename.md |
 | task | REUSE-WP-0023-T01 | wait | — | workplans/REUSE-WP-0023-access-engine-source-rename.md |
 | task | REUSE-WP-0023-T02 | wait | — | workplans/REUSE-WP-0023-access-engine-source-rename.md |

workplans/REUSE-WP-0023-access-engine-source-rename.md

@@ -4,13 +4,13 @@ type: workplan
 title: "Follow the access-engine repository rename in federation sources"
 domain: infotech
 repo: reuse-surface
-status: active
+status: blocked
 flavor: residual
 owner: claude
 origin: residual
 origin_ref: FLEX-WP-0020
 created: "2026-09-20"
-updated: "2026-09-20"
+updated: "2026-09-28"
 state_hub_workstream_id: "65c03b24-4349-5a60-b7d6-79cf54931d06"
 ---
 
@@ -88,3 +88,26 @@ way commerce-canon was handled under REUSE-WP-0021: keep the superseded
 registration disabled with a replacement note rather than deleting it, so the
 rename stays auditable. Confirm the hub's composed index serves the capability
 from the canonical URL with no target warnings.
+
+## Loose-end review — 2026-09-28
+
+Reviewed all 23 repository workplans, including archived files. The 22 closed
+workplans have no unfinished task blocks; T01 and T02 here are the only open
+tasks. Neither can complete before the upstream FLEX-WP-0020 rename lands.
+This workplan is now `blocked`, with both tasks remaining `wait`; no new tasks
+or workplans were opened.
+
+Fresh read-only probes used `curl -sS -L -o <temporary-file> -w '%{http_code}'`
+against the raw capability-index URLs listed above:
+
+- `access-engine/raw/main/registry/indexes/capabilities.yaml`: HTTP **404**.
+- `flex-auth/raw/main/registry/indexes/capabilities.yaml`: HTTP **200** after
+  following redirects.
+
+The 2026-09-20 flex-auth inbox handoff also confirms T01 must follow
+FLEX-WP-0020-T06, with the upstream owner responsible for announcing that the
+new raw index is available. The checked-in source and local roster still use
+`flex-auth`, correctly preserving the working source until that prerequisite
+is met. T02 remains blocked on T01; the hosted registration must follow the
+verified source migration. Resume these existing tasks when the canonical
+access-engine raw index is available and validates successfully.