---
id: w6/m9/t006
title: "Render parity — verify t004/t005's user-facing validation-error shape and autoscaling mutation behavior vs render.com"
worker: worker6
status: done
estimate: 30m
depends_on: [w6/m9/t004, w6/m9/t005]
---

## Objective

Check that the CRD-validation error shape (t004) and the fixed autoscaling mutation (t005) are consistent across REST/GraphQL/MCP/UI and don't diverge from Render's documented behavior.

## Context

- `docs/ADR018-render-parity.md` — the parity ledger.

## Steps

1. Confirm a rejected `repo`/`branch`/`rootDir` value produces a consistent, reasonable error across bex-api's create/update paths (REST/GraphQL/MCP already had Go-level validators from `w6/m6`; this checks the CRD-level rejection path doesn't produce a worse error for hand-applied CRs, which is a different failure mode than bex-api's own validators).
2. Confirm the fixed `setAutoscaling`/`disableAutoscaling` GraphQL mutations match the REST/MCP autoscaling surface (`w1/m20`) in behavior now that the panic is fixed.
3. Note any drift as follow-up work.

## Files

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

## Acceptance criteria

- [ ] No unexplained drift between REST/GraphQL/MCP/UI for either surface.
