---
id: w3/m10/t006
title: "Render parity — verify the new metrics fields/semantics are consistent across REST/GraphQL/MCP/UI vs render.com"
worker: worker3
status: todo
estimate: 30m
depends_on: [w3/m10/t005]
---

## Objective

Check that the four new metrics series are consistent across REST, GraphQL, MCP, and the dashboard, and compare against render.com's documented/live extended-metrics behavior.

## Context

- `docs/ADR018-render-parity.md` — the parity ledger; update the "Extended metrics" 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.
3. Update `docs/ADR018-render-parity.md`'s row to `✅` (or `◐` noting the replication-lag gate on `w1/m22`).

## Files

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

## Acceptance criteria

- [ ] All surfaces agree on field shapes.
- [ ] Parity ledger updated with evidence, including the explicit replication-lag caveat.
