Skip to content

Declare the site's live preview (saas-parallel-baselining PB4) - #5

Merged
ruehowl merged 1 commit into
mainfrom
claude/declare-preview
Nov 4, 2026
Merged

ruehowl merged 1 commit into
mainfrom
claude/declare-preview

Conversation

@ruehowl

@ruehowl ruehowl commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

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:
    preview:
      run:
      - sh
      - -c
      - pnpm install --frozen-lockfile --prefer-offline --filter "@app/web..." && exec node_modules/.bin/next dev -H 127.0.0.1 -p 3000
      port: 3000
      path: /
      env:
        NODE_OPTIONS: --max-old-space-size=1024
        NEXT_TELEMETRY_DISABLED: '1'
  • 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 local Host but passes the browser's Origin through, and Next 16 refuses the hot reload's WebSocket from an unlisted origin (Unauthorized). Only next dev reads this setting.
  • apps/web/next.config.ts, inside experimental: serverActions.allowedOrigins for the same two hosts, only when NODE_ENV === "development" (next dev). Behind the gateway a Server Action's Origin is the preview's host while next dev sees Host: 127.0.0.1:3000, and Next refuses it ("Invalid Server Actions request"). next build runs with NODE_ENV=production, so the deployed Worker keeps its same-origin check.
  • .github/workflows/baseline.yml: orun v2.88.0 → v2.96.0, the first release that reads spec.preview, so the placement test's orun validate checks the declaration. ci.yml (the product'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 Host and the browser's own Origin; the page is framed from a foreign origin):

Check Result
orun validate passes
orun preview start --json ready in 18.7 s (warm pnpm store)
GET / 200, 59.0 KB, "next-wp"
foreign Host + Origin straight to the dev server 200
through the gateway stand-in, framed frame 200, failed: FAILED net::ERR_ABORTED /?_rsc=1uexl, hot-reload socket connected
an edit reaches the frame hot update in 1.5s
memory dev server 864 MB at its peak (page compiled, after an edit); the install peaks at 1420 MB
orun preview stop stops it; port freed

Notes

  • No WordPress site is connected in the preview: its URL is the product's WORDPRESS_URL secret, and nothing per-product goes in env. The site handles that itself and renders its bundled sample posts and pages under the "no WordPress site is connected yet" notice.
  • The one aborted request in the frame (/?_rsc=…, ERR_ABORTED) is a route prefetch the hot update cancelled, not a missing asset.
  • Server Actions: this app has none yet, so Next answers any action POST "not found" before its origin check and the check cannot be exercised here. The same block was checked against the running next dev of another Next 16.3 baseline that has actions (sourceplane/subscription-payments), POSTing an action with each Origin: https://abc123def456.orun-preview.app and the stage gateway host pass the origin check (404, action not found), https://elsewhere.example.com is refused (500, "Invalid Server Actions request").
  • Also passing locally: the contract tests (manifest, phases, coverage, rebrand, retouch, bootstrap-defer) and gen-component-docs.py --check.
  • Next 16.3's next dev writes apps/web/AGENTS.md and CLAUDE.md (its own agent rules) on startup, as it does for any next dev; this PR leaves that alone.

Generated by Claude Code

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..."), then runs `next dev` alone on
  127.0.0.1:3000, with a 1 GiB heap cap; the tab opens /. No WordPress
  site is connected (its URL is the product's WORDPRESS_URL secret), so the
  pages render the bundled sample content.
- 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); Next 16
  refuses the hot reload's WebSocket from an origin it is not told about.
  And, in `next dev` only (NODE_ENV=development), the same hosts as Server
  Actions origins, which Next refuses from an Origin that is not the Host.
  `next build` reads neither.
- baseline.yml: orun v2.88.0 -> v2.96.0, the first release that reads
  spec.preview, so the placement's `orun validate` checks it. ci.yml (the
  product's own lane pin) is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019PcpNV6SjymJBPv3nNkC4z
@ruehowl
ruehowl marked this pull request as ready for review November 4, 2026 20:54
@ruehowl
ruehowl merged commit 855b356 into main Nov 4, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants