docs: complete hub-core package slice

docs/hub-core-extraction-boundary.md

@@ -74,6 +74,9 @@ Current implementation status:
 - 2026-06-06: progress event and capability request adapter seams were added.
   Hub-core uses generic JSON context fields where State Hub currently has
   dev-specific workstream/task/topic/decision foreign keys.
+- 2026-06-07: progress and capability REST router factories were added. T05 now
+  has the package-side models, schemas, routers, migration scaffold, and shared
+  utilities needed before T06/T08.
 
 ## Extract Now
 
@@ -92,6 +95,8 @@ rewriting and small router seams:
 | `api/schemas/agent_message.py` | Generic message schemas. |
 | `api/schemas/tpsc.py` | Generic TPSC schemas. |
 | `api/routers/messages.py` | Mostly self-contained generic router. |
+| `api/routers/progress.py` | Generic progress-event router once dev-hub foreign keys move behind `subject_refs` or extension mapping. |
+| `api/routers/capability_requests.py` | Generic capability catalog/request router once dev-hub flow side effects and task unblocking stay in dev-hub. |
 | `api/routers/tpsc.py` | Generic catalog and GDPR report router. |
 | `api/routers/policy.py` | Generic policy document router if policy roots become configurable. |
 

workplans/CUST-WP-0025-fos-hub-bootstrap.md

@@ -8,7 +8,7 @@ status: active
 owner: custodian
 topic_slug: custodian
 created: "2026-03-20"
-updated: "2026-06-06"
+updated: "2026-06-07"
 state_hub_workstream_id: "293a74fe-a85a-4ad6-8933-23d52a72fe8b"
 ---
 
@@ -143,7 +143,7 @@ record in `the-custodian`.
 
 ```task
 id: CUST-WP-0025-T05
-status: in_progress
+status: done
 priority: high
 state_hub_task_id: "04bf480c-8847-4a89-a4f2-e7c5fc51088d"
 ```
@@ -185,6 +185,12 @@ requests use JSON request/fulfillment context fields instead of workstream/task
 columns. This keeps hub-core reusable while giving State Hub a migration path
 for its dev-specific references.
 
+Completed package slice (2026-06-07): added the remaining generic REST router
+factories for progress events and capability catalog/request lifecycle. With
+models, schemas, routers, Alembic templates, and shared utilities present in
+`/home/worsch/hub-core`, T05 is complete enough for T06 MCP base-server work
+and T08 State Hub import refactoring to begin.
+
 ### T06 — Hub-core FastMCP base server
 
 ```task