Please incorporate the following "Addendum v1" into the project context, sitting alongside the latest "Laravel E-Ordering System - 项目需求大纲 - EN.txt" and "project_for_ai.txt". Use these rules for all future code generation and analysis:

1. Identity & Relationship Refactoring:

a. Refactor the User-Customer relationship from 1:1 to Many-to-One. Multiple users can now be linked to a single customer_details record.

b. Permission Gate: Only CS Staff or higher can create these logins and assign them to a specific HQ or Branch via the "My Customer" management module.

c. Schema Update: The customer_details table must now support company_code (for Main/HQ) and branch_code (for Branches). These fields are mutually exclusive in the frontend based on the user's role.

2. Enhanced Order Security:

a. Cancellation Protocol: Once an order status is Approved, a CS Staff cannot cancel it directly. They must submit a "Cancellation Request" with a mandatory reason.

b. Approval Authority: Only a CS Leader or Admin has the authority to approve this request and move the status to Cancelled.

3. UOM (Unit of Measure) System:

a. Implement a UOM entity linked to Products. Fields: uom_name, rate_qty, and price.

b. Privacy Rule: staff_price must be strictly filtered out of all API responses or Blade views accessible by Customer or Branch roles.

c. Deletion Rule: Prevent "Hard Delete" of a UOM if it is referenced in any existing order_items. Otherwise, allow "Hide" (Soft Delete).

4. Staff Dashboard UI:

a. Create a "Unified Order Dashboard" for Staff.

b. Stats Container: At the top of the dashboard, include a summary container showing real-time counts for: All, Pending, Approved, In Transit, Delivered, and Cancelled.

Constraint: Before suggesting any code, check if the current project_for_ai(v95).txt migration files support these "Many-to-One" relationships. If not, suggest the Migration changes first.