diff --git a/.custodian-brief.md b/.custodian-brief.md
index 86c0e6c..70010a1 100644
--- a/.custodian-brief.md
+++ b/.custodian-brief.md
@@ -2,7 +2,7 @@
 # Custodian Brief — railiance-cluster
 
 **Domain:** financials  
-**Last synced:** 2026-10-16 19:05 UTC  
+**Last synced:** 2026-10-13 18:24 UTC  
 **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
 
 ## Current Goal
@@ -11,17 +11,12 @@ Install k3s and Kubernetes Baseline on the HostEurope Server
 
 ## Active Workstreams
 
-### Review NetKingdom signer runtime and node-local storage readiness
-Progress: 1/3 done  |  workplan_id: `f383557d-c8a8-553e-adcd-9f82ff9c2929`
-
-**Open tasks:**
-- ► Review the bounded native preflight and storage action  `7f4320c6`
-- · Verify the approved runtime and storage result  `747a8d77`
+*(none — repo may need first-session setup)*
 
 ## Inbox Hygiene
 
 **Stale unread:** 6 message(s) older than 3 day(s) — triage at session start.
-**Missing thread_id:** 8 unread message(s) lack supersession chains.
+**Missing thread_id:** 6 unread message(s) lack supersession chains.
 - ! the-custodian: Workplan 'three-phoenix-ha-cluster' is blocked with no wait task  `a1368d99`
 
 ---
diff --git a/workplans/RCLUSTER-WP-0018-keycape-original-tls-recovery.md b/workplans/RCLUSTER-WP-0018-keycape-original-tls-recovery.md
index 78f7319..f8ff4eb 100644
--- a/workplans/RCLUSTER-WP-0018-keycape-original-tls-recovery.md
+++ b/workplans/RCLUSTER-WP-0018-keycape-original-tls-recovery.md
@@ -44,6 +44,26 @@ separate receipts, not claimed by this completed preparation task.
 Evidence: the-custodian docs/changes/netkingdom-target-2026-10-16/
 recovery-owner-handoffs-r1/ and prior recovery-attempt-r1/t35-t36-source-next/.
 
+Publication return, 2026-10-17: normal owner source publication at
+c562d7134c38679952a8ffd17a8a893a900aef0d was applied on primary/railiance01
+with expected and derived commits equal. Read-only source/remote/Hub proof
+verified this workplan's five exact task ID/UUID/status bindings and three
+internal dependency edges. Receipts are retained in the Custodian packet
+docs/changes/netkingdom-target-2026-10-17/railiance-cluster-projection.json and
+cluster-publication-readback.json. The later legitimate C23 lifecycle repair
+at 26671d33600e218316d29c9cd020f115ebfb35b2 changed ready to active; active
+is retained. This return records publication separately from the completed
+source preparation above. Original TLS artifact/provider custody, extraction
+and native admission remain T02–T05 obligations; publication proves no TLS
+recovery, private-key custody or native acceptance.
+
+The whole maintenance pipeline's historical-row guard failed for three parent
+rows while 15 task full-row hashes remained unchanged. STATE-WP-0095-T07 and
+RMGR-WP-0019-T06 remain wait; neither publication nor this memo asserts full
+historical-row preservation or restoration. The subsequent forward correction
+restores the brief's committed content to its pre-accident version while restoring
+the original staged/worktree change for its owner; history is not rewound. No legacy deep consistency fix is run by the correction.
+
 ## Establish exact independent original TLS artifact and provider custody metadata
 
 ```task