261006_01_ENH: 전화를 걸지 않았는데 거는 중으로 남는 CTI 상태 오류 수정 및 AI Agent용 하네스 변경 적용

This commit is contained in:
2026-10-06 13:56:56 +09:00
parent b86ab58767
commit 746f709e92
18 changed files with 508 additions and 93 deletions

View File

@@ -1,28 +1,18 @@
## KriContact Front Repository Rules
# KriContact Front Project Instruction Router
### Product Purpose and Current Phase
## Required Project References
- This is the launched Next.js frontend for KRI contact operations. Preserve first-release behavior while planning and delivering approved follow-up features.
- The primary workflows include project and contact-list management, interviewer and list assignment, call/contact and event history, survey/contact/interview/message progress, SMS and email templates, result codes, users, companies, and roles.
- Prefer product-purpose clarity, workflow consistency, and backward compatibility over broad technical cleanup.
Before each related task, read the current contents of every matching reference below, even if it was read earlier in the session.
### Domain and Integration Boundaries
| Task scope | Required reference |
|---|---|
| Any substantive analysis, planning, implementation, debugging, review, or documentation work in this repository | `.agent/references/repository-rules.md` |
- Preserve the selected project context and company, project, role, and user access boundaries across navigation, queries, dialogs, and mutations.
- Treat list headers/items, assignment state, contact history, call state, progress metrics, result codes, templates, uploaded files, and exported files as coordinated API contracts with contact-server.
- Keep server-only credentials and privileged integration logic out of client bundles. Preserve the established Next.js API proxy and server/client boundaries.
- Minimize exposure of names, telephone numbers, contact history, and uploaded list data in UI state, logs, errors, screenshots, and test fixtures.
- Do not send real SMS or email, initiate real calls, or invoke production integrations during development or validation.
If a task spans multiple scopes, read every matching reference. Do not assume remembered content is current.
### Frontend Implementation
## Harness Workflow
- Use the consumed KRI frontend common and UI registry contracts instead of copying shared utilities, components, or conventions locally.
- Prefer an existing shadcn/ui or approved registry component before creating a new foundational UI component. Compose or extend it locally only for project-specific behavior.
- Do not create new TypeScript type or interface names ending in `Dto` or `DTO`; use domain- or purpose-specific names.
- Preserve accessibility and loading, empty, error, disabled, confirmation, and success states for operational workflows.
- Coordinate request, response, validation, authentication, and error-shape changes with contact-server without requiring an unsafe simultaneous deployment.
### Harness and Verification
- `AGENTS.md` and `CLAUDE.md` are generated. Edit `.agent/profile.yml` or `.agent/project.md`, then recompose instead of editing generated files.
- Use the repository's existing package manager and focused lint, type-check, test, or build commands. Validation must not call real business integrations.
- `AGENTS.md` and `CLAUDE.md` are generated outputs. Never edit them directly.
- Edit `.agent/project.md` only when routing changes. Store durable project detail in `.agent/references/`.
- A reference-only content change does not require recomposition when its route is unchanged. Run harness verification to validate routing and UTF-8.
- Recompose and verify after changing `.agent/project.md`, `.agent/profile.yml`, or another composed instruction source.