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

Updated by fix-consistency on 2026-07-27:
  - update .custodian-brief.md for ops-mason

.custodian-brief.md

@@ -1,27 +1,22 @@
-<!-- custodian-brief: generated by statehub register; fix-consistency may replace this file -->
+<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
-# Custodian Brief - ops-mason
+# Custodian Brief — ops-mason
 
-**Project:** ops-mason
+**Domain:** infotech  
-**Domain:** infotech
+**Last synced:** 2026-07-26 22:23 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:** `cee7bedf-2b48-46ef-8601-006474f2ad7a`
 
-## Open Workplans
+## Active Workstreams
 
 ### Bootstrap State Hub integration
+Progress: 3/4 done  |  workplan_id: `d3d405f6-7608-4e8c-88cf-3a32261b103c`
 
-Workplan file: `workplans/MASON-0001-statehub-bootstrap.md`
+**Open tasks:**
+- · Review Generated Integration Files  `ede1aa62`
 
-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=ops-mason&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-07-27