@zenky/storefront-vue 0.10.8 → 0.10.9

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.