docs: complete hub-core MCP and risk tools

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: in_progress
+status: done
 priority: high
 state_hub_task_id: "6b49d94a-b1ea-4507-a8a3-e27c1a918491"
 ```
@@ -213,15 +213,19 @@ 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.
+catalog/requests, repos, TPSC, and progress.
+
+Completed MCP slice (2026-06-07): added the remaining orientation tools
+(`get_state_summary`, `get_domain_summary`), DoI passthrough tools
+(`check_repo_doi`, `get_doi_summary`), and FOS §10 risk/alert read tools to
+`HubCoreMCPServer`. The DoI evaluator still remains host-hub-owned, but the
+generic MCP contract now exposes the required DoI tools.
 
 ### T07 — FOS §10 risk and alert tools
 
 ```task
 id: CUST-WP-0025-T07
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "5a54af24-f7cb-451f-874f-66bd6979ab07"
 ```
@@ -233,6 +237,11 @@ ProgressEvent patterns. Define canonical event_type values:
 
 This completes the FOS §10 cross-hub contract.
 
+Completed (2026-06-07): added canonical FOS §10 event constants to
+`hub_core.events`, exposed `/progress/risks` and `/progress/alerts` filtered
+views, and registered matching `get_risks` / `get_alerts` MCP tools. Hub-core
+tests cover the event contract, router views, and MCP tool registration.
+
 ### T08 — Refactor state-hub to import from hub-core
 
 ```task