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

Updated by fix-consistency on 2026-05-01:
  - update .custodian-brief.md for the-custodian

.custodian-brief.md

@@ -1,22 +1,16 @@
 <!-- custodian-brief: generated by fix-consistency — do not edit manually -->
 # Custodian Brief — the-custodian
 
-**Domain:** railiance  
-**Last synced:** 2026-05-01 19:53 UTC  
+**Domain:** custodian  
+**Last synced:** 2026-05-01 20:00 UTC  
 **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
 
 ## Active Workstreams
 
-### Cross-Repo E2E Sandbox Framework
-Progress: 8/8 done  |  workstream_id: `b68de20b-e397-4f97-b1be-ad30711fc2a6`
-
 ### Task-Flow-Engine — Declarative Workstation and Requisite Model
-Progress: 0/6 done  |  workstream_id: `781e519b-0dd7-451b-b63c-fad50f999c9c`
+Progress: 3/6 done  |  workstream_id: `781e519b-0dd7-451b-b63c-fad50f999c9c`
 
 **Open tasks:**
-- · T01: Design specification — workstations, assertions, flow definitions  `25ad9022`
-- · T02: Core Python library — pure engine, no FastAPI dependency  `df5ce1f2`
-- · T03: Flow definitions for existing custodian entities  `3d01fc77`
 - · T04: State-hub integration — migrate from enums to engine  `db320d4e`
 - · T05: MCP tools — flow-aware session orientation  `8ea7e49f`
 - · T06: Extraction boundary and future repo scope  `b9242cb4`
@@ -75,6 +69,6 @@ Progress: 0/9 done  |  workstream_id: `9cc32158-2f5c-4ef6-9713-aacce4623d5e`
 ## MCP Orientation (when available)
 
 If the state-hub MCP server is reachable, call:
-`get_domain_summary("railiance")`
+`get_domain_summary("custodian")`
 This provides richer cross-domain context.
 If the MCP call fails, use this file as your orientation source.