erp-mecanicas-diesel/orchestration/inventarios/BACKEND_INVENTORY.yml

# BACKEND INVENTORY - ERP Mecánicas Diesel (Vertical)
# Generado: 2025-12-08
# Actualizado: 2025-12-12
# Sistema: NEXUS + SIMCO v2.2.0

proyecto:
  nombre: ERP Mecanicas Diesel
  codigo: mecanicas-diesel
  nivel: 2B.2 (Vertical)
  estado: EN_DESARROLLO

herencia_core:
  backend: erp-core
  servicios_heredados: 40+
  referencia: "apps/erp-core/backend/"

# =============================================================================
# SERVICIOS IMPLEMENTADOS (Sprint 1.1)
# =============================================================================
servicios_implementados:
  auth:
    - nombre: AuthService
      modulo: AUTH
      estado: IMPLEMENTADO
      archivo: src/modules/auth/auth.service.ts
      endpoints:
        - POST /api/v1/auth/login
        - POST /api/v1/auth/register
        - POST /api/v1/auth/logout
        - POST /api/v1/auth/refresh
        - GET /api/v1/auth/profile
        - POST /api/v1/auth/change-password
      entidades:
        - User (src/modules/auth/entities/user.entity.ts)
        - RefreshToken (src/modules/auth/entities/refresh-token.entity.ts)
        - Workshop (src/modules/auth/entities/workshop.entity.ts)
      dependencias:
        - bcryptjs
        - jsonwebtoken
        - uuid

  users:
    - nombre: UsersService
      modulo: USERS
      estado: IMPLEMENTADO
      archivo: src/modules/users/users.service.ts
      endpoints:
        - GET /api/v1/users
        - GET /api/v1/users/:id
        - POST /api/v1/users
        - PATCH /api/v1/users/:id
        - DELETE /api/v1/users/:id
        - PATCH /api/v1/users/:id/reset-password
      permisos:
        - admin: todos los endpoints
        - jefe_taller: crear, listar, actualizar usuarios
        - otros: solo lectura (GET)

  service_management:
    - nombre: ServiceOrderService
      modulo: MD-001
      estado: IMPLEMENTADO
      archivo: src/modules/service-management/services/service-order.service.ts
      endpoints:
        - GET /api/v1/service-orders
        - POST /api/v1/service-orders
        - GET /api/v1/service-orders/:id
        - PATCH /api/v1/service-orders/:id
        - DELETE /api/v1/service-orders/:id

    - nombre: QuoteService
      modulo: MD-004
      estado: IMPLEMENTADO
      archivo: src/modules/service-management/services/quote.service.ts
      endpoints:
        - GET /api/v1/quotes
        - POST /api/v1/quotes
        - GET /api/v1/quotes/:id
        - PATCH /api/v1/quotes/:id

    - nombre: DiagnosticService
      modulo: MD-001
      estado: IMPLEMENTADO
      archivo: src/modules/service-management/services/diagnostic.service.ts
      endpoints:
        - GET /api/v1/diagnostics
        - POST /api/v1/diagnostics
        - GET /api/v1/diagnostics/:id

  vehicle_management:
    - nombre: VehicleService
      modulo: MD-002
      estado: IMPLEMENTADO
      archivo: src/modules/vehicle-management/services/vehicle.service.ts
      endpoints:
        - GET /api/v1/vehicles
        - POST /api/v1/vehicles
        - GET /api/v1/vehicles/:id
        - PATCH /api/v1/vehicles/:id

    - nombre: FleetService
      modulo: MD-002
      estado: IMPLEMENTADO
      archivo: src/modules/vehicle-management/services/fleet.service.ts
      endpoints:
        - GET /api/v1/fleets
        - POST /api/v1/fleets
        - GET /api/v1/fleets/:id
        - PATCH /api/v1/fleets/:id

  parts_management:
    - nombre: PartService
      modulo: MD-003
      estado: IMPLEMENTADO
      archivo: src/modules/parts-management/services/part.service.ts
      endpoints:
        - GET /api/v1/parts
        - POST /api/v1/parts
        - GET /api/v1/parts/:id
        - PATCH /api/v1/parts/:id

    - nombre: SupplierService
      modulo: MD-003
      estado: IMPLEMENTADO
      archivo: src/modules/parts-management/services/supplier.service.ts
      endpoints:
        - GET /api/v1/suppliers
        - POST /api/v1/suppliers
        - GET /api/v1/suppliers/:id
        - PATCH /api/v1/suppliers/:id

