---
id: w5/m12/t006
title: Render parity — UI vs captured Render pages; ledger UI cell
worker: worker5
status: done
estimate: 30m
depends_on: [w5/m12/t004, w5/m12/t005]
---

## Objective

Side-by-side the shipped pages against the t001 captures (create flow, list, detail/connect) and against what the API actually serves — the UI must render w2/m7's fields verbatim, no client-side inventions. Flip the ledger Key Value row's UI cell ✖→✅ with evidence; omissions (maxmemoryPolicy, metrics tab, ipAllowList) stay listed in the row as conscious gaps.

## Context

- docs/ADR018-render-parity.md § Key Value row — after w2/m7's t007 the REST/GraphQL/MCP cells are ✅; this completes the row.
- Live verification order per m8 precedent: stub first, then prod once w2/m7 deploys.

## Steps

1. Walk create → list → detail on bex and on the captures; diff structure/wording/behavior.
2. Verify UI fields = GraphQL fields (no derived fabrications).
3. Update the ledger row + evidence; file drift as follow-ups.

## Files

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

## Acceptance criteria

- [ ] UI cell flipped with evidence; every divergence filed or listed in-row.

## Out of scope

- Fixing API-side drift (belongs to w2/m7 follow-ups).
