---
id: w2/m11/t006
title: "Render parity — verify create semantics + deploy-history behavior are consistent across REST/GraphQL/MCP/UI vs render.com"
worker: worker2
status: todo
estimate: 30m
depends_on: [w2/m11/t005]
---

## Objective

Check that the now-unified create path produces consistent field shapes/semantics across REST, GraphQL, MCP, and the dashboard, and compare against render.com's documented create + deploy-history behavior.

## Context

- `docs/ADR018-render-parity.md` — the parity ledger; the "List / get deploy objects" row is flagged stale (refresh needed per `w2/m10/t006`) — fold this milestone's evidence in too.

## Steps

1. Diff create-response shapes across REST/GraphQL/MCP after the routing change (t002) — confirm no accidental contract drift.
2. Confirm the dashboard's create wizard (`w5/m15`) and deploy list still behave correctly against the unified path.
3. Update `docs/ADR018-render-parity.md`'s relevant rows with fresh evidence.

## Files

- `docs/ADR018-render-parity.md`

## Acceptance criteria

- [ ] No unexplained drift across the four surfaces.
- [ ] Parity ledger updated with evidence.
