---
id: w8/m5/t005
title: Dashboard Compute section labels resource kind
worker: worker8
status: todo
estimate: 35m
depends_on: [w8/m5/t004]
---

## Objective

Update the dashboard's Usage page Compute section so Postgres/Key Value rows are visibly distinguished from App/web-service rows, using the resource-kind field added in t003.

## Context

- `dashboard/src/features/usage/components/usage-page.tsx`'s `ComputeSection` renders `serviceId`/`tier`/hours with no notion of resource kind — a `db-…`/`kv-…` id would otherwise look like a web service.
- Follows the dashboard's existing `space-y-6`/Card conventions (`dashboard/CLAUDE.md`).

## Steps

1. Extend `ComputeRow`/`extractRows` to carry the resource-kind field.
2. Add a kind label/column (or icon) to the Compute table so App/Database/KeyValue rows are visually distinct.
3. Update the `useUsage` hook's GraphQL query/types if the new field requires it.

## Files

- `dashboard/src/features/usage/components/usage-page.tsx`
- `dashboard/src/features/usage/hooks/use-usage.ts`

## Acceptance criteria

- [ ] A workspace with metered App + Database + KeyValue instances shows all three in the Compute section, each labeled with its kind.

## Out of scope

- Bandwidth/build sections (Database/KeyValue don't populate them per t001).
