@spree/docs 0.1.262 → 0.1.264

package/dist/developer/core-concepts/webhooks.md

@@ -12,7 +12,7 @@ Webhooks are built on top of Spree's [event system](events.md), providing:
 - **Multi-store support** - Each store has its own webhook endpoints
 - **Event filtering** - Subscribe to specific events or patterns with wildcards
 - **Secure delivery** - HMAC-SHA256 signatures for payload verification
-- **Failure handling** - Failed deliveries are recorded and can be re-sent, and an endpoint that keeps failing is disabled
+- **Failure handling** - Failed deliveries are retried automatically and can be re-sent by hand, and an endpoint that keeps failing is disabled
 - **Full audit trail** - Track every delivery attempt with response codes and timing
 
 ## How Webhooks Work
@@ -269,7 +269,9 @@ end
 
 ### Failed Deliveries
 
-Spree sends each delivery once. Any response other than 2xx — including a timeout or a connection error — marks the delivery as failed, and Spree does not send it again on its own. To send a failed delivery again, re-send it from the delivery log (see below).
+Any response other than 2xx — including a timeout or a connection error — marks the delivery as failed. Spree then sends it again, waiting longer before each try, up to 5 attempts in total over about six minutes. The delivery log shows the outcome of the latest attempt. Retries stop as soon as the endpoint is turned off.
+
+Every attempt carries the same event `id`, so use it to ignore an event your receiver has already processed. To send a delivery again after the retries run out, re-send it from the delivery log (see below).
 
 If an endpoint fails 15 deliveries in a row, Spree disables it and emails the store staff. Fix the endpoint, then turn it back on by marking it active again.
 

package/dist/developer/dashboard/customization/slots.md

@@ -68,7 +68,7 @@ import { usePermissions } from '@spree/dashboard'
 
 function AdminOnlyMenuItem() {
   const { permissions } = usePermissions()
-  if (!permissions.can('manage', 'Spree::User')) return null
+  if (!permissions.can('manage', 'Spree::Customer')) return null
   return <DropdownMenuItem>…</DropdownMenuItem>
 }
 ```

package/dist/developer/dashboard/public-api.md

@@ -229,6 +229,17 @@ import { spreeDashboardPlugin } from '@spree/dashboard/vite'  // Vite plugin: Ta
 import '@spree/dashboard/styles.css'                          // the app's CSS entry
 ```
 
+A host app that builds its own sign-in or onboarding screens, rather than mounting `<Dashboard />`, can reuse the dashboard's building blocks one module at a time without pulling in the app shell:
+
+```ts
+import { AuthShell } from '@spree/dashboard/components/spree/auth-shell'              // two-column sign-in layout
+import { StoreSetupFields } from '@spree/dashboard/components/spree/store-setup-fields' // store name, country, language, currency
+import { useAuthProviders, authCallbackErrorKey } from '@spree/dashboard/hooks/use-auth-providers' // password + SSO options, SSO error copy
+import { loginFormSchema, resetPasswordFormSchema } from '@spree/dashboard/schemas/auth' // Zod schemas for the auth forms
+```
+
+Their translations ship with `@spree/dashboard-core`, so they render translated as soon as its i18n instance is loaded.
+
 A few names exist in both re-exported packages — the design system ships a presentational component and the framework wraps it with data (`ResourceCombobox`, `StatusCard`, `Slot`, `DateRange`, `ResourceMultiAutocomplete`). The facade gives you the framework's version, which is the one an application wants. Reach past it when you want the presentational half:
 
 ```ts

package/dist/developer/tutorial/events.md

@@ -63,7 +63,7 @@ When the consumer is a system you do not deploy your own code into, use a webhoo
 
 Each delivery is an HTTP POST carrying the event name and the same serialized payload. The endpoint's **signing secret is shown once when you create it**: store it in the receiving system and verify every request against it, so the receiver can prove the call came from your store.
 
-Deliveries are retried with exponential backoff, and the dashboard shows the attempt history per endpoint, which is where to look when a third party says they never received something.
+Failed deliveries are retried with increasing delays, and the dashboard shows the delivery history per endpoint, which is where to look when a third party says they never received something.
 
 > **TIP:** Webhooks need no code in your app at all. Reach for a subscriber only when the reaction needs application context or credentials you would rather not hand to a third party. See [events](../core-concepts/events.md) and [webhooks](../core-concepts/webhooks.md).
 

package/package.json

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