@base44/app-plugin-commerce 0.10.3 → 0.10.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@base44/app-plugin-commerce",
-  "version": "0.10.3",
+  "version": "0.10.4",
   "description": "Base44 Commerce plugin — entities, backend functions, shared commerce engine, admin UI and the commerce skill, shipped as copyable source",
   "keywords": [
     "base44",

package/skills/commerce/references/storefront-verification.md

@@ -1,5 +1,5 @@
 ---
-read_when: "You are about to drive the storefront from a browser script — adding to the cart, stepping quantities, filling the checkout, placing an order."
+read_when: "You are about to drive the storefront from a browser script — adding to the cart, stepping quantities, opening the checkout."
 skip_when: "You are not scripting the storefront."
 ---
 
@@ -37,17 +37,13 @@ DOM is briefly right about the *intent* and wrong about the *state*.
   `/checkout` — URL plus a field of the form on screen — before emptying the
   cart or moving on. Tearing the cart down while still on the cart page, or
   mid-navigation, produces an empty checkout that reads as a routing bug.
-- **Filling the checkout.** Every field is a controlled React input, so writing
-  `el.value` changes nothing React sees. Use the harness's own fill (it
-  dispatches `input` + `change`) — never lift the native setter off
-  `HTMLInputElement.prototype` and call `descriptor.set(v)`: detached from the
-  element it throws `Illegal invocation`, and the workaround it is reaching for
-  is what the fill helper already does.
-- **`placeOrder` ends the page.** It navigates with `window.location.assign`,
-  so a script that placed an order loses its page context and can land back at
-  `/` — while the order itself was created normally. That is the hard
-  navigation, not a broken redirect. The confirmation is reachable at any time
-  from a fresh navigation to `orderReceivedUrl(result)`
-  (`/order-received?order_id=…&order_key=…` — the ids come back in
-  `placeOrder`'s result, and `commerce/admin-orders` `search` has the order
-  either way).
+- **The checkout is shipped code — never fill it, never place an order.** Its
+  logic is the kit's and already tested; what is yours is how it looks. Open
+  `/checkout` with items in the cart and check that: it renders inside the
+  store's chrome, the `.sfui` tokens took (colours, radius, heading face match
+  the rest of the site), the `brand` copy reads in the store's voice, and
+  nothing overflows on a phone-width viewport. Do not type into its fields and
+  do not submit — an order is real store data the owner sees in `/store-admin`,
+  and the platform's "delete the record you created" rule does not fit it (the
+  entities are admin-only; a raw delete skips the engine that releases stock).
+  Empty the cart when you are done.

package/src/commerce/storefront-ui/internal.jsx

@@ -54,10 +54,12 @@ export function CartLineRow({ item, tt, productHref, compact = false, lineExtra
   const formatMoney = useFormatMoney();
   const attrs = attributesLabel(item.attributes);
   const href = productHref ? productHref(item) : null;
+  // storefront-cart sends `image` as a bare URL string; order lines carry {src, alt}.
+  const imageSrc = typeof item.image === "string" ? item.image : item.image?.src;
   return (
     <li className="sfui-line" data-pending={line.pending || undefined} data-compact={compact || undefined}>
       <div className="sfui-line-media" aria-hidden="true">
-        {item.image?.src && <img src={item.image.src} alt="" loading="lazy" />}
+        {imageSrc && <img src={imageSrc} alt="" loading="lazy" />}
       </div>
       <div className="sfui-line-main">
         <p className="sfui-line-name">