Messaging UseCase Integrity — E2E

• Verify Claude audit against current server/client code.

• Implement password-reset email-only behavior.

• Hide dead use cases from seller automation catalog.

• Stop admin preview signup from publishing customer signup events.

• Add signup welcome shop-name variable support.

• Filter stale automation mappings on client save.

• Run targeted server/client tests.

• Review the corrected spec against Claude's audit, especially enum-retention vs enum-delete.

• Decide whether to remove stale i18n keys for hidden use cases from apps/web/messages/*/messaging.json or keep them harmless for historical display.

• Before non-dev deploy, scan non-dev MESSAGING_CONFIG.use_case_template_mapping for PASSWORD_RESET, EMAIL_VERIFY, REVIEW_REQUEST.

• If stale mappings exist outside dev, run cleanup before deploying the server catalog change.

• Decide next cycle priority: TemplateCategory rename, compatibility UI hints, or REVIEW_REQUEST scheduler/manual design.

• Seller messaging automation page does not show PASSWORD_RESET, EMAIL_VERIFY, REVIEW_REQUEST.

• Mapping save succeeds after loading a config that previously had a stale use case key.

• Forgot-password request sends email OTP and creates no messaging NotificationRecord for PASSWORD_RESET.

• Admin preview OTP new customer flow creates/logs in preview customer but creates no signup welcome messaging record.

• Signup welcome template with #{쇼핑몰명} or button #{url} can be mapped and receives shop name/homepage URL in dispatch variables.