Order Model + Sub-entities

Unified Order shape that absorbs both the Medusa /store/orders response and the seller /vendor/orders response. Customer-facing fields (sellerName/Phone/Photo, startTime/endTime, shipping methods) sit alongside seller-facing fields (customer block, splitOrderPayment).

1. Order.fromJson reads the Medusa payload and conditionally populates customer + splitOrderPayment when those keys exist (seller response).
2. OrderItem nests variant info needed by OrderCard.
3. OrderAddress carries shipping + billing addresses.
4. SplitOrderPayment surfaces status / authorized / captured / refunded for seller-side UIs.
5. displayIdFormatted formats the human-readable id used in logs and the receipt.

• fromJson is intentionally lenient — parse errors on a single order are caught upstream (in OrderService) and that order is dropped from the list rather than aborting the whole load.
• Seller payload includes product_type='provision' on items which the UI can use to differentiate physical vs booking orders.
• Some customer-side fields (seller info, startTime/endTime) are derived from order metadata.slot — null is normal for non-booking orders.

• lib/src/features/shared/orders/models/order.dart:3 // Order
• lib/src/features/shared/orders/models/order.dart // OrderItem / OrderAddress / OrderCustomer / SplitOrderPayment

The CLAUDE.md inside this feature folder documents the seller-orders rollout plan — keep new fields in fromJson tolerant of both response shapes.