# =============================================================================
# SHARED/INFRAESTRUCTURA
# =============================================================================
shared:
  middleware:
    - nombre: authMiddleware
      archivo: src/shared/middleware/auth.middleware.ts
      descripcion: Verifica JWT y extrae usuario/tenant
      estado: IMPLEMENTADO

  utils:
    - nombre: jwt.utils
      archivo: src/shared/utils/jwt.utils.ts
      funciones:
        - generateAccessToken
        - generateRefreshToken
        - verifyToken
        - decodeToken
      estado: IMPLEMENTADO

  types:
    - nombre: types/index
      archivo: src/shared/types/index.ts
      tipos:
        - JwtPayload
        - AuthRequest
        - ApiResponse
      estado: IMPLEMENTADO

# =============================================================================
# ENTIDADES POR MODULO
# =============================================================================
entidades:
  auth:
    total: 3
    lista:
      - User (workshop_core.users)
      - RefreshToken (workshop_core.refresh_tokens)
      - Workshop (workshop_core.workshops)

  service_management:
    total: 6
    lista:
      - ServiceOrder (service_management.service_orders)
      - OrderItem (service_management.order_items)
      - Diagnostic (service_management.diagnostics)
      - Quote (service_management.quotes)
      - WorkBay (service_management.work_bays)
      - Service (service_management.services)

  vehicle_management:
    total: 5
    lista:
      - Vehicle (vehicle_management.vehicles)
      - Fleet (vehicle_management.fleets)
      - VehicleEngine (vehicle_management.vehicle_engines)
      - EngineCatalog (vehicle_management.engine_catalog)
      - MaintenanceReminder (vehicle_management.maintenance_reminders)

  parts_management:
    total: 4
    lista:
      - Part (parts_management.parts)
      - PartCategory (parts_management.part_categories)
      - Supplier (parts_management.suppliers)
      - WarehouseLocation (parts_management.warehouse_locations)

# =============================================================================
# MODULO CUSTOMERS (Agregado 2025-12-18)
# =============================================================================
customers:
  - nombre: CustomersService
    modulo: CUSTOMERS
    estado: IMPLEMENTADO
    archivo: src/modules/customers/services/customers.service.ts
    endpoints:
      - POST /api/v1/customers
      - GET /api/v1/customers
      - GET /api/v1/customers/search
      - GET /api/v1/customers/stats
      - GET /api/v1/customers/:id
      - GET /api/v1/customers/email/:email
      - GET /api/v1/customers/phone/:phone
      - PATCH /api/v1/customers/:id
      - DELETE /api/v1/customers/:id
      - POST /api/v1/customers/:id/activate
    entidades:
      - Customer (service_management.customers)

# =============================================================================
# RESUMEN
# =============================================================================
resumen:
  servicios_implementados: 11
  endpoints_implementados: 50
  entidades_implementadas: 19
  modulos_completos:
    - AUTH (Sprint 1.1)
    - USERS (Sprint 1.1)
    - CUSTOMERS (Sprint 1.2 - 2025-12-18)
  modulos_parciales:
    - MD-001 (Service Management - backend listo)
    - MD-002 (Vehicle Management - backend listo)
    - MD-003 (Parts Management - backend listo)
    - MD-004 (Quotes - backend listo)
  estado_general: EN_DESARROLLO
  typecheck: PASS
  ultima_actualizacion: 2025-12-18

# =============================================================================
# PROXIMOS PASOS
# =============================================================================
proximos_pasos:
  sprint_1_2:
    - Conectar frontend con nuevos endpoints de auth
    - Implementar guards de autenticacion en frontend
    - Crear paginas de login/register
    - Integrar manejo de tokens en frontend

referencias:
  herencia_core: "../00-guidelines/HERENCIA-ERP-CORE.md"
  plan_implementacion: "../01-planning/PLAN-IMPLEMENTACION-2025-12.md"