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

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

.custodian-brief.md

@@ -1,8 +1,8 @@
 <!-- custodian-brief: generated by fix-consistency — do not edit manually -->
 # Custodian Brief — issue-core
 
-**Domain:** custodian  
-**Last synced:** 2026-06-19 19:09 UTC  
+**Domain:** infotech  
+**Last synced:** 2026-06-23 12:26 UTC  
 **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
 
 ## Active Workstreams
@@ -12,16 +12,16 @@ Progress: 1/7 done  |  workstream_id: `896ace77-21b3-450b-8fb7-254aefc8c570`
 
 **Open tasks:**
 - ! ArgoCD bootstrap (railiance-platform dependency) + issue-core Application  `9b199b1d`
+- ! OpenBao secret: ISSUE_CORE_API_KEY  `ad52527f`
 - ► Kubernetes manifests (namespace, Deployment, Service) in GitOps source  `38887dd6`
 - ► In-cluster backend config (cluster Gitea / markitect)  `10923f1e`
-- · OpenBao secret: ISSUE_CORE_API_KEY  `ad52527f`
-- · Wire activity-core to the live service  `96b14cdb`
-- · End-to-end verification + GitOps runbook  `8d853b8e`
+- ► Wire activity-core to the live service  `96b14cdb`
+- ► End-to-end verification + GitOps runbook  `8d853b8e`
 
 ---
 ## MCP Orientation (when available)
 
 If the state-hub MCP server is reachable, call:
-`get_domain_summary("custodian")`
+`get_domain_summary("infotech")`
 This provides richer cross-domain context.
 If the MCP call fails, use this file as your orientation source.