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

Updated by fix-consistency on 2026-03-27:
  - update .custodian-brief.md for the-custodian

.custodian-brief.md

@@ -1,12 +1,15 @@
 <!-- custodian-brief: generated by fix-consistency — do not edit manually -->
 # Custodian Brief — the-custodian
 
-**Domain:** custodian  
-**Last synced:** 2026-03-27 00:55 UTC  
+**Domain:** railiance  
+**Last synced:** 2026-03-27 01:29 UTC  
 **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
 
 ## Active Workstreams
 
+### Cross-Repo E2E Sandbox Framework
+Progress: 8/8 done  |  workstream_id: `b68de20b-e397-4f97-b1be-ad30711fc2a6`
+
 ### FOS Hub Bootstrap — Identity, Hub Extraction, Ops Hub, Fin Hub
 Progress: 0/26 done  |  workstream_id: `293a74fe-a85a-4ad6-8933-23d52a72fe8b`
 
@@ -61,6 +64,6 @@ Progress: 0/9 done  |  workstream_id: `9cc32158-2f5c-4ef6-9713-aacce4623d5e`
 ## MCP Orientation (when available)
 
 If the state-hub MCP server is reachable, call:
-`get_domain_summary("custodian")`
+`get_domain_summary("railiance")`
 This provides richer cross-domain context.
 If the MCP call fails, use this file as your orientation source.

Makefile

@@ -127,10 +127,20 @@ RAILIANCE_SSH   := ssh -i "$(RAILIANCE_KEY)" -o StrictHostKeyChecking=no $(RAILI
 .PHONY: e2e-cron-install
 e2e-cron-install:
 	@test -n "$(REPO)" || (echo "ERROR: REPO is required."; exit 1)
-	$(eval REMOTE_REPO := /home/$(RAILIANCE_USER)/$(REPO))
-	$(eval CRON_CMD := $(REMOTE_REPO)/e2e/run-on-host.sh >> /var/log/$(REPO)-e2e.log 2>&1)
-	$(eval CRON_LINE := 13 3 * * 0 $(CRON_CMD))
-	@echo "Installing cron on $(RAILIANCE_USER)@$(RAILIANCE_HOST) for $(REPO)..."
+	$(eval REPO_PATH     := $(HOME)/$(REPO))
+	$(eval REMOTE_REPO   := /home/$(RAILIANCE_USER)/$(REPO))
+	$(eval CRON_CMD      := $(REMOTE_REPO)/e2e/run-on-host.sh >> /var/log/$(REPO)-e2e.log 2>&1)
+	$(eval CRON_LINE     := 13 3 * * 0 $(CRON_CMD))
+	@test -d "$(REPO_PATH)" || (echo "ERROR: local repo not found: $(REPO_PATH)"; exit 1)
+	@test -f "$(REPO_PATH)/e2e/run-on-host.sh" || (echo "ERROR: no e2e/run-on-host.sh in $(REPO_PATH)"; exit 1)
+	@echo "--- syncing $(REPO) to $(RAILIANCE_USER)@$(RAILIANCE_HOST):$(REMOTE_REPO)"
+	@rsync -az --delete \
+		--exclude=.git --exclude=__pycache__ --exclude='*.pyc' \
+		--exclude=.venv --exclude=node_modules \
+		-e "ssh -i $(RAILIANCE_KEY) -o StrictHostKeyChecking=no" \
+		"$(REPO_PATH)/" \
+		"$(RAILIANCE_USER)@$(RAILIANCE_HOST):$(REMOTE_REPO)/"
+	@echo "--- installing cron on $(RAILIANCE_USER)@$(RAILIANCE_HOST) for $(REPO)"
 	@$(RAILIANCE_SSH) "chmod +x $(REMOTE_REPO)/e2e/run-on-host.sh && \
 		( crontab -l 2>/dev/null | grep -v '$(REPO)-e2e' ; echo '$(CRON_LINE)' ) | crontab - && \
 		echo 'Cron installed:' && crontab -l | grep '$(REPO)-e2e'"

workplans/CUST-WP-0028-e2e-sandbox-framework.md

@@ -168,7 +168,7 @@ Note: manual validation on railiance01 still needed (first live run).
 id: CUST-WP-0028-T06
 status: done
 priority: high
-state_hub_task_id: "038d8085-d2a7-446d-9aff-211afdd5c163"
+state_hub_task_id: "b878804e-a9a2-433d-8c85-cc69f669a1b2"
 ```
 
 The framework is a runner — it still needs a trigger. This task wires up the