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

Updated by fix-consistency on 2026-04-22:
  - update .custodian-brief.md for railiance-cluster

.custodian-brief.md

@@ -1,39 +1,13 @@
 <!-- custodian-brief: generated by fix-consistency — do not edit manually -->
-# Custodian Brief — railiance-bootstrap
+# Custodian Brief — railiance-cluster
 
 **Domain:** railiance  
 **Last synced:** 2026-04-22 20:46 UTC  
 **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
 
-## Current Goal
-
-Install k3s and Kubernetes Baseline on the HostEurope Server
-
 ## Active Workstreams
 
-### ThreePhoenix — HA Cluster Implementation
-Progress: 0/7 done  |  workstream_id: `9e208376-23f1-40c7-9813-fac1f7d6ad3b`
-
-**Open tasks:**
-- · Phase 1 — K3s HA cluster setup (3-node embedded etcd)  `1f8a8668`
-- · Phase 2 — Longhorn distributed storage  `b1d4e0fa`
-- · Phase 3 — PostgreSQL HA (repmgr + Pgpool-II)  `11283b4c`
-- · Phase 4 — Gitea HA (reference stateful application)  `4a20e593`
-- · Phase 5 — Nginx ingress + Cert-Manager SSL  `68315a40`
-- · Phase 6 — Phoenix CronJob automation (weekly node rotation)  `f658aa6a`
-- · Phase 7 — Monitoring stack + acceptance audit checklist  `70f6c8ab`
-
-### Staged Promotion Lifecycle
-Progress: 0/7 done  |  workstream_id: `cb72d3ba-1863-43c2-a2a5-49ac75fc2603`
-
-**Open tasks:**
-- · S0.1 — Write deployment lifecycle spec (docs/deployment-lifecycle.md)  `fbfc341f`
-- · S0.2 — Define railiance/ directory schema and app.toml contract  `523cf928`
-- · S0.3 — Overlay repo pattern and create_railiance_overlay_repo.sh  `7cd378f2`
-- · S1 — railiance run command (STAGE 1 local dev tooling)  `95c3311b`
-- · S2 — Canary Helm chart template (STAGE 2 infrastructure)  `47b8cd47`
-- · S2 — railiance deploy --stage 2 and observation tooling  `6a5c7422`
-- · S3 — railiance promote, rollback, and reference onboarding guide  `476198f6`
+*(none — repo may need first-session setup)*
 
 ---
 ## MCP Orientation (when available)