---
id: w5/m16/t006
title: Render parity check
worker: worker5
status: done
estimate: 20m
depends_on: [w5/m16/t005]
---

## Objective

Compare the shipped dashboard stepper against the t001 live capture and the REST/GraphQL/MCP surfaces (`w2/m12`); flag any drift as follow-up work rather than silently diverging.

## Context

- Per `.claude/commands/pm.md`'s standing closing task: consistency check across REST, GraphQL, MCP, and dashboard UI, compared against the equivalent render.com behavior.

## Steps

1. Re-open the t001 capture side by side with the shipped dashboard stepper; note any visual/interaction drift.
2. Confirm the dashboard mutation's field names/behavior match the REST/MCP surfaces' semantics (bounds, error shape).
3. File any drift found as a follow-up inbox note rather than fixing it silently in this milestone.

## Files

- N/A (verification task)

## Acceptance criteria

- [ ] Drift (if any) is documented and filed as a follow-up, not silently absorbed.
