Feature Specification: Inventory UI

Feature Branch: feat/041-inventory-ui
Created: 2026-01-07
Status: Draft

Purpose

Provide a consistent admin UI for browsing Inventory, understanding sync status, and seeing capability/coverage information per policy type.

Tenant Admin (primary)
MSP Operator (if cross-tenant access exists; read-only unless explicitly allowed)

Given a tenant context
When the user opens Inventory
Then they can browse inventory items by type and see core fields (name, platform/type, last observed, status)

Given an inventory item exists
When the user opens the item details
Then they can see normalized metadata and the latest observed payload (or a safe subset if full payload is not available)

Given the system has a support matrix
When the user views the coverage table
Then they can see which types are supported for backup/restore/preview and any restrictions

FR1: Provide an Inventory landing view scoped to the current tenant.
FR2: Provide inventory list views grouped by policy type (or category) with pagination/search.
FR3: Provide an inventory item detail view showing:
- stable identifiers
- last observed timestamps
- source run reference
- capability/support status for the item’s type
FR4: Provide a Sync Runs list/detail view.
FR5: Provide a Coverage/Capabilities view derived from configuration/contract registry.
FR6: Enforce tenant isolation in all navigation and data access.

NFR1: Pages should remain usable for tenants with large inventories (no full-table loads).
NFR2: UI must not expose secrets or unsafe payload fields.
NFR3: Errors should be actionable (clear messages + stable error codes where available).

SC1: Admins can find an inventory item and view its details in under 60 seconds.
SC2: Admins can identify the latest completed sync run for a tenant in under 30 seconds.
SC3: Coverage view communicates support level clearly enough that admins make the correct decision without trial-and-error.