Finish OpenRouter provider lane workplan

workplans/RAILIANCE-WP-0010-llm-connect-openrouter-provider-key-lane.md

@@ -4,13 +4,13 @@ type: workplan
 title: "llm-connect OpenRouter Provider Key Lane"
 domain: financials
 repo: railiance-platform
-status: active
+status: finished
 owner: codex
 topic_slug: railiance
 planning_priority: high
 planning_order: 10
 created: "2026-06-29"
-updated: "2026-07-02"
+updated: "2026-08-21"
 depends_on_workplans:
   - RAIL-PL-WP-0002
   - RAILIANCE-WP-0004
@@ -294,7 +294,7 @@ Acceptance:
 
 ```task
 id: RAILIANCE-WP-0010-T08
-status: wait
+status: cancel
 priority: high
 ```
 
@@ -335,6 +335,14 @@ mode-0600 file to the existing KV path, ESO reports a new successful refresh,
 the Deployment is restarted, and the fixture passes; then revoke the old key.
 No provider-key value was read or printed during diagnosis or repair.
 
+Closure 2026-08-21: the railiance-platform portion is complete: the durable
+OpenBao-to-ESO delivery path is repaired, the `ExternalSecret` is synced, and
+the workload consumes the canonical lane. The remaining action is an attended
+replacement of a provider key rejected by OpenRouter, followed by a consumer
+fixture smoke. That operational incident is already tracked by the owning
+consumer as `ACTIVITY-WP-0031-T01`, so this duplicate task is cancelled rather
+than keeping the completed platform-lane workplan active.
+
 ## Exit Criteria
 
 - `CCR-2026-0003` is reviewed, approved, applied, verified, and active.