fix: 立即续费

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

@@ -36,3 +36,24 @@ The client SHALL create a renewal by calling `POST /api/c/v1/orders/create` with
 - **WHEN** neither asset info nor the relevant historical order supplies a valid package ID
 - **THEN** the client SHALL show that renewal is unavailable
 - **AND** the client SHALL not guess an ID from the ordinary package catalog
+
+### Requirement: Renewal buttons SHALL be limited to the homepage and order list
+
+The client SHALL show an `立即续费` button in the homepage asset summary and in every order card in the order list. The client SHALL NOT show a renewal button in the order detail page, package catalog, package-order page, or other pages.
+
+#### Scenario: Customer renews from the homepage
+
+- **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
+
+#### 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
+
+#### Scenario: Customer views another page
+
+- **WHEN** the customer views any page other than the homepage or order list
+- **THEN** the client SHALL NOT show an `立即续费` button

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

@@ -19,6 +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
 
 ## 4. Wallet recharge and payment completion