docs: start hub-core MCP base server

docs/hub-core-extraction-boundary.md

@@ -77,6 +77,8 @@ Current implementation status:
 - 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.
+- 2026-06-07: `HubCoreMCPServer` was added as the first T06 slice. It wraps the
+  generic REST endpoints with FastMCP tools and keeps the MCP layer stateless.
 
 ## Extract Now
 
@@ -184,7 +186,6 @@ to import it:
 
 ## Next Step
 
-Create the `/home/worsch/hub-core` package with only the first package slice,
-commit that seed independently, then return to `/home/worsch/state-hub` for the
-first import-based refactor. Do not rename State Hub to dev-hub until T05-T08
-prove the shared package boundary.
+Continue T06 by adding DoI and FOS §10 risk/alert surfaces, then return to
+`/home/worsch/state-hub` for the first import-based refactor. Do not rename
+State Hub to dev-hub until T05-T08 prove the shared package boundary.

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

@@ -195,7 +195,7 @@ and T08 State Hub import refactoring to begin.
 
 ```task
 id: CUST-WP-0025-T06
-status: todo
+status: in_progress
 priority: high
 state_hub_task_id: "6b49d94a-b1ea-4507-a8a3-e27c1a918491"
 ```
@@ -210,6 +210,13 @@ Add a base MCP server class to hub-core that provides the ~17 generic tools:
 
 Domain-specific hubs inherit and add their own tools.
 
+Implementation start (2026-06-07): added `HubCoreMCPServer` in
+`/home/worsch/hub-core` as a thin FastMCP wrapper over hub-core REST endpoints.
+The base class registers generic tools for domains, messages, capability
+catalog/requests, repos, TPSC, and progress. DoI tools remain a follow-up
+because the DoI cache/evaluator still lives in State Hub and has not yet moved
+into hub-core.
+
 ### T07 — FOS §10 risk and alert tools
 
 ```task