---
id: w2/m8/t007
title: Render parity — cross-surface consistency + declare the repo surface a bex superset
worker: worker2
status: done
estimate: 30m
depends_on: [w2/m8/t006]
---

## Objective

Standing closing task. Check the milestone's change is consistent across REST, GraphQL, MCP (`lego/backend/`) and the dashboard UI — same fields, semantics, error shapes — and compare against Render's GitHub-integration behavior, flagging drift as follow-up rather than silently diverging.

## Context

- Render's comparable: GitHub App install → repo grant → repo list in the dashboard only (`render.com/docs/github`); no public REST/MCP repo surface, no public GraphQL capture.
- bex's REST `GET /v1/repos` + MCP repo tools are therefore **supersets** — record them in [docs/ADR018-render-parity.md](../../../docs/ADR018-render-parity.md) § "bex ahead of Render", and update the "Git connections (GitHub / GitLab app)" row cells + evidence.

## Steps

1. Field-by-field sweep across the four surfaces; fix or file drift.
2. Update `docs/ADR018-render-parity.md` (row + superset section + gap backlog).
3. `npx prettier@3.4.2 --write "**/*.md"`.

## Files

- `docs/ADR018-render-parity.md`; any adapter files needing alignment

## Acceptance criteria

- [ ] Four surfaces agree (or drift is filed as follow-up work)
- [ ] Parity ledger row updated with evidence pointers

## Out of scope

- New features
