diff --git a/workplans/MAS-WP-0003-provider-live-test.md b/workplans/MAS-WP-0003-provider-live-test.md
index 90c7336..f6186e5 100644
--- a/workplans/MAS-WP-0003-provider-live-test.md
+++ b/workplans/MAS-WP-0003-provider-live-test.md
@@ -180,7 +180,7 @@ or are stripped.
 
 ```task
 id: MAS-WP-0003-T06
-status: progress
+status: done
 priority: high
 state_hub_task_id: "aadd3010-da3f-5e38-b62d-0dcf489b1455"
 ```
@@ -193,8 +193,11 @@ the outbox unsent. The entrypoint passes `MAS_MAX_SENT` (manifest: 300) and
 routes null-sender mail (Postfix bounces) to `discard:`, so nothing else can
 use the relay outside the count. A unit test covers the cap. The container
 was verified locally: bounces are discarded and replies go to TEM.
-Remaining: deploy, and mark the one reply already sent (GS-85QJ8WC09P) as
-counted.
+Deployed 2026-10-18 (image `mas-live:wp0003-20261018c`). Live: the ticket
+service runs with `--max-sent 300` and null-sender mail goes to `discard:`.
+The one reply sent earlier (GS-85QJ8WC09P) is marked `sent=1`, so the count
+starts at 1/300. Outbox rows 1-5 predate the relay and were never sent. To
+change the cap, edit `MAS_MAX_SENT` in the manifest and restart the pod.
 
 ## Close the review