diff --git a/workplans/USER-WP-0027-account-journey-clarity.md b/workplans/USER-WP-0027-account-journey-clarity.md
index 83f5284..8724586 100644
--- a/workplans/USER-WP-0027-account-journey-clarity.md
+++ b/workplans/USER-WP-0027-account-journey-clarity.md
@@ -9,7 +9,7 @@ flavor: implementation
 owner: codex
 topic_slug: communication
 created: "2026-09-13"
-updated: "2026-09-13"
+updated: "2026-09-22"
 state_hub_workstream_id: "455300ca-ec1e-569e-a584-a8dcda2595cf"
 ---
 
@@ -80,7 +80,7 @@ assurance claims, redirect return parameters or manual step completion.
 
 ```task
 id: USER-WP-0027-T05
-status: progress
+status: done
 priority: high
 state_hub_task_id: "92906113-e28b-58d3-95a7-779e815d1ced"
 ```
@@ -91,6 +91,14 @@ consolidated onboarding diagnosis, scoped lifecycle confirmation/readback, admin
 succession guard review and safe audit/support recovery. Existing headless routes
 are starting points, not browser acceptance. Split into owner workplans as needed.
 
+2026-09-22: closed. Split into USER-WP-0029 and USER-WP-0030 (both finished);
+`tests/journey-coverage.json` marks T03, T06–T08, P02, P04, P07 and P08
+implemented, and `make test-journeys` passes 61 tests. The remaining gaps in scope
+lie outside the admin browser layer and each already has an owner: T02 invited-person
+mail receipt (T06 here), T04 provider lost-factor recovery (T04 here), and T05
+application grant/revoke (USER-WP-0028-T02). This closes the implementation only.
+It does not accept those journeys.
+
 ## Validate all journeys across roles and applications
 
 ```task