---
id: w1/m20/t005
title: Render parity — verify …/autoscaling across REST/GraphQL/MCP/UI
worker: worker1
status: done
estimate: 30m
depends_on: [w1/m20/t002, w1/m20/t003, w1/m20/t004]
---

## Objective

Confirm the autoscaling change is consistent across every surface it exposes — REST, GraphQL, MCP, and the dashboard — and matches render.com's behavior/API. Flag any drift as follow-up rather than silently diverging.

## Context

- bex-api is meant to be Render-compatible (`docs/ADR006-bex-api.md`); Render's autoscaling: `PUT/DELETE /v1/services/{id}/autoscaling`, min/max instances + target CPU%/mem%.
- Update `docs/ADR018-render-parity.md` — the autoscaling row moves from gap → ✅ with evidence.

## Steps

1. Diff bex fields/semantics/error shapes vs Render for each surface; note any deltas.
2. Update the `docs/ADR018-render-parity.md` row(s) with evidence per surface.
3. File follow-ups for any intentional divergence.

## Files

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

## Acceptance criteria

- [ ] REST/GraphQL/MCP/UI verified against Render; parity ledger updated with evidence.
- [ ] Any divergence captured as an inbox note, not left implicit.

## Out of scope

- New feature work beyond reconciling drift.
