inventory

README.md

@@ -85,6 +85,7 @@ The current inventory foundation supports:
 - SKU, description, type, status, unit-of-measure, sellable/purchasable, default cost, and notes fields
 - BOM header and BOM line editing directly on the item form
 - searchable component lookup for BOM lines, designed for large item catalogs
+- SKU-first searchable component lookup for BOM lines, with SKU shown in the picker and description kept separate in the selected row
 - BOM detail display with component SKU, name, quantity, unit, notes, and position
 - protected warehouse list, detail, create, and edit flows
 - nested stock-location management inside each warehouse record
@@ -95,6 +96,16 @@ This module introduces `inventory.read` and `inventory.write` permissions. After
 
 Moving forward, any UI that requires searching for an item by SKU or item name should use a searchable picker/autocomplete rather than a static dropdown.
 
+## UI Density
+
+The active client screens have been normalized toward a denser workspace layout:
+
+- form controls and action bars use tighter padding
+- CRM, inventory, warehouse, settings, dashboard, and login screens use reduced card spacing
+- headings, metric cards, empty states, and long-text blocks were tightened for better data density
+
+This denser layout is now the baseline for future screens. New pages should avoid reverting to oversized card padding, tall action bars, or long static dropdowns for operational datasets.
+
 ## Branding
 
 Brand colors and typography are configured through the Company Settings page and the frontend theme token layer. Update runtime branding in-app, or adjust defaults in the theme config if you need a new baseline brand.
@@ -121,6 +132,7 @@ As of March 14, 2026, the latest committed domain migrations include:
 
 - Dark mode persistence is handled through the frontend theme provider and should remain stable across page navigation.
 - The shell layout is tuned for wider desktop use than the original foundation build, and now exposes CRM, inventory, settings, and planning modules from the same app shell.
+- The active module screens now follow a tighter density baseline for forms, tables, and detail cards.
 - The client build still emits a Vite chunk-size warning because the app has not been code-split yet.
 
 ## PDF Generation