RPF-WP-0046-T06: eso.token-renewal assurance signal; plan finished

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 150322@bnt-lap001
Assistant-Session: 16a7b788-374e-4915-a1df-fc87ffd9a5e4

workplans/RPF-WP-0046-eso-database-token-renewal.md

@@ -4,7 +4,7 @@ type: workplan
 title: "Keep the dynamic-database ESO parent tokens alive: periodic tokens and a renewer"
 domain: financials
 repo: railiance-platform
-status: active
+status: finished
 owner: railiance-platform
 topic_slug: railiance
 created: "2026-09-23"
@@ -165,7 +165,7 @@ ready.
 
 ```task
 id: RPF-WP-0046-T06
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "2f528e56-ebf0-547e-8d4f-3cb34c348d46"
 ```
@@ -210,3 +210,10 @@ state_hub_task_id: "2f528e56-ebf0-547e-8d4f-3cb34c348d46"
   State Hub `/repos` returns 200. No workload now depends on a lease from the
   replaced max-TTL tokens. Those tokens expire on their own, from about
   2026-10-10.
+- **T06 done.** Hand-offs sent 2026-09-23. rapp-postgres and audit-core were
+  asked to retire or change their 768h mint scripts. railiance-telemetry was
+  asked for an alert on a failed run or no success for 48h. activity-core was
+  told the October re-mint is not needed. `assurance-capture` now emits
+  `eso.token-renewal` (CronJob status timestamps only, 36h budget), and it is
+  healthy on the first live check. The owners' follow-through is tracked in
+  their own repos.