inventory1

README.md

@@ -9,6 +9,7 @@ Current foundation scope includes:
 - CRM customers and vendors with create/edit/detail workflows
 - CRM search, filtering, status tagging, and reseller hierarchy
 - CRM contact history, account contacts, and shared attachments
+- inventory item master and BOM foundation
 - file storage and PDF rendering
 
 ## Workspace
@@ -54,7 +55,7 @@ docker build --build-arg NODE_VERSION=22 -t mrp-codex .
 
 The container startup script runs `npx prisma migrate deploy` automatically before launching the server.
 
-This Docker path is currently the most reliable way to ensure the database schema matches the latest CRM migrations on Windows.
+This Docker path is currently the most reliable way to ensure the database schema matches the latest CRM and inventory migrations on Windows.
 
 ## Persistence And Backup
 
@@ -76,6 +77,18 @@ The current CRM foundation supports:
 
 Recent CRM features depend on the committed Prisma migrations being applied. If you update the code and do not run migrations, the UI may render fields that are not yet present in the database.
 
+## Inventory
+
+The current inventory foundation supports:
+
+- protected item master list, detail, create, and edit flows
+- 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
+- BOM detail display with component SKU, name, quantity, unit, notes, and position
+- seeded sample inventory items and a starter assembly BOM during bootstrap
+
+This module introduces `inventory.read` and `inventory.write` permissions. After updating the code, restart the server against the migrated database so bootstrap can upsert the new permissions onto the default administrator role.
+
 ## 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.
@@ -88,17 +101,20 @@ Logo uploads are stored through the authenticated file pipeline and are rendered
 - Apply committed migrations in production: `npm run prisma:deploy`
 - If Prisma migration commands fail on a local Node 24 Windows environment, use Node 22 or Docker for migration execution. The committed migration files in `server/prisma/migrations` remain the source of truth.
 
-As of March 14, 2026, the latest committed CRM migrations include:
+As of March 14, 2026, the latest committed domain migrations include:
 
 - CRM status and list filters
 - CRM contact-history timeline
 - reseller hierarchy and reseller discount support
 - CRM commercial terms and account contacts
+- CRM lifecycle stages and operational metadata
+- inventory item master and BOM foundation
 
 ## UI Notes
 
 - 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, but the client build still emits a Vite chunk-size warning because the app has not been code-split yet.
+- 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 client build still emits a Vite chunk-size warning because the app has not been code-split yet.
 
 ## PDF Generation