Repository navigation
Declare the site's live preview (saas-parallel-baselining PB4) - #4
Merged
Merged
Conversation
orun.work's Preview tab shows a coding session's dev server, live from its
box: `orun preview` (orun v2.96.0) runs what a repository declares, and the
session keeps it running while it works.
- apps/web/component.yaml: spec.preview. It installs this app's packages
only (--filter "@app/web..."), builds packages/client (the workspace
package whose dist/ the site loads), writes the GraphQL types from the
committed schema (scripts/generate.cjs, as `pnpm dev` does), then runs
`next dev` alone on localhost:3000 with a 1 GiB heap cap; the tab opens
/. --dns-result-order=ipv4first makes localhost 127.0.0.1 alone, and
`localhost` keeps the proxy's rewrites in-process behind the gateway
(Next normalizes 127.0.0.1 to localhost in a request's URL, and with
-H 127.0.0.1 every rewrite looked external: a 500 under
x-forwarded-proto: https). On a Node without the URLPattern global (it
is Node 24's) `next dev` preloads the site's own urlpattern-polyfill,
which the proxies' matchers need. It is given no BigCommerce store.
- intent.yaml: preview: {component: web}.
- apps/web/next.config.ts: allowedDevOrigins for the preview's hosts
(*.orun-preview.app, preview-gateway-stage.oruncloud.workers.dev), and,
only when NODE_ENV is development, experimental.serverActions
.allowedOrigins for the same hosts. The gateway passes the browser's
Origin through while `next dev` sees a local Host: Next 16 refuses the
hot reload's WebSocket and every Server Action from an origin it is not
told about. `next build` reads neither.
- apps/web/lib/content-security-policy.ts: `next dev` sends no
frame-ancestors (NODE_ENV=development only). The storefront's
`frame-ancestors 'none'` kept the dev server out of the Preview tab's
frame, and the gateway can only add to it. `next build` runs with
NODE_ENV=production, so the deployed storefront's CSP is unchanged.
- baseline.yml: orun v2.88.0 -> v2.96.0 (all three jobs), the first
release that reads spec.preview, so the placement's `orun validate`
checks it. ci.yml (the site's own lane pin) is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019PcpNV6SjymJBPv3nNkC4z
`framing` was inferred as `{} | { frameAncestors: string[] }`, which
TypeScript widens to an optional `frameAncestors?: undefined` that
content-security-policy-builder's directive map refuses (TS2322 in the
site job's typecheck). Annotating it as Record<string, string[]> keeps the
same value: no frame-ancestors under `next dev`, the same header for every
build.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019PcpNV6SjymJBPv3nNkC4z
ruehowl
marked this pull request as ready for review
November 4, 2026 21:37
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The baseline declares its live preview, so orun.work's Preview tab can show a coding session's dev server (saas-parallel-baselining PB4).
apps/web/component.yaml:spec.preview:intent.yaml:preview: {component: web}.apps/web/next.config.ts:allowedDevOrigins: ['*.orun-preview.app', 'preview-gateway-stage.oruncloud.workers.dev']. The gateway gives the dev server a localHostbut passes the browser'sOriginthrough, and Next 16 refuses the hot reload's WebSocket from an unlisted origin (Unauthorized). Onlynext devreads this setting;next buildand the deployed Worker don't.apps/web/next.config.ts, inexperimental(next tooptimizePackageImports), only whenNODE_ENVisdevelopment:serverActions.allowedOriginsfor the same two hosts. For the same reason Next 16 refuses every Server Action behind the gateway ("Invalid Server Actions request", 500).next buildruns withNODE_ENV=production, so the deployed Worker keeps its same-origin check.apps/web/lib/content-security-policy.ts: undernext devonly (NODE_ENV === 'development'), the CSP leaves outframe-ancestors. The storefront sendsframe-ancestors 'none'(or Makeswift's origin) on every page, which kept the dev server out of the Preview tab's frame, and the gateway can only append to a page'sframe-ancestors, not loosen it.next buildruns withNODE_ENV=production, so the deployed storefront's header is byte-for-byte the same..github/workflows/baseline.yml: orunv2.88.0→v2.96.0(all three jobs), the first release that readsspec.preview, so the placement test'sorun validatechecks the declaration; its comments say why.ci.yml(the site's own lane pin,v2.78.4) is unchanged.Nothing about how the baseline builds or deploys changes.
Checked
From a clean clone, with orun v2.96.0, and through a local stand-in of the preview gateway (the dev server sees a local
Hostand the browser's ownOrigin; the page is framed from a foreign origin):orun validateorun preview start --jsonreadyin 14.2 s (warm pnpm store)GET /Host+Originstraight to the dev serverorun preview stopNotes
-H localhost, with--dns-result-order=ipv4first. The proxy rewrites/to/connect-store(and, with a store, routes by locale and channel). Withnext dev -H 127.0.0.1, Next normalizes127.0.0.1in the request's URL tolocalhost, so every rewrite looks external, and behind the gateway (which passesx-forwarded-proto: https) Next proxies it tohttps://localhost:3000and fails (500,EPROTO). Bound tolocalhost,/answers 200 with and withoutx-forwarded-proto: https;ipv4firstmakeslocalhostresolve to127.0.0.1only, so the listener is still loopback IPv4 alone (/proc/net/tcpshows0100007F:0BB8, nothing on tcp6,[::1]:3000refused). The proxy's redirects come back relative (307 /), so they stay on the preview's host.next dev, the preview buildspackages/client(tsup, a few seconds;next.config.tsimports it, and itsdist/is not committed) and runsscripts/generate.cjs(the GraphQL types from the committedbigcommerce.graphql, offline), as the build andpnpm devdo. The proxies buildURLPatternmatchers at import;URLPatternis a global from Node 24 on, and the box runs Node 22, so the preview'snext devpreloadsurlpattern-polyfill(already the site's devDependency, the onevitest.setup.tsloads; it fills the global in only where it is missing). Without itnext devcannot load the proxy at all.env), so/is the storefront's own "Connect your BigCommerce store" page and every other page redirects there — what a fresh deploy without a store serves./compiles no Server Actions, so the action probe answered 404 for every origin; the allow-list is the same dev-only block as the other Next baselines'.wire),leak.test.sh,placement.test.sh(orun v2.96.0) andgen-component-docs.py --checkpass locally; the edited.tsfiles are Prettier-clean with the app's settings. The/?_rscrequest aborted in the frame is the router's fetch superseded by the hot update (net::ERR_ABORTED). Next 16.3'snext devwritesapps/web/AGENTS.mdandCLAUDE.mdon startup; this PR leaves that alone.Generated by Claude Code