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

## Objective

Check that the five new observability surfaces (processes, top-queries, sizes, table-scans, parameter-overrides) are consistent across REST, GraphQL, MCP, and the dashboard — same fields, semantics, and error shapes — and compare against render.com's documented behavior.

## Context

- `docs/ADR006-bex-api.md` — Render-compatibility conventions.
- `docs/ADR018-render-parity.md` — the parity ledger; update the "Postgres observability" row once this ships.

## Steps

1. Diff each endpoint's REST/GraphQL/MCP field names and semantics against each other and against Render's documented shape.
2. Flag any drift as follow-up work (new inbox note) rather than silently diverging.
3. Update `docs/ADR018-render-parity.md`'s "Postgres observability" row to `✅` (or `◐` with the divergence noted).

## Files

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

## Acceptance criteria

- [ ] All three API surfaces + dashboard agree on field shapes for the five endpoints.
- [ ] Parity ledger updated with evidence.

## Out of scope

- Fixing unrelated parity rows.
