@spree/docs 0.1.276 → 0.1.278

package/dist/developer/core-concepts/returns-exchanges-claims.md

@@ -114,7 +114,7 @@ curl -X PATCH 'https://api.mystore.com/api/v3/admin/orders/or_xxx/returns/ret_xx
 
 Receiving takes the quantities the warehouse actually counted, because partial and damaged returns are normal rather than exceptional. A customer says three items are coming; two arrive; one of those can't be sold again. Only resellable goods go back into stock.
 
-Leave `items` out to receive everything as requested. Refunds default to whatever the return is still owed, and can go back to the original payment method or to store credit.
+Leave `items` out to receive everything as requested. Refunds default to whatever the return is still owed, and can go back to the original payment method or to store credit. A returned item is worth what the customer paid for it after discounts, not its list price, so a free gift sent back refunds nothing. Refunding a return that is owed nothing completes it with no money moved and no refund email; an amount of zero is refused on any return the customer is still owed money on.
 
 ### Where the goods come back to
 
@@ -193,6 +193,8 @@ A replacement creates a new [fulfillment](fulfillments.md) on the original order
 
 The replacement is filed under the order line it replaces, but it doesn't count toward that line's quantity. Editing the line later, from a claim or an [exchange](#exchanges), adds or removes only the goods the customer paid for and leaves the replacement where it is.
 
+A claim never refunds more than the customer paid for the claimed items after discounts. Each claim line reports that ceiling as `paid_amount`.
+
 ## Exchanges
 
 An exchange works like a return, but ends by sending different items instead of refunding:

package/dist/developer/how-to/build-a-marketplace.md

@@ -714,9 +714,16 @@ const tokens = await sellerClient.auth.login({
 sellerClient.setToken(tokens.token)
 
 // A user who runs several sellers picks which one they are acting as
-sellerClient.setSeller('sel_xxx')
+const { sellers } = await sellerClient.me.get()
+sellerClient.setSeller(sellers[0].id)
+
+// The signed-in person edits their own account (name, photo, panel language);
+// the seller business itself is `sellerClient.profile.update(...)`
+await sellerClient.me.update({ first_name: 'Ada', selected_locale: 'de' })
 ```
 
+> **NOTE:** `sellerClient.me` is an object with `get()` and `update()`. Code written against `@spree/seller-sdk` 1.0.0-beta.1 or beta.2 that calls `sellerClient.me()` directly keeps working, but that form is deprecated and logs a one-time warning — switch to `sellerClient.me.get()`.
+
 Authentication is JWT only. **There is deliberately no secret-key equivalent**: a key that acts as a seller without a seller signing in is exactly what the Seller API's design exists to prevent. Sign-in fails for a store staff member who runs no seller, even though staff share the same user class.
 
 The chosen seller travels as `X-Spree-Seller-Id`. The store is derived from the seller server-side and never sent alongside, so no header a client can set widens what it reaches.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@spree/docs",
-  "version": "0.1.276",
+  "version": "0.1.278",
   "description": "Spree Commerce developer documentation for AI agents and local reference",
   "type": "module",
   "license": "CC-BY-4.0",