diff --git a/workplans/STATE-WP-0099-node-allocation-wave1.md b/workplans/STATE-WP-0099-node-allocation-wave1.md
index 2b53c93..e12d391 100644
--- a/workplans/STATE-WP-0099-node-allocation-wave1.md
+++ b/workplans/STATE-WP-0099-node-allocation-wave1.md
@@ -151,7 +151,7 @@ historical 100m cases are kept explicitly through `historical-100m-release.json`
 
 ```task
 id: STATE-WP-0099-T03
-status: todo
+status: done
 priority: high
 state_hub_task_id: "61a60518-4607-5831-acd0-0f648f3a94b4"
 ```
@@ -194,7 +194,7 @@ Also revert the values line in git if the rollback is to be kept.
 
 ```task
 id: STATE-WP-0099-T04
-status: todo
+status: done
 priority: high
 state_hub_task_id: "08ca83df-cf37-502f-9a8c-48c3ef67fae7"
 ```
@@ -233,7 +233,7 @@ restarts again.
 
 ```task
 id: STATE-WP-0099-T05
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "6c1e9863-b7d6-565c-b3b9-8a0e6a690e2e"
 ```
@@ -260,3 +260,11 @@ record whether a routine release (live 390m equal to target 390m) passes.
 Do not lower the API request and do not drop the preflight to get a release
 through. If an urgent release is needed earlier, Bernd decides between waiting
 for wave 2 and an attended release with a brief API outage.
+
+## Applied — 2026-10-21
+
+- Preflight: ok, 605m remaining against a 390m surge (surge read from the values).
+- Helm revision 78: the API requests 390m, health is ok and the schema is current.
+- The upgrade also rolled out image main-c103cbf. The values bump bb525bc was committed on 17 Oct and never deployed; revision 77 ran main-5dd3df9. Those commits were already in main, and their migration c4d5e6f7a8b9 had already been applied. Rollback: `helm rollback state-hub 77`.
+- state-hub-db (namespace databases) requests 70m/416Mi. The CNPG cluster is healthy and the hub stayed connected.
+- Node requests after the probe removal: 3605m. Evidence: the-custodian docs/evidence/2026-10-21-wave1-apply.md.