---
id: w5/m15/t005
title: Live walkthrough vs Render's /web/new; capture reference in docs/render-artifacts/
worker: worker5
status: todo
estimate: 30m
depends_on: [w5/m15/t004]
---

## Objective

Prove the DoD live and pin the parity reference: walk all three source paths on a real cluster (GitHub repo pick → Running; public URL → Running; image → Running), and capture Render's `/web/new` flow (docs screenshots or a logged-in capture if available) into `docs/render-artifacts/` so future parity checks have a fixed reference like `key-value.md` does.

## Context

- Cluster: mock cluster (`scripts/mock-cluster.sh` + build-from-git quirks in memory) or prod.
- GitHub path needs w2/m8 live (and w2/m9 for a private repo — use private if m9 shipped, public-repo-via-connection otherwise; note which).
- Playwright screenshots: bare filenames → `.playwright-mcp/`; curated captures move to `docs/render-artifacts/`.

## Steps

1. Three live create runs; evidence (screenshots, service URLs, timings) recorded in the milestone README.
2. Write `docs/render-artifacts/new-service-wizard.md` with the Render reference + bex's deliberate omissions (region/runtime/commands).
3. `npx prettier@3.4.2 --write "**/*.md"`.

## Files

- `docs/render-artifacts/new-service-wizard.md` (new)
- `.pm/w5/m15/README.md` (evidence)

## Acceptance criteria

- [ ] All three sources reach Running from the dashboard alone; evidence recorded
- [ ] Render reference captured for t006

## Out of scope

- Fixing backend issues found (file them)
