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

Updated by fix-consistency on 2026-09-04:
  - update .custodian-brief.md for fluid-core

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 1116572@bnt-lap001
Assistant-Session: 8ba9bb93-a72a-4883-b189-2499cce5c400

.custodian-brief.md

@@ -1,27 +1,18 @@
-<!-- custodian-brief: generated by statehub register; fix-consistency may replace this file -->
-# Custodian Brief - fluid-core
+<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
+# Custodian Brief — fluid-core
 
-**Project:** fluid-core
-**Domain:** infotech
-**State Hub:** http://127.0.0.1:8000
-**Topic ID:** `cee7bedf-2b48-46ef-8601-006474f2ad7a`
+**Domain:** infotech  
+**Last synced:** 2026-09-03 23:51 UTC  
+**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
 
-## Open Workplans
+## Active Workstreams
 
-### Bootstrap State Hub integration
+*(none — repo may need first-session setup)*
 
-Workplan file: `workplans/FLUID-WP-0001-statehub-bootstrap.md`
+---
+## MCP Orientation (when available)
 
-Open tasks:
-- T01 - Review generated integration files
-- T02 - Verify local developer workflow
-- T03 - Seed first real workplan
-
-## Session Start
-
-1. Read `INTENT.md`, `SCOPE.md`, and `AGENTS.md`.
-2. Check inbox: `GET /messages/?to_agent=fluid-core&unread_only=true`.
-3. Scan `workplans/`.
-4. Update task statuses in workplan files as work progresses.
-
-Last generated: 2026-09-04
+If the state-hub MCP server is reachable, call:
+`get_domain_summary("infotech")`
+This provides richer cross-domain context.
+If the MCP call fails, use this file as your orientation source.