---
id: w8/m6/t006
title: "Render parity: historical usage view"
worker: worker8
status: todo
estimate: 30m
depends_on: [w8/m6/t005]
---

## Objective

Compare this milestone's month-picker/trend view against Render's historical/previous-period billing view and flag any drift as documented follow-up, per the standing Render-parity closing task.

## Context

- `docs/ADR018-render-parity.md` § Usage metering is the place to record the outcome.
- REST and MCP already had `period` support before this milestone — the parity gap this milestone closes is GraphQL + dashboard UI specifically.

## Steps

1. Compare the dashboard's month-picker/trend UX (t001's design) against Render's historical billing view.
2. Update `docs/ADR018-render-parity.md`'s usage-metering entry to note GraphQL now has `period` parity with REST/MCP, and record the UI comparison outcome.
3. File any drift as a follow-up note, not silently.

## Files

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

## Acceptance criteria

- [ ] `docs/ADR018-render-parity.md` reflects the comparison with an explicit verdict (parity or documented drift).

## Out of scope

- Building any drift-closing feature itself (goes to a follow-up note/task).
