CI / test (push) Canceled after 0s
## Summary epic r04 - begin refactor ## Change Type - [x] Cowork feature - [ ] Bug fix - [ ] Core AI contribution - [ ] Test / hardening - [ ] Performance - [ ] Documentation ## Related Work Cowork Task: Core Repo: http://34.143.229.138/gitea-admin/fsg-ai-core-assets Core AI Issue: Core Task: Related PR: ## Scope What is intentionally included? What is intentionally NOT included? ## Validation - [ ] Unit tests - [ ] Integration tests - [ ] Manual verification - [ ] Regression check Commands / evidence: ## Security Impact Permission / credential / network / customer data impact: ## Compatibility - [ ] No breaking change - [ ] Breaking change documented ## Reviewer Notes Anything Cowork reviewers should pay attention to. --------- Co-authored-by: Anh Tran Nguyen Minh <anhtnm1@fpt.com> Co-authored-by: Huong Le Thi Thien <huongltt35@fpt.com> Co-authored-by: Nam Pham Dinh Thanh <nampdt@fpt.com> Co-authored-by: Vu Dam Tuan <vudt15@fpt.com> Co-authored-by: Hiep Ha Van <hiephv3@fpt.com> Co-authored-by: Lam Hoang Van <lamhv7@fpt.com> Reviewed-on: #7 Co-authored-by: Duy Le Huu <duylh19@fpt.com>
20 lines
1.0 KiB
Python
20 lines
1.0 KiB
Python
"""Read-only query services for monitoring/dashboard screens (EPIC R08).
|
|
|
|
⚠️ Ownership note (R08-T13): per ``docs/refactor/Feature_Architecture_
|
|
Proposal.md``'s file-split diagram, ``dashboard_query_service.py`` lives
|
|
under ``application/monitoring/`` alongside the Dashboard split — but the
|
|
SAME document's "Ranh giới phân hệ" table assigns ``application/monitoring/``
|
|
to Team Nam (R08-T07→T10, Monitoring's own 8-tab split). This directory did
|
|
not exist yet when Team Hoa reached R08-T13, so creating it here does not
|
|
collide with any file Team Nam has written — same situation R06-T02 flagged
|
|
for ``infrastructure/persistence/json/atomic_write.py`` vs. Team Nam's
|
|
planned ``atomic_json_file.py``. Team Nam should confirm when they start
|
|
R08-T07→T10 whether ``DashboardQueryService`` belongs here permanently or
|
|
should move once Monitoring's own query service exists.
|
|
"""
|
|
|
|
from .dashboard_query_service import DashboardQueryService
|
|
from .monitoring_query_service import MonitoringQueryService
|
|
|
|
__all__ = ["DashboardQueryService", "MonitoringQueryService"]
|