---
id: w3/m9/t006
title: "Render parity — verify REST/GraphQL/MCP/UI field/shape consistency vs render.com"
worker: worker3
status: todo
estimate: 30m
depends_on: [w3/m9/t003, w3/m9/t005]
---

## Objective

Check that the notification-settings surface is consistent across REST, GraphQL, MCP, and the dashboard, and compare against render.com's documented/live behavior.

## Context

- `docs/ADR018-render-parity.md` — the parity ledger; update the "Notifications (deploy/failure alerts)" row once this ships.

## Steps

1. Diff field names/semantics across the three API surfaces and the dashboard.
2. Flag any drift as follow-up work rather than silently diverging.
3. Update `docs/ADR018-render-parity.md`'s row to `✅` (or `◐` with divergence noted).

## Files

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

## Acceptance criteria

- [ ] All surfaces agree on field shapes.
- [ ] Parity ledger updated with evidence.
