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

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

.custodian-brief.md

@@ -1,18 +1,27 @@
 <!-- custodian-brief: generated by fix-consistency — do not edit manually -->
 # Custodian Brief — railiance-apps
 
-**Domain:** (unknown)  
-**Last synced:** 2026-03-27 12:23 UTC  
+**Domain:** railiance  
+**Last synced:** 2026-05-15 13:39 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)*
+### Enable Gitea Container Registry for Cluster Image Publishing
+Progress: 0/6 done  |  workstream_id: `abd268e6-5af9-45ec-93e0-5ffca0211dd0`
+
+**Open tasks:**
+- · T01 — Inventory current registry and routing state  `30075930`
+- · T02 — Enable Gitea package and container registry config  `e4136a4a`
+- · T03 — Ensure `/v2/` reaches the Gitea registry handler  `21c503be`
+- · T04 — Prove Docker login, push, and pull  `5ffd7515`
+- · T05 — Document registry handoff for State Hub deployment  `55c2fd0c`
+- · T06 — Capture backup and retention implications  `d5734ef1`
 
 ---
 ## MCP Orientation (when available)
 
 If the state-hub MCP server is reachable, call:
-`get_domain_summary("")`
+`get_domain_summary("railiance")`
 This provides richer cross-domain context.
 If the MCP call fails, use this file as your orientation source.