@zenky/storefront-vue 0.10.8 → 0.10.10

package/CHANGELOG.md

@@ -8,12 +8,35 @@ All notable changes to this project are documented in this file. The format foll
 
 ### Added
 
+- `catalogItemEntity` / `isRenderableCatalogItem` (`/catalog`) — resolve a static catalog
+  item to a discriminated `category | collection` entity, with `id` and `name` lifted out
+  so a consumer can key, title, and scroll-spy a section without branching. Manual
+  catalogs can now contain product collections, which ship a `products_collection` object
+  instead of `category`. The entity is resolved by which object is present rather than by
+  `type`, because the payload (`products_collection`) and `@zenky/storefront-api@1.0.2`
+  (`collection`) disagree on the discriminator; both spellings are read. Items whose
+  entity has no id are treated as malformed and resolve to `null`.
+- `StaticCatalogItem` / `StaticRemoteCatalog` (`/catalog`) — the catalog shapes as the
+  payload actually ships them. The SDK types predate manual catalogs: they omit
+  `products_collection` and `catalog_id`, the latter already returned by the live store
+  profile (`null` for automatic catalogs, filled for manual ones).
+- `buildCollectionSchemas` (`/seo`) — JSON-LD for a products collection page.
 - `useProductList` — fetches a page of products for a category or collection, with the
   include list that keeps per-stock pricing working (`variants.prices`). Three call sites
   in the consuming app built this fetch by hand and had drifted apart; one of them was
   missing `variants.prices` and silently showed every product's store-wide price instead
   of the price of the stock the customer was actually browsing.
 
+### Changed
+
+- `useCatalogStore` (`catalog`, `initCatalog`), `findProductInCatalog`, and the
+  `catalogItem` on `CatalogProductMatch` are typed `StaticCatalogItem` instead of the
+  SDK's `CatalogItem`, so the collection fields are visible on what the store holds.
+  `CatalogItem` values remain assignable, so passing catalog data in is unaffected; a
+  consumer that annotates a value read back out of the store as `CatalogItem[]` needs to
+  widen that annotation.
+- `getRemoteCatalog` returns `StaticRemoteCatalog`, so `catalog_id` is typed.
+
 ## 0.10.7 - 2026-08-02
 
 ### Added

package/README.md

@@ -119,7 +119,7 @@ Pinia falls back to its module-level active instance. Under concurrent SSR that
 belongs to whichever request touched it last, so the lookup succeeds with another user's
 state instead of failing.
 
-Two cases behave differently, and the distinction is verified rather than assumed:
+Two cases behave differently:
 
 - **Inside a store action — safe.** Pinia activates the action's own instance for the
   duration of the call, so resolving another store there returns the right one.
@@ -163,7 +163,9 @@ import {
 
 The full public contract, adapter examples, SSR lifecycle, and security boundary are in
 [Runtime Ports](docs/ports.md). For a step-by-step consumer integration and upgrade
-checklist, see [Consumer Setup](docs/consumer-setup.md).
+checklist, see [Consumer Setup](docs/consumer-setup.md). For a map of what lives in each
+domain folder and how to decide whether new logic belongs here or in the consumer app,
+see [Architecture](docs/architecture.md).
 
 ## Subpath Imports
 
@@ -248,22 +250,6 @@ npm run check:runtime  # import all entries in SSR + reject Node-only output
 npm run check:size     # enforce gzip bundle budgets
 ```
 
-### Local linking with yalc
-
-To iterate on an unreleased change without cutting a version, link the package into a
-consumer app with [yalc](https://github.com/wclr/yalc):
-
-```bash
-# in this package, after a build:
-npx yalc publish
-
-# in the consumer app:
-npx yalc add @zenky/storefront-vue
-
-# after each change here:
-npm run build && npx yalc push
-```
-
 ## Package Scripts
 
 - `build` — bundle the multi-entry ESM package with tsup.