[e-cline]

What and why

A larger Weft example than weft_notes, built to exercise how Weft's features work together, with the latency of real services in between, and to find bugs the smaller examples don't. It found six; each is fixed here with a regression test (checked to fail without the fix) and a changeset.

examples/weft_shop ("Loom & Co.")

• Server-driven pages: the home and category pages are a tree of CMS blocks kept as data, personalised per shopper (signed in or not, experiment half) and changed at runtime. Each block streams under its own Suspense boundary inside a BlockFrame entrypoint (error boundary with Retry, refetched from its own route, polled when live), and keeps its state when a refresh moves it.
• Synthetic latency (Latency.res): seeded random delays and failures in vp dev/vp run start; gates the tests open, in the order they choose.
• Catalog filters as navigations, "Load more" through an RPC returning server-rendered cards, search suggestions cancelling older requests (Rpc.call with a signal), variant offers refetched by themselves, a cart in a signals store handed down by context, portals (drawer, sign-in dialog), cookie sessions through servy middleware, a three-step checkout, a self-refreshing order page.
• Tests: 45 scenario tests through the plugin's harness; 16 Playwright tests against the build, one project with gated latency and one with seeded random latency and failures. The shop's e2e is added to CI's browser job.

Framework fixes

1. weft: a pending boundary whose content arrived after hydration started, and suspended while hydrating (an entrypoint's chunk still loading), rendered its content a second time after the server's, which stayed unhydrated.
2. weft_signals: the hooks gave useSyncExternalStore no server snapshot, so an entrypoint reading a signal couldn't render on the server (error 15).
3. weft_dom: hydration compared style as written, not as the browser reads it back (hsl → rgb, -0% → 0%), warning about identical styles; autoFocus didn't focus elements rendered after page load. Also new aria and form props.
4. weft_server: Navigation.navigate/load/refresh resolved when their transition started, not once the new page was on screen as documented.
5. weft_server: a navigation the server redirected recorded and pushed the URL it asked for, not the redirect's final URL.
6. Test harness (weft_vite_plugin): no cookies, no redirects, and pages from earlier tests stayed mounted and acted in later ones. It now keeps cookies, follows redirects, and closes a page when the next opens (Bootstrap.start ~signal).

Known follow-ups, not in this PR

• useRefetchable's refetch resolves when its render starts (documented); BlockFrame's Retry waits on isPending before resetting its error boundary.
• After a navigation, a hydrated boundary's new content is inserted after its end marker (nothing visible breaks).
• document.title isn't updated on navigation (already in the server components plan's follow-ups).

Checklist

• pnpm run check, pnpm run build and pnpm run test pass
• Tests cover the change
• A changeset is included (pnpm changeset) if a published package changed

🤖 Generated with Claude Code