---
id: w6/m5/t006
title: "Render parity: workspace lifecycle UX vs Render, final check"
worker: worker6
status: done
estimate: 20m
depends_on: [w6/m5/t005]
---

## Objective

Final consistency check that bex's workspace lifecycle UX and its REST/GraphQL/MCP surfaces remain aligned with Render's semantics after t001-t005's fixes, and that any remaining drift is documented rather than silent.

## Context

- `w6/m2` already covers REST/GraphQL/MCP owners-API parity; this check is scoped to confirming the dashboard UX changes from t002 didn't introduce new drift on those surfaces.
- Render's REST owners surface stays read-only (RESEARCH-workspaces.md finding 9) — no mutation parity concern.
- _2026-07-11: the "(if any)" hedge is resolved — `docs/ADR018-render-parity.md` has NO workspaces/owners-lifecycle row at all; its "Identity, workspaces & account" section covers API keys, login, recovery, MFA, members, audit logs, SSO, SSH keys only. w6/m1–m3 shipped a whole parity surface (owners read API, lifecycle mutations, dashboard switcher/settings/delete) the evidence ledger does not record, so adding the row IS warranted within this task's existing scope._

## Steps

1. Spot-check that t002's UI fixes didn't require any REST/GraphQL/MCP field changes (they shouldn't — this milestone is UI/verification only).
2. Add the missing Workspaces/owners row to `docs/ADR018-render-parity.md`: REST read-only owners API ✅ (w6/m2; mutation absence is deliberate parity per RESEARCH-workspaces.md finding 9), GraphQL/MCP lifecycle verbs ✅ (w6/m1–m2), UI ✅ (w6/m3) — with the DNS-label-name deliberate-drift note.

## Files

- `docs/ADR018-render-parity.md` (add the Workspaces/owners row; other edits only if warranted)

## Acceptance criteria

- [ ] No new REST/GraphQL/MCP drift introduced by this milestone
- [ ] `docs/ADR018-render-parity.md` carries the Workspaces/owners row with per-surface evidence and the deliberate-drift note

## Out of scope

- New parity work beyond confirming this milestone's own changes.
