arky-sdk 0.11.0 → 0.11.2

package/README.md

@@ -10,14 +10,19 @@ npm install arky-sdk
 
 ## Storefront quick start
 
+The current browser contract is `arky-sdk@0.11.2`. Pin that exact version during the coordinated
+prelaunch cutover so the Server, App, and storefront route/header contracts move together:
+
+```bash
+npm install --save-exact arky-sdk@0.11.2
+```
+
 Copy the Store publishable key from Developer and initialize one client:
 
 ```typescript
 import { initialize } from "arky-sdk";
 
-export const arky = initialize(
-  import.meta.env.PUBLIC_ARKY_PUBLISHABLE_KEY,
-);
+export const arky = initialize(import.meta.env.PUBLIC_ARKY_PUBLISHABLE_KEY);
 ```
 
 `initialize` is synchronous. It makes no request and creates no visitor. Production requests use `https://api.arky.io` by default.
@@ -198,7 +203,8 @@ Authorization: Bearer arky_vst_...
 ```
 
 For cart recovery, `cart.get({ id, token })` sends the recovery credential as
-`X-Arky-Cart-Token`. It is never placed in the request URL or body.
+`X-Arky-Cart-Token`. It is never placed in the request URL or body, and the corresponding response
+is private and non-cacheable.
 
 Locale and market headers are omitted when no explicit context is set, allowing the server to use Store defaults.
 
@@ -259,6 +265,17 @@ type StorefrontCart = StorefrontDto<Cart>;
 
 Storefront request types intentionally contain no Store routing ID. Admin request types remain Store-explicit.
 
+## Verification
+
+Run the complete SDK package contract with one command:
+
+```bash
+npm test
+```
+
+It builds the distributable package and runs every SDK contract case. Consumer compatibility is
+then owned by App and each storefront's `npm test` against the same immutable Server image digest.
+
 ## Adding an endpoint
 
 When adding SDK methods: