Close recovery acceptance and reconcile blocked workplans

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e38e-e5bb-7b50-968d-a738a0294997

workplans/USER-WP-0035-onboarding-handoff-findings.md

@@ -4,12 +4,12 @@ type: workplan
 title: "Onboarding handoff findings from the 2026-09-23 operator run"
 domain: communication
 repo: user-engine
-status: active
+status: blocked
 flavor: implementation
 owner: claude-code
 topic_slug: user-engine
 created: "2026-09-23"
-updated: "2026-09-23"
+updated: "2026-09-27"
 related: [USER-WP-0027, USER-WP-0028, NK-WP-0036, NK-WP-0041]
 state_hub_workstream_id: "35aa6adf-255a-5705-9294-a50d98e45f00"
 ---
@@ -60,3 +60,12 @@ governed transactional mail lane (`email-connect` plus the OpenBao delivery
 token) that SCOPE records as operator-owned; U04 and T02 in
 `tests/journey-coverage.json` stay `external-blocked` until then. Do not
 substitute a portal-rendered link for delivery evidence.
+
+2026-09-27: the generic missing-mail-lane description above is superseded
+by EMAIL-WP-0004 and USER-WP-0032/P05: the authenticated mail lane exists and
+live non-sending SMTP/store checks passed. That adapter handles invitation
+outbox events, not the provider's single-use password-setup link. Closing this
+task still needs an owner-supported setup-link delivery handoff and evidence of
+receipt by the intended person; a generic SMTP success is insufficient.
+The latest attended onboarding record still uses out-of-band handoff. No message
+was sent and no setup-link secret was copied into an event or work record.