# Change: Return to login for manual re-login after mandatory phone bind

## Why

The current mandatory bind-success continuation either relies on a homepage bypass workaround or on an automatic follow-up login flow. Both approaches make the post-bind path more fragile than necessary. The desired behavior is simpler: after successful mandatory phone binding, return the user to the login page, tell them they need to log in again, preserve the identifier they already entered, and let the user manually tap login.

## What Changes

- Return the user to `pages/login/login` after successful phone binding when the bind page was entered from the mandatory login gate
- Show a one-time prompt on the login page that phone binding succeeded and re-login is required
- Preserve the identifier the user already entered so the login input stays prefilled after returning
- Require the user to manually tap login again instead of auto-starting the login flow
- Keep the existing non-mandatory bind completion behavior unchanged
- Remove dependence on an automatic post-bind wechat-login recheck for this flow
- Preserve the current login and bind-phone API contracts without adding backend endpoints

## Capabilities

### New Capabilities
- `post-bind-manual-relogin`: Define the mandatory post-bind return-to-login and identifier-preservation flow

### Modified Capabilities
- `index-phone-bind-gate`: Allow mandatory bind completion from the login gate to return to login instead of homepage

## Impact

- Affected code: `pages/bind/bind.vue`, `pages/login/login.vue`, `pages/index/index.vue`
- Affected flow: mandatory phone binding, post-bind routing, login input restoration, manual re-login
- No backend API changes
- No login or bind-phone response schema changes
