# Commercial Admin Polish Report

**Date:** 2026-07-29

**Scope:** Admin Commercial Presentation
**Status:** COMPLETE

## Admin dashboard

- Every registry card resolves its title, description, icon, and accent color from the universal Presentation Dictionary.
- Live catalog entries and local API bindings are deduplicated by registry key.
- Tenant commercial resources are presented in a dedicated customer and activation section.
- Generic runtime display names and API descriptions are not used as card copy.

## List pages

Every Commercial admin list now uses business-facing columns:

- Name
- Status
- Version
- Last updated
- Visibility
- Actions

Status and visibility values are localized. Technical identifiers remain hidden and are used only for stable row identity and API targeting.

List UX includes search, status filtering, sorting, loading skeletons, empty states, pagination, selection, bulk actions, localized status chips, and read-only treatment for tenant projections.

## Forms and details

- Create and edit titles come from the resource presentation definition.
- Fields are grouped into basic information, commercial information, pricing, capabilities, visibility, publishing, and additional information.
- Technical fields, stable codes, raw payloads, routes, traces, and internal identifiers are excluded.
- Arrays render as human-readable chips.
- Nested objects render as structured field groups.
- English runtime names and descriptions are replaced by their business-facing presentation.
- Raw JSON is not rendered.

## Safety and scope

Only frontend presentation files and Commercial presentation documentation were changed. Backend services, APIs, database, schemas, contracts, ADRs, and Runtime adapters are unchanged.
