Contact-form messages, Builder annotations and publishing via API
Contact-form submissions in the Messages inbox
Messages sent through your storefront contact form now land in the Messages inbox alongside the rest of your customer conversations, instead of only leaving as an email nobody owns. Merchant notifications are routed by the routing key the storefront assigns, so an enquiry reaches the person on your team who handles it.
Annotations in Builder chat
Point at anything in the preview and say what should change: annotations dispatch straight from the chat composer, pins stay attached to the element after the preview reloads, and a batch of them arrives in the chat as one compact card. Element selection and annotation are now a single blue mode, and error reports render DevTools-style rather than as a wall of text.
Publishing via API with a store key
A store-key publish endpoint lets you trigger a publish from your own scripts, so taking a store live can be a step in an automated release instead of a click in the admin.
Also shipped
- Task review folded into the design-session collecting hub, so a session's work and its review sit in one place
- Sandboxes wake silently on their own — no wake button, no waiting screen
- AI assistant creates product images during onboarding — new stores start with pictures on their products instead of empty frames
Fixes
- [api]Publish status segment must not match the UUID param guard
- [builder]Allow ending a feedback session while collecting annotations
- [builder]De-jargon the sandbox wake-up message
- [builder]Re-broadcast annotation pins after the preview reloads
- [builder]Restore toast-style error report styling
- [builder]Self-heal zombie sandbox records when waking the Builder
- [builder]Stop showing a Stop button while the socket is connecting
- [feedback]Fail prepare sessions terminally, isolate prepare sandboxes