# PR-05c Selected Asset Details Contract and Preview ## Briefing Implement the selected-asset details surface in the required fixed order: 1. `Summary` 2. `Runtime Contract` 3. `Inputs / Preview` 4. `Diagnostics` 5. `Actions` This PR materializes the didactic core of the `Assets` workspace. ## Objective Deliver the first usable selected-asset details experience, including: - summary identity/state rendering - runtime-facing contract rendering - inputs-by-role rendering - first previewable input surfaces - inline diagnostics - action groups with routine vs sensitive separation ## Dependencies - [`./PR-05a-assets-workspace-foundation-and-service-state.md`](./PR-05a-assets-workspace-foundation-and-service-state.md) - [`./PR-05b-asset-navigator-search-filters-and-selection.md`](./PR-05b-asset-navigator-search-filters-and-selection.md) ## Scope - render the fixed details skeleton - render summary metadata and location - render runtime contract fields such as `output.format`, `codec`, and `preload` - render input groups and input selection - implement first preview surfaces for previewable inputs - render inline diagnostics by severity - render action groups for: - `Doctor` - `Build` - `Adopt` - `Register` - sensitive operations placeholders where needed ## Non-Goals - no final staged preview/apply workflow yet - no final lower log integration yet - no exhaustive preview support for every asset family ## Execution Method 1. Build the selected-asset details layout in the mandated section order. 2. Render summary and runtime contract from workspace state. 3. Implement inputs-by-role rendering and input selection. 4. Implement baseline preview handling for previewable types. 5. Render inline diagnostics and action grouping. ## Acceptance Criteria - selecting an asset hydrates a full details view in the fixed section order - runtime-facing contract fields are visible without raw JSON inspection - previewable inputs can be inspected from the details area - diagnostics are visible inline and differentiated by severity - routine actions and sensitive actions are visibly separated ## Validation - unit tests for selected-asset detail mapping - unit tests for action availability by asset state - UI smoke validation for previewable input rendering ## Affected Artifacts - `AssetsWorkspace` details area - preview components - diagnostics rendering - action surface wiring - tests for selected-asset detail behavior