feat: add admin users page (structurizr)

[parse]

No description provided.

[erode-app]

Architectural Drift Analysis

Component: frontend (Web Frontend)

Selected from 5 candidates

• frontend (Web Frontend)
• api_gateway (API Gateway)
• user_service (User Service)
• product_service (Product Service)
• database (Database)

Status: ⚠️ Issues detected

Detected Issues (1)

• [HIGH] The Web Frontend ('frontend') is calling the User Service directly, bypassing the API Gateway. According to the model, frontend is only allowed to depend on api_gateway, not user_service. This is a cross-boundary violation and breaks the intended system separation and control.
  • Source: packages/frontend/src/index.ts
  • Recommendation: Refactor the frontend code to send user-related requests through the API Gateway, not directly to the user_service. Only update the architecture model if this is a deliberate, model-driven change, and after architectural review.

How to Resolve:
Adjust the architecture model to:

• Include missing relationships between components
• Revise component boundaries if code has been relocated
• Record intentional architectural changes

Overview

This PR introduces architectural drift by allowing the frontend to bypass the API Gateway and call the user_service directly, which violates the current architectural constraints. No improvements to architecture alignment were found, and this dependency should be removed or revised to preserve proper boundary enforcement.

Analysis details

AI Provider	openai
Quick model (Stages 1, 2)	gpt-4.1-mini
Deep model (Stage 3)	gpt-4.1

---

Automated by erode