---
id: w5/m14/t005
title: "Render parity — dashboard danger-zone UX vs Render's service Settings delete flow"
worker: worker5
status: done
estimate: 20m
depends_on: [w5/m14/t003, w5/m14/t004]
---

## Objective

Check the shipped delete flow's consistency across REST/GraphQL/MCP (as built in w2/m4) and the dashboard danger zone (this milestone) against Render's own service Settings delete behavior; document any drift as follow-up rather than leaving it silent.

## Context

- Render's service Settings danger zone: delete requires typing the service name, is scoped to the service's own Settings page, and shows a clear irreversibility warning (render.com/docs).
- `docs/ADR018-render-parity.md`'s "Delete service" row should be updated from ✖ to ✅ (UI column) once this lands.

## Steps

1. Compare the type-to-confirm UX (copy, warning tone, button placement) against Render's captured/documented behavior.
2. Verify REST/GraphQL/MCP delete responses are consistent with each other (same error shape on not-found, same success shape).
3. Update `docs/ADR018-render-parity.md`'s Delete service row UI cell and evidence pointer — and the milestone-tracking owner row (currently "Delete service | w2/m4 | done 2026-07-09 (REST/GraphQL/MCP; dashboard UI → w5)"): replace the vague "dashboard UI → w5" with w5/m14 completion evidence when the UI cell flips to ✅.
4. File any divergence found as a follow-up inbox note rather than silently diverging.

## Files

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

## Acceptance criteria

- [ ] `docs/ADR018-render-parity.md` Delete service row UI cell flips to ✅ with an evidence pointer to this milestone.
- [ ] Any UX/response-shape drift from Render is documented, not silently accepted.

## Out of scope

- Building new surfaces to close a drift found here — that's follow-up work.
