ReturnTo nudge suppression, contact priority, yearly label, and lock-popup frequency

DEC-0060 - ReturnTo nudge suppression, contact priority, yearly label, and lock-popup frequency

Context

Core policies were mostly aligned, but five execution details remained ambiguous and could create inconsistent UX between auth return, checkout, and result paywall behavior.

Decision

ReturnTo + nudge timing:

• If user completes auth and is returned to a protected in-progress context, do not show goal nudge immediately in that return moment.
• Goal nudge remains contextual-only on Home, Practice Management, and Profile.

Checkout contact priority:

• When checkout is blocked due to missing verified recoverable contact, prioritize verification prompt for the channel most recently used in auth.

Yearly label:

• Show both labels for 12-month one-time option:
  • Yearly Pass
  • Gói 12 tháng (không tự gia hạn)
• Keep savings badges for longer one-time durations versus shorter durations.

Locked-AI popup repetition:

• In result context, each tap on a locked AI feature opens upgrade popup (repeat on every tap).

Downgrade credit handling:

• If user downgrades from Pro Max to Pro with remaining AI credit, retained balance stays in account.
• Retained balance remains usage-locked for features outside current entitlement.

Decision Value

• Prevents interruption of active learning flow right after auth return.
• Makes checkout recovery faster by prioritizing likely-to-pass contact verification path.
• Clarifies yearly packaging language and value communication.
• Removes ambiguity in lock interaction behavior for result page implementation.
• Keeps credit fairness while preserving entitlement boundaries during downgrade.

Rationale

These rules reduce edge-case friction without introducing heavy branching and keep behavior deterministic across auth, payment, and result surfaces.