chore(openspec): archive replace-mock-api-wave-5

The merge creates the store-directory capability (two requirements, six scenarios) and updates the mall's store-and-marketing requirement so the store directory and store home read live shops and order surfaces name their shop. openspec validate --all --strict stays green at 13 specs.
2026-09-17 17:13:49 +00:00
parent d0b6350d2d
commit b44ba39e8c
8 changed files with 46 additions and 2 deletions
@@ -117,8 +117,16 @@ The mall SHALL provide B2B2C mall-style login, register and forgot-password pane
 - **THEN** the stored session is cleared and the shopper is returned to sign-in
 ### Requirement: Store and marketing pages
-The mall SHALL provide a store directory, store home, timed seckill page, collective-buy list and points-mall home using fixed bilingual mock content. Marketing pages MAY be display-only except navigation to product detail.
+The mall SHALL provide a store directory and store home reading live shops from the shop API, with each store's products coming from the catalog API, and SHALL keep the timed seckill page, collective-buy list and points-mall home on fixed bilingual content for now. The cart, payment and order surfaces SHALL show each order's shop by name from the shop API rather than a generic label. Marketing pages MAY be display-only except navigation to product detail.
 #### Scenario: navigate storefront discovery channels
 - **WHEN** a shopper opens stores, seckill, collective or integral routes
- **THEN** each page renders the appropriate B2B2C mall-style banner/filter/session/card layout and product links resolve to mock product details
+- **THEN** each page renders the appropriate B2B2C mall-style banner/filter/session/card layout, the store directory and store home list real shops, and product links resolve to product detail
 #### Scenario: order surfaces name the shop
 - **WHEN** a shopper views a cart line, a payment group or an order card
 - **THEN** the shop is shown by its name, not a placeholder
 #### Scenario: a shop without a profile still renders
 - **WHEN** a shop has no profile row
 - **THEN** the directory and store home render it without inventing logo, scores or copy
@@ -0,0 +1,36 @@
 # store-directory Specification
 ## Purpose
 The buyer-facing view of a shop: its public profile — identity, contact and service copy — alongside the products it sells, so the store directory, a store's home page and the store card on a product page all read real shops.
 ## Requirements
 ### Requirement: Public shop directory
 `GET /api/shops` SHALL list the active shops without authentication, and `GET /api/shops/{slug}` SHALL return one shop by slug, answering 404 for an unknown slug or a suspended shop. Each entry SHALL carry the shop's id, slug, bilingual name and its profile: logo and banner URLs, company, region, bilingual address, bilingual notice and after-sale copy, and four score values. A shop with no profile row SHALL still be returned, with the profile fields absent rather than invented.
 #### Scenario: directory lists active shops only
 - **WHEN** a suspended shop exists alongside active ones
 - **THEN** the directory lists only the active shops
 #### Scenario: store home by slug
 - **WHEN** a shopper opens a shop's slug
 - **THEN** the profile and the shop's products are available, with the products filtered by that shop through the catalog API
 #### Scenario: unknown slug is a 404
 - **WHEN** a shopper opens a slug that does not exist
 - **THEN** the API answers 404 rather than an empty profile
 ### Requirement: Shop profile management
 A platform admin SHALL set a shop's profile with `PUT /api/admin/shops/{id}/profile`, which upserts the profile row and returns the composed shop. Bilingual fields SHALL carry non-empty `en` and `zh` text, and the write SHALL require the `platform_admin` role.
 #### Scenario: profile upsert round-trips
 - **WHEN** an admin sets a profile and then reads the shop publicly
 - **THEN** the public read returns those values
 #### Scenario: incomplete bilingual text is refused
 - **WHEN** an admin submits a notice with only `en` text
 - **THEN** the request is refused and the stored profile is unchanged
 #### Scenario: only platform admins may write
 - **WHEN** a shop owner or customer submits a profile
 - **THEN** the API refuses the write