diff --git a/workplans/EMAIL-WP-0009-wave2-resource-right-sizing.md b/workplans/EMAIL-WP-0009-wave2-resource-right-sizing.md
index 0e204a0..bdd7271 100644
--- a/workplans/EMAIL-WP-0009-wave2-resource-right-sizing.md
+++ b/workplans/EMAIL-WP-0009-wave2-resource-right-sizing.md
@@ -4,7 +4,7 @@ type: workplan
 title: "Wave-2 resource right-sizing from the 2026-10-21 allocation review"
 domain: infotech
 repo: email-connect
-status: ready
+status: finished
 flavor: implementation
 owner: claude
 topic_slug: email-connect
@@ -26,10 +26,8 @@ Origin: the 2026-10-21 node allocation review (`RESOURCE-WP-0008-T03`, feeding `
 
 ```task
 id: EMAIL-WP-0009-T01
-status: wait
+status: done
 priority: medium
-needs_human: true
-blocking_reason: "Wave-2 cluster write; founder approval for wave 2 not yet given (2026-10-21 interview)"
 state_hub_task_id: "b34ff94e-a2ef-5df1-b7ec-f2a29ae0191f"
 ```
 
@@ -63,3 +61,7 @@ Status stays `wait` / `needs_human`. Local commit only: not pushed, not applied.
 - Change: email-connect `64d81e3`: CPU request 25m -> 5m.
 - Diff: NOT resource-only. Besides requests.cpu, the apply would also replace the `email-connect.railiance.io/rollback-note` annotation text (the source wording from e9b9d1c differs from live) and reorder the container volumeMounts and pod volumes. The volume set itself is unchanged. This drift goes to the founder before apply.
 - Apply (after founder OK): `kubectl apply -k deploy/k8s/railiance`.
+
+## Applied — 2026-10-22 (EMAIL-WP-0009-T01)
+
+Applied under the founder's wave-2 authorization (the-custodian docs/decisions/2026-10-21-cust-wp-0071-delivery-interview.md), after a full-render diff against live that showed resources only, plus the founder-approved annotation and volume reordering. Ready; both ExternalSecrets are synced. Evidence: the-custodian docs/evidence/2026-10-22-wave2-apply.md.