@reblu/site-blocks 0.5.0 → 0.6.0

package/CHANGELOG.md

@@ -1,5 +1,41 @@
 # @reblu/site-blocks
 
+## 0.6.0
+
+### Minor Changes
+
+- 74a94ff: Add cart + checkout presentational organisms (REB-829): `AddToCartButton`,
+  `CartIcon`, `CartLineList`, `CartSummary`, `CheckoutLoginPrompt`,
+  `CheckoutForm`, `OrderConfirmation`. Same container/presentational split as
+  `ShopFilters` — data + optional callbacks in, no fetching, RSC-safe by
+  construction (callbacks only do anything when supplied from a Client
+  Component). Spanish-neutral default labels, all overridable via props. Wire
+  them to `@reblu/site-next/cart`'s `useCart()` and the
+  `./shop-route-handlers`/`./shop-server` Route Handlers and server helper.
+
+### Patch Changes
+
+- Updated dependencies [74a94ff]
+  - @reblu/site-contracts@1.5.0
+
+## 0.5.1
+
+### Patch Changes
+
+- 75d3963: Fix `ShopFilters` stranding an active price filter when the price range
+  collapses (REB-827). The Price fieldset previously rendered only when
+  `facets.price.max > facets.price.min`; an active price band can itself
+  collapse that range to a single value (or every currently filtered product
+  can simply cost the same), which made the whole Price group — including the
+  active band's own click-to-clear affordance — disappear, leaving "Clear
+  filters" as the only way out. The group now also renders whenever
+  `active.priceMin`/`active.priceMax` is set, matching the same rule every
+  taxonomy axis already follows, and `shouldRenderShopFilters` stays consistent
+  with it (it already accounted for an active price selection via
+  `hasAnyActiveFilter`).
+- Updated dependencies [87b7fa0]
+  - @reblu/site-contracts@1.4.0
+
 ## 0.5.0
 
 ### Minor Changes

package/README.md

@@ -17,6 +17,7 @@ a different-looking site for every tenant, with zero forks.
 | `MarkdownRenderer` | `.` | Canonical Blog renderer: `marked` → **hast-util-sanitize** (XSS) → component map, with a YouTube-domain allowlist. RSC-safe. |
 | `Treatment`, `Specialty`, `ProfileCard`, `ProductCard` | `.` | Presentational organisms over the SITE API contracts. RSC-safe. |
 | `ShopFilters` | `.` | Plug-and-play shop filter chrome over `GET /api/site/shop/facets`. RSC-safe. See "Shop filters" below. |
+| `AddToCartButton`, `CartIcon`, `CartLineList`, `CartSummary`, `CheckoutLoginPrompt`, `CheckoutForm`, `OrderConfirmation` | `.` | Cart & checkout organisms. RSC-safe by construction. See "Cart & checkout" below. |
 | `useCollection` | `./client` | Headless filterable/sortable/paginated collection hook (facets, category, tag, search). Serves both page and blog indexes. |
 | `Collection` | `./client` | Token-driven presentational grid over `useCollection`. |
 | `ShareButtons` | `./client` | Social share (X / LinkedIn / WhatsApp / copy). |
@@ -181,6 +182,48 @@ has a selection to clear (an active filter can legitimately collapse every
 facet option to zero; the component still renders "Clear filters" then,
 never stranding the visitor with no way back).
 
+## Cart & checkout
+
+Seven organisms over the cart/checkout flow (REB-829), all presentational —
+data + optional callbacks in, no fetching, no cart/zustand dependency of
+their own. Wire them to `@reblu/site-next/cart`'s `useCart()` and the
+`./shop-route-handlers` Route Handlers (see that package's README for the
+wiring steps and a full example app).
+
+| Component | Props it needs | RSC-safe without callbacks? |
+| --------- | --------------- | ---------------------------- |
+| `AddToCartButton` | `onAddToCart?`, `disabled?`, `outOfStock?`, `pending?` | Yes |
+| `CartIcon` | `itemCount`, `href` | Yes |
+| `CartLineList` | `items`, `onQuantityChange?`, `onRemove?`, `liveMessage?` | Yes |
+| `CartSummary` | `subtotal`, `discount?`, `shipping?`, `shippingEnabled?`, `total` | Yes |
+| `CheckoutLoginPrompt` | `open`, `email`, `onEmailChange`, `onClose`, `onSubmitEmail`, `onContinueAsGuest` | Yes (renders `null` when `open` is false) |
+| `CheckoutForm` | `contact`, `onContactChange`, `discountCode`, `onDiscountCodeChange`, `onApplyDiscount`, `onRemoveDiscount`, `onSubmit` | Yes |
+| `OrderConfirmation` | `status` (`'polling' \| 'found' \| 'timeout'`), `order` | Yes |
+
+Same RSC-safety contract as `ShopFilters`'s `OptionLink`: none of these
+components carry `'use client'` themselves — a Server Component may render
+any of them read-only (omit the callback props), and a Client Component
+wires the callbacks to real state/mutations. All labels default to
+Spanish-neutral copy and are overridable via each component's `labels` prop.
+
+`CartLineList`'s `liveMessage` prop renders inside a visually-hidden
+`aria-live="polite"` region — the consuming SITE sets it (e.g. "Cantidad
+actualizada", "Producto eliminado") after a successful mutation; the
+component only renders the live region, it never decides when to announce.
+
+`CheckoutForm` intentionally does NOT collect shipping/billing addresses —
+those field sets vary by tenant shop config far more than the guest-email +
+discount-code flow. Render them via `CheckoutForm`'s `children` slot
+(rendered between the contact and discount sections) if your shop has
+shipping enabled.
+
+`validate-cart`'s rejection path (out-of-stock, price-changed, empty cart)
+surfaces through `CheckoutForm`'s own error-display conventions: pass the
+first `ShopCartValidationError.message` from `client.shop.validateCart(...)`
+as a toast/banner in your page (the component itself has no cart-wide error
+slot — it only owns contact/discount field-level errors via `contactErrors`/
+`discountError`).
+
 ## Security boundaries
 
 Two sinks, two different helpers, in two different packages — do not reach for