---
id: w2/m4/t005
title: Render parity — cross-surface consistency + render.com comparison for create/delete
worker: worker2
status: done
estimate: 20m
depends_on: [w2/m4/t004]
---

## Objective

Standing closing task. Check the milestone's changes are consistent across every surface they touch: REST, GraphQL, and MCP return the same fields/semantics/error shapes for create and delete (one verb pair, three thin adapters), and compare against Render's actual behavior (OpenAPI spec; dashboard captures in `docs/render-artifacts/` where relevant). Flag any drift as follow-up work (inbox note) rather than silently diverging. Dashboard UI is out of scope here — service create/delete UI is w5's lane; note that in the findings.

## Acceptance criteria

- [ ] Same service object/error shapes across the three adapters for create and delete; divergences from Render documented or filed as follow-ups.
