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

Updated by fix-consistency on 2026-05-15:
  - update .custodian-brief.md for repo-scoping

.custodian-brief.md

@@ -1,19 +1,28 @@
 <!-- custodian-brief: generated by fix-consistency — do not edit manually -->
 # Custodian Brief — repo-scoping
 
-**Domain:** custodian  
-**Last synced:** 2026-05-15 19:17 UTC  
+**Domain:** capabilities  
+**Last synced:** 2026-05-15 19:59 UTC  
 **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
 
 ## Active Workstreams
 
-### Activity-Core Scope Context API
-Progress: 4/4 done  |  workstream_id: `83a43ab6-d566-41e0-afd7-f2833812564f`
+### Agentic Hierarchy And Intent/Scope Review
+Progress: 0/7 done  |  workstream_id: `83df7082-789f-440e-b7a8-d1f8ecd01cc6`
+
+**Open tasks:**
+- · T01: Capture Sparse-Hierarchy Dataset Baseline  `dd00a642`
+- · T02: Generate Candidate Hierarchies From Facts And Scope Text  `01eb03da`
+- · T03: Add Agentic Draft Generation Layer  `fd572f4d`
+- · T04: Review And Edit INTENT.md / SCOPE.md Drafts  `286d96e0`
+- · T05: Make Dependency Graph Work For Partial Hierarchies  `80bc671c`
+- · T06: Transparent Quality Criteria For Generated Abstractions  `4b74a058`
+- · T07: Re-Run And Compare The Dataset  `cd1a3c14`
 
 ---
 ## MCP Orientation (when available)
 
 If the state-hub MCP server is reachable, call:
-`get_domain_summary("custodian")`
+`get_domain_summary("capabilities")`
 This provides richer cross-domain context.
 If the MCP call fails, use this file as your orientation source.