1.3 KiB
1.3 KiB
1. Post-Bind Manual Re-Login
- 1.1 Route mandatory bind success to
pages/login/logininstead of continuing directly topages/index/index - 1.2 Show a one-time prompt that the user needs to log in again after successful binding
- 1.3 Preserve the previously entered identifier so the login input stays prefilled after returning
- 1.4 Ensure the restored identifier does not auto-trigger login and the user must manually tap login
2. Flow Compatibility
- 2.1 Keep the existing non-mandatory bind completion behavior unchanged
- 2.2 Remove dependence on automatic post-bind wechat-login continuation
- 2.3 Keep the normal homepage bind gate behavior for later homepage entries
- 2.4 Remove dependence on a one-time homepage bypass for mandatory bind success
3. API Contract Preservation
- 3.1 Keep using the existing login and bind-phone API contracts
- 3.2 Avoid adding a backend endpoint or changing current response schemas
4. Regression Verification
- 4.1 Verify mandatory bind success returns to the login page with the identifier still visible
- 4.2 Verify the login page shows the re-login prompt after bind success
- 4.3 Verify login does not auto-start until the user clicks login
- 4.4 Verify ordinary bind entry from homepage actions still follows the current completion path