feat(reporting): compose role dashboards from feature services

This commit is contained in:
sechmachine
2026-08-15 01:30:18 +07:00
parent 3f2f789905
commit b1c6b170d0
9 changed files with 540 additions and 2 deletions
@@ -4,7 +4,7 @@
- **Requirement IDs:** `AUTH-003`, `UI-003`, `UI-013`, `I1-UI-03`
- **Scenario IDs:** `AC-AUTH-002`, `AC-UI-005`
- **Test class/method:** `com.lab.labtimesheet.feature.reporting.ReportingArchitectureTest`, `com.lab.labtimesheet.feature.reporting.controller.DashboardTemplateWebTest`
- **Implementation commit:** `5638286`, `pending`
- **Implementation commit:** `5638286`, `f8db8a3`
## Protected behavior
@@ -101,4 +101,4 @@ Total time: 24.823 s
## External-test boundaries
These tests prove package and template contracts with controlled view DTOs. They deliberately do not claim that `/dashboard` is connected to real account, Project, Task, attendance, or notification data; that integration remains gated on the platform's cross-feature service APIs and will require a PostgreSQL/Testcontainers test after the pinned platform structure is merged. Browser viewport, contrast, and pre-paint behavior remain integrated UI gates.
These tests prove package and template contracts with controlled view DTOs. The separate role-dashboard routing evidence covers the now-complete cross-feature service composition and PostgreSQL-backed Admin route. Browser viewport, contrast, and pre-paint behavior remain integrated UI gates.