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

Updated by fix-consistency on 2026-03-28:
  - update .custodian-brief.md for activity-core

.custodian-brief.md

@@ -1,32 +1,18 @@
 <!-- custodian-brief: generated by fix-consistency — do not edit manually -->
 # Custodian Brief — activity-core
 
-**Domain:** custodian  
+**Domain:** (unknown)  
-**Last synced:** 2026-03-27 23:43 UTC  
+**Last synced:** 2026-03-27 23:59 UTC  
 **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
 
 ## Active Workstreams
 
-### activity-core Foundation — Temporal Backbone
+*(none — repo may need first-session setup)*
-Progress: 21/21 done  |  workstream_id: `e22516cc-4fdf-4dad-a928-a9e04a9fa7c7`
-
-### activity-core Triggers & Ops
-Progress: 0/12 done  |  workstream_id: `3a4f47d9-8bc1-434e-acb4-bed5d4dacda0`
-
-**Open tasks:**
-- · T22: Write schedule_manager.py  `e50550d1`
-- · T23: Bootstrap script to sync schedules on startup  `5a1f7fa3`
-- · T24: Handle misfire policy in schedule config  `00231668`
-- · T25: Test schedule pause/resume lifecycle  `7abfd375`
-- · T26: Implement Event Router service  `68b6610b`
-- · T27: Implement routing rules (event.type + filters → activity_ids)  `9348efea`
-- · T28: Start/signal workflow from Event Router  `cac1f45a`
-- … and 5 more open tasks
 
 ---
 ## MCP Orientation (when available)
 
 If the state-hub MCP server is reachable, call:
-`get_domain_summary("custodian")`
+`get_domain_summary("")`
 This provides richer cross-domain context.
 If the MCP call fails, use this file as your orientation source.