## MODIFIED Requirements

### Requirement: Index entry SHALL enforce the bind-phone gate from the asset association state
The system SHALL determine whether phone-verification guidance is required whenever the homepage is entered, using the current asset association state returned by `GET /api/c/v1/asset/info` -> `bound_phone` (empty means the asset is not associated and binding is required). The widened `need_bind_phone` decision stays wechat-login-only: no main phone -> required; main phone exists but the current asset is unassociated -> required; already associated -> not required; global switch off -> never required. The frontend still uses the signal only to decide whether to guide the user, and the backend does not block any business interface on the missing relation.

#### Scenario: User has no main phone
- **WHEN** the account has no main phone and the user enters `pages/index/index`
- **THEN** the system SHALL treat phone verification as required
- **AND** the system SHALL route the user into the bind-phone guide

#### Scenario: User has a main phone but the current asset is unassociated
- **WHEN** the account has a main phone but the current asset is not associated with it
- **THEN** the system SHALL treat phone verification as required
- **AND** the bind page SHALL prefill the account main phone from `asset/info.bound_phone`

#### Scenario: User is already associated
- **WHEN** the current asset is already associated with the account main phone
- **THEN** the system SHALL keep the user on the homepage
- **AND** the system SHALL NOT route the user into the bind-phone guide

#### Scenario: Global switch off
- **WHEN** the global phone-bind switch is off
- **THEN** the system SHALL never route the user into the bind-phone guide regardless of account state