fix: 立即续费不跳转

openspec/changes/update-july-h5-c-iteration/specs/c-notification-reminders/spec.md

@@ -53,3 +53,14 @@ When the user views or activates a notification, the client SHALL call `PUT /api
 - **WHEN** marking a notification read fails
 - **THEN** the client SHALL retain the unread state or refresh it from the backend
 - **AND** the failure SHALL not prevent the user from viewing other asset or notification content
+
+### Requirement: Multi-notification popup SHALL communicate horizontal navigation
+
+When the homepage notification popup contains more than one notification, the client SHALL make the horizontal swipe interaction visible to the user and SHALL retain the current-position indicator.
+
+#### Scenario: User opens multiple unread notifications
+
+- **WHEN** the homepage popup contains two or more notifications
+- **THEN** the popup SHALL display an explicit `左右滑动切换通知` hint
+- **AND** the user SHALL be able to move between notifications by swiping horizontally
+- **AND** the popup SHALL display the current notification position

openspec/changes/update-july-h5-c-iteration/specs/legacy-package-renewal/spec.md

@@ -13,12 +13,12 @@ The H5/C client SHALL keep discontinued packages out of the ordinary package cat
 
 - **WHEN** asset info returns a discontinued package through `current_package_id`
 - **THEN** the client SHALL expose that ID only in the eligible renewal context
-- **AND** the client SHALL allow the customer to continue through the existing package-order flow
+- **AND** the client SHALL allow the customer to continue through the existing standard order/payment flow without navigating to the package catalog
 
 #### Scenario: Existing customer renews from a historical order
 
 - **WHEN** a historical order returns one or more valid `package_ids`
-- **THEN** the client SHALL use those IDs for the renewal selection when the existing renewal flow provides that entry
+- **THEN** the client SHALL use those IDs for the renewal selection when the order-list renewal entry is used
 - **AND** the client SHALL preserve the historical order data unchanged
 
 ### Requirement: Renewal SHALL reuse the standard order creation contract
@@ -45,13 +45,13 @@ The client SHALL show an `立即续费` button in the homepage asset summary and
 
 - **WHEN** the homepage asset summary is displayed
 - **THEN** the client SHALL show an `立即续费` button
-- **AND** tapping it SHALL start the standard renewal flow for the asset's current package ID when one is available
+- **AND** tapping it SHALL directly start the standard order/payment flow for the asset's current package ID when one is available
 
 #### Scenario: Customer renews from an order card
 
 - **WHEN** an order is displayed in the order list
 - **THEN** the client SHALL show an `立即续费` button for that order
-- **AND** tapping it SHALL use the order's package IDs for the standard renewal flow
+- **AND** tapping it SHALL directly start the standard order/payment flow for that order's package IDs without navigating to the package-order page
 
 #### Scenario: Customer views another page
 

openspec/changes/update-july-h5-c-iteration/tasks.md

@@ -19,7 +19,7 @@
 - [x] 3.2 Keep discontinued packages out of the ordinary package catalog for new customers and agents
 - [x] 3.3 Add the eligible existing-customer renewal path using `current_package_id` or historical `package_ids`
 - [x] 3.4 Reuse `POST /api/c/v1/orders/create` for renewal and preserve selected identifier, package IDs, payment method, and existing payment result handling
-- [x] 3.5 Show `立即续费` only on the homepage asset summary and every order-list card
+- [x] 3.5 Show `立即续费` only on the homepage asset summary and every order-list card, with direct order/payment handling
 
 ## 4. Wallet recharge and payment completion