202 Commits

Author	SHA1	Message	Date
Samir Boulahtit	c614b7d74c	feat: extract billing module with routes (Phase 3) ... Create app/modules/billing/ directory structure with: - definition.py: Module definition with features and menu items - routes/admin.py: Admin billing routes with module access control - routes/vendor.py: Vendor billing routes with module access control Key changes: - Billing module uses require_module_access("billing") dependency - Admin router now includes billing module router instead of legacy - Module registry imports billing_module from extracted location - Routes have identical functionality but are now module-gated Module structure pattern for future extractions: app/modules/{module}/ ├── __init__.py ├── definition.py (ModuleDefinition + router getters) └── routes/ ├── __init__.py ├── admin.py (require_module_access dependency) └── vendor.py (require_module_access dependency) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	2026-01-25 21:54:42 +01:00
Samir Boulahtit	5be42c5907	feat: implement modular platform architecture (Phase 1) ... Add module system for enabling/disabling feature bundles per platform. Module System: - ModuleDefinition dataclass for defining modules - 12 modules: core, platform-admin, billing, inventory, orders, marketplace, customers, cms, analytics, messaging, dev-tools, monitoring - Core modules (core, platform-admin) cannot be disabled - Module dependencies (e.g., marketplace requires inventory) MenuService Integration: - Menu items filtered by module enablement - MenuItemConfig includes is_module_enabled and module_code fields - Module-disabled items hidden from sidebar Platform Configuration: - BasePlatformConfig.enabled_modules property - OMS: all modules enabled (full commerce) - Loyalty: focused subset (no billing/inventory/orders/marketplace) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	2026-01-25 21:42:44 +01:00