CLAUDE.md: add end-to-end custom workflow spec (9-stage plating lifecycle)

Documents the full Quote→PO→SO→Recipe+WO→Invoice→Ship→Email workflow
for next sessions. Includes status table, architectural decisions needed,
and component mapping to Odoo models.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

fusion-plating/CLAUDE.md

@@ -148,6 +148,69 @@ Project: `nexasystems` (id: `ikvdlqkbqsitabxidvnq`)
 - `fusionapps.vm_registry` — VM inventory
 - `fusionapps.proxmox_nodes` — cluster node specs
 
+## Custom Workflow (TO BUILD — Next Sessions)
+
+End-to-end plating job lifecycle. This is the core business process.
+
+```
+1. Quotation via Configurator
+   └─ sale.order (draft) — configurator picks process type → suggests recipe
+
+2. Quotation Sent
+   └─ sale.order (sent)
+
+3. PO Received from Customer
+   └─ sale.order (confirmed by customer PO)
+
+4. Sale Order Created → triggers MO
+   └─ sale.order confirmed → mrp.production created
+   └─ **Recipe assigned to MO** (x_fc_recipe_id on mrp.production)
+
+5. Two paths:
+   a. Invoice Directly (simple jobs)
+      └─ account.move created from SO
+   b. Work Order Created for Factory + Shipping Label
+      └─ mrp.workorder records generated from recipe template
+      └─ **Per-job opt-in/out overrides configured here**
+      └─ Shipping label created (Fusion Shipping module)
+
+6. Work Order Completed
+   └─ mrp.production → done
+
+7. Invoice Created
+   └─ account.move — but check for account hold (non-payment flag)
+   └─ If hold → block invoice until resolved
+
+8. Product Shipped
+   └─ stock.picking confirmed
+   └─ Fusion Shipping module handles carrier integration
+
+9. Email to Client
+   └─ Automated email with:
+      - PDF Certificate of Conformance
+      - Invoice PDF
+      - Shipping tracking information
+```
+
+### What Exists vs What Needs Building
+
+| Component | Status |
+|-----------|--------|
+| Sale Order / Quotation | Standard Odoo (exists) |
+| Product Configurator | Needs building or extending |
+| Recipe assignment to MO | **Not built** — need `x_fc_recipe_id` on `mrp.production` |
+| Per-job opt-in/out overrides | **Not built** — need `fusion.plating.job.node.override` model + wizard |
+| WO generation from recipe | **Not built** — need to convert recipe nodes → mrp.workorder records |
+| Account hold check | Needs investigation (may exist in fusion_plating or accounting) |
+| Fusion Shipping integration | Module exists (`fusion_plating_logistics`) — check capabilities |
+| Auto-email with Cert+Invoice+Tracking | Needs building (automated action or cron) |
+
+### Key Architectural Decisions Needed
+1. Does the configurator extend Odoo's standard product configurator or is it custom?
+2. How do recipe nodes map to mrp.workorder? One node = one WO? Or only operation-level nodes?
+3. How does account hold work? Flag on res.partner? On sale.order?
+4. What triggers the final email — shipping confirmation? Invoice validation?
+
 ## Repackaged Enterprise Modules
 See `K:\Github\RePackaged-Odoo\CLAUDE.md` for full details. Key points:
 - Odoo 19 enterprise modules repackaged for community edition