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

Updated by fix-consistency on 2026-07-26:
  - update .custodian-brief.md for rein-aharness

.custodian-brief.md

@@ -1,28 +1,24 @@
 <!-- custodian-brief: generated by fix-consistency — do not edit manually -->
-# Custodian Brief — agent-harness
+# Custodian Brief — rein-aharness
 
-**Domain:** agents  
-**Last synced:** 2026-07-17 21:36 UTC  
+**Domain:** infotech  
+**Last synced:** 2026-07-26 10:31 UTC  
 **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
 
 ## Active Workstreams
 
-### Harness Foundation: from prototype to shared runtime
-Progress: 0/7 done  |  workplan_id: `1509b40c-94c9-4a52-8661-22ca05979bca`
+### Bootstrap State Hub integration
+Progress: 0/3 done  |  workplan_id: `e10231e6-a051-43dd-8343-b3963d25cbaa`
 
 **Open tasks:**
-- · Task: Instance manifest spec and validation  `ee8f6f16`
-- · Task: Named tool profiles  `a043a228`
-- · Task: Task intake from activity-core emission  `4970daca`
-- · Task: Kaizen metrics emission per run  `1496a3e9`
-- · Task: Budget enforcement  `9a388b80`
-- · Task: Railiance deployment  `bc1b29b0`
-- · Task: Tenant #1 onboarding — binky-control  `3b724966`
+- · Review Generated Integration Files  `69710723`
+- · Verify Local Developer Workflow  `8a060f11`
+- · Seed First Real Workplan  `ee1b1a63`
 
 ---
 ## MCP Orientation (when available)
 
 If the state-hub MCP server is reachable, call:
-`get_domain_summary("agents")`
+`get_domain_summary("infotech")`
 This provides richer cross-domain context.
 If the MCP call fails, use this file as your orientation source.