From 74b713988c128dd27d3112d9b9de52bf29da189f Mon Sep 17 00:00:00 2001
From: tegwick <bernd.worsch@gmail.com>
Date: Fri, 15 May 2026 18:34:52 +0200
Subject: [PATCH] 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 | 13 +++++--------
 1 file changed, 5 insertions(+), 8 deletions(-)

diff --git a/.custodian-brief.md b/.custodian-brief.md
index 0cb42c9..050aca6 100644
--- a/.custodian-brief.md
+++ b/.custodian-brief.md
@@ -1,22 +1,19 @@
 <!-- custodian-brief: generated by fix-consistency — do not edit manually -->
 # Custodian Brief — repo-scoping
 
-**Domain:** capabilities  
-**Last synced:** 2026-05-15 16:29 UTC  
+**Domain:** custodian  
+**Last synced:** 2026-05-15 16:34 UTC  
 **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
 
 ## Active Workstreams
 
-### Native Candidate Generation Recovery
-Progress: 2/3 done  |  workstream_id: `088c5674-8edb-447b-8fb5-2a7a34d85ba1`
-
-**Open tasks:**
-- · T03: Re-Run Clean Self-Assessment And Compare  `9ae662c0`
+### Activity-Core Scope Context API
+Progress: 4/4 done  |  workstream_id: `83a43ab6-d566-41e0-afd7-f2833812564f`
 
 ---
 ## MCP Orientation (when available)
 
 If the state-hub MCP server is reachable, call:
-`get_domain_summary("capabilities")`
+`get_domain_summary("custodian")`
 This provides richer cross-domain context.
 If the MCP call fails, use this file as your orientation source.