chore: hub writeback for KAIZEN-WP-0009 registration

State Hub C-06 created workstream and tasks; write state_hub IDs into
the workplan file and refresh .custodian-brief.md.

.custodian-brief.md

@@ -1,18 +1,29 @@
 <!-- custodian-brief: generated by fix-consistency — do not edit manually -->
 # Custodian Brief — kaizen-agentic
 
-**Domain:** infotech
-**Last synced:** 2026-07-03 16:44 UTC
+**Domain:** agents
+**Last synced:** 2026-07-16 08:35 UTC
 **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
 
 ## Active Workstreams
 
-*(none — repo may need first-session setup)*
+### Forward-deployed agency: engagements, Kai ledger, host-operator pilot
+Progress: 1/11 done  |  workplan_id: `70f7afb1-78f1-4e3b-8437-48840b5b58cc`
+
+**Open tasks:**
+- · Accept open decisions  `d624072d`
+- · host-operator Role package  `407eae88`
+- · Phase 1 engagement layout + pilot record  `c90fd780`
+- · Bound agent definition  `e48f0ec3`
+- · Ramp checklists  `3c166660`
+- · Kai ledger (Phase 1)  `16e90a62`
+- · CLI engagement group  `52f7d872`
+- … and 3 more open tasks
 
 ---
 ## MCP Orientation (when available)
 
 If the state-hub MCP server is reachable, call:
-`get_domain_summary("infotech")`
+`get_domain_summary("agents")`
 This provides richer cross-domain context.
 If the MCP call fails, use this file as your orientation source.