승인 단계 삭제 복구 흐름 구현하고 API 정렬 문서 추가
This commit is contained in:
@@ -21,6 +21,7 @@ Commits follow the existing Superport convention: Korean imperative summaries wi
|
||||
|
||||
## Architecture & Environment Notes
|
||||
Initialize environments via `.env.development` / `.env.production` and load them through `Environment.initialize()` before bootstrapping DI. New data sources should expose repository interfaces in `domain/` and rely on the shared `ApiClient` instance. Do not use mock data in the application; always call the real backend (staging/production as appropriate). If an endpoint is not available, mark the feature as disabled behind a feature flag rather than mocking.
|
||||
- Frontend behaviour/data models must strictly follow the deployed backend contract. (프론트엔드는 백엔드 API 계약을 절대 우선으로 준수해야 하며, 누락된 기능은 백엔드 수정 요청 후 진행한다.)
|
||||
|
||||
---
|
||||
|
||||
@@ -34,6 +35,12 @@ Initialize environments via `.env.development` / `.env.production` and load them
|
||||
|
||||
---
|
||||
|
||||
## Notification Policy
|
||||
|
||||
- Every task completion must trigger a notification via the configured `notify.py` workflow so users are consistently alerted.
|
||||
|
||||
---
|
||||
|
||||
## SRP & Clean Architecture Enforcement
|
||||
|
||||
Apply these principles repo-wide. Use the checklist below during reviews.
|
||||
|
||||
Reference in New Issue
Block a user