diff --git a/workplans/MAS-WP-0005-spec-errata-v0-1-1.md b/workplans/MAS-WP-0005-spec-errata-v0-1-1.md
index 882f7c1..913d5d1 100644
--- a/workplans/MAS-WP-0005-spec-errata-v0-1-1.md
+++ b/workplans/MAS-WP-0005-spec-errata-v0-1-1.md
@@ -152,7 +152,7 @@ by design. Verify on the live MX by repeating the Google Groups post.
 
 ```task
 id: MAS-WP-0005-T04
-status: progress
+status: done
 priority: medium
 state_hub_task_id: "4ff67908-52c4-5106-b851-e1dec8274226"
 ```
@@ -326,7 +326,7 @@ profile `ionos-forward`. This is the base for the composer (MAS-WP-0006).
 
 ```task
 id: MAS-WP-0005-T10
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "6431ae1e-c449-5732-a40f-99b0644da44a"
 ```
@@ -335,3 +335,15 @@ Switch `mas.coulomb.social` to a v0.2 statute that enables both stand-ins
 and case-insensitive ids. Repeat the IONOS forward test with
 `ticket--gs-…+comments@`. It must now be correlated to the ticket.
 
+- 2026-10-18 done. The live statute is v0.2 (`alternate_syntax`
+  resource+interaction, `resource_id_case: insensitive`), deployed as image
+  `mas-live:v0.2-51bf87c`. The operator sent to `mas-fwd@coulomb.social`
+  (IONOS forward, unchanged since MAS-WP-0003). It arrived at 20:29:57Z
+  for `ticket--gs-85qj8wc09p+comments@` (envelope sender SRS0 from IONOS)
+  and was read as `ticket=gs-85qj8wc09p+comments`
+  (`target_syntax: resource-alternate`). It was **correlated** (200) to
+  GS-85QJ8WC09P with facet `comments`; in MAS-WP-0003 the same forward was
+  404 not-handled. The ticket now holds mail via all four paths: direct,
+  reply, Google Groups (lower-cased) and IONOS forward (stand-in). T04 is
+  complete. `mas explain` also shows "read as … (v0.2 stand-in)".
+