james/vmall
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(openspec): archive the mock-migration waves and green the spec set

Browse Source 
Archive the three completed changes behind replace-mock-api-wave-1/2/3. Each
merge applied cleanly to the main specs:

- catalog gains the Public product browse requirement (subtree filtering and
  price sort)
- frontend-mall picks up the per-domain adapter, the pinned home page, the
  discovery-page changes, the live auth panels and the live transaction flows
- cart's Server-side cart requirement now documents the shop and stock carried
  by every line

Also replace the TBD Purpose placeholder in all eleven specs with a one-line
description of what each capability covers. Those placeholders predate this
work and were the only reason `openspec validate --all --strict` reported
0 passed / 11 failed; it now reports 11 passed / 0 failed.
This commit is contained in:
james
2026-09-17 16:36:10 +00:00
parent e1a0a5dbdb
commit 2136a48fbe
28 changed files with 84 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files
openspec/specs/cart/spec.md
+7 -2
View File
@@ -1,10 +1,12 @@
# cart Specification
## Purpose
TBD - created by archiving change cart-checkout-orders. Update Purpose after archive.
A per-user Redis cart holding SKU quantities, read back with product, price, stock and shop snapshots.
## Requirements
### Requirement: Server-side cart
Authenticated shoppers SHALL have a Redis-backed cart keyed by user id, containing sku_id + qty entries.
Authenticated shoppers SHALL have a Redis-backed cart keyed by user id, containing sku_id + qty entries. Reading the cart SHALL return, for every line, the SKU's current price, currency and stock together with the product's name, image and owning shop, so the storefront can group lines by shop and cap quantity without reading the fixed-data catalog. Lines whose SKU has become inactive or unpurchasable SHALL be omitted from the view.
#### Scenario: add and update
- **WHEN** a shopper POSTs sku + qty, then PUTs a new qty
@@ -14,3 +16,6 @@ Authenticated shoppers SHALL have a Redis-backed cart keyed by user id, containi
- **WHEN** adding a SKU that is inactive or whose product is not published
- **THEN** the API returns 400
#### Scenario: cart view carries shop and stock
- **WHEN** a shopper reads a cart holding SKUs from more than one shop
- **THEN** each line reports its shop and the SKU's current stock, so the storefront can group the lines per shop and cap quantity from the response alone