chore(consistency): sync task status from DB [auto]

Updated by fix-consistency on 2026-06-22:
  - update .custodian-brief.md for hub-core

.custodian-brief.md

@@ -1,27 +1,24 @@
-<!-- custodian-brief: generated by statehub register; fix-consistency may replace this file -->
+<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
-# Custodian Brief - hub-core
+# Custodian Brief — hub-core
 
-**Project:** hub-core
+**Domain:** infotech  
-**Domain:** inter_hub
+**Last synced:** 2026-06-22 17:33 UTC  
-**State Hub:** http://127.0.0.1:8000
+**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
-**Topic ID:** `1f2e4d10-c967-4803-ae6c-7f4b4e806409`
 
-## Open Workplans
+## Active Workstreams
 
-### Bootstrap State Hub integration
+### Import-refactor adapter seams for State Hub closeout
+Progress: 0/3 done  |  workstream_id: `439b559b-fcb7-4d21-b831-cfc9c6bbc1a0`
 
-Workplan file: `workplans/HUB-WP-0001-statehub-bootstrap.md`
+**Open tasks:**
+- · Capability Request Write Router Factory  `f2e0a8a1`
+- · MCP Server Composition Hooks  `f50cd78f`
+- · Regression And Boundary Update  `450676fa`
 
-Open tasks:
+---
-- T01 - Review generated integration files
+## MCP Orientation (when available)
-- T02 - Verify local developer workflow
-- T03 - Seed first real workplan
 
-## Session Start
+If the state-hub MCP server is reachable, call:
-
+`get_domain_summary("infotech")`
-1. Read `INTENT.md`, `SCOPE.md`, and `AGENTS.md`.
+This provides richer cross-domain context.
-2. Check inbox: `GET /messages/?to_agent=hub-core&unread_only=true`.
+If the MCP call fails, use this file as your orientation source.
-3. Scan `workplans/`.
-4. Update task statuses in workplan files as work progresses.
-
-Last generated: 2026-06-16