261026_01_ENH: 공연 상세정보에 관리번호(NCAS), 변경 메모 추가

This commit is contained in:
2026-10-26 16:21:42 +09:00
parent 0708ddd936
commit 2667c40086
21 changed files with 534 additions and 86 deletions

View File

@@ -1,22 +1,18 @@
## GWCF Monitoring Frontend Repository Rules
# GWCF Monitoring Frontend Project Instruction Router
### Deliverable and User Workflows
## Required Project References
- This Next.js frontend supports GWCF performance records, monitoring assignments, schedules and visits, reviews, users, file preview, and related operational workflows.
- Its product character is similar to KriContact, but its requirements, API, permissions, terminology, and deliverables remain project-specific.
- Preserve selected performance context, assignment state, review state, visit information, filters, file-preview behavior, and user/role boundaries across navigation and mutations.
- Keep personal information, monitoring details, uploaded documents, and exported data out of logs, fixtures, screenshots, and external services.
Before each related task, read the current contents of every matching reference below, even if it was read earlier in the session.
### Frontend and Local Next.js Guidance
| Task scope | Required reference |
|---|---|
| Any substantive analysis, planning, implementation, debugging, review, or documentation work in this repository | `.agent/references/repository-rules.md` |
- Use the consumed KRI frontend common and UI registry contracts. Prefer an existing shadcn/ui or registry component before creating a new foundational component.
- Do not create new TypeScript type or interface names ending in `Dto` or `DTO`.
- This repository may use Next.js APIs and conventions newer than model training data. Read the relevant local guide under `node_modules/next/dist/docs/` before changing a Next.js API, routing convention, or file structure, and follow deprecation notices.
- Preserve accessibility, loading, empty, error, unauthorized, confirmation, success, and file-preview states.
- Coordinate request, response, authentication, file, and error changes with the backend without requiring an unsafe simultaneous deployment.
If a task spans multiple scopes, read every matching reference. Do not assume remembered content is current.
### Harness and Verification
## Harness Workflow
- The previous standalone `AGENTS.md` Next.js guidance has been preserved in this project source. `AGENTS.md` and `CLAUDE.md` are now harness-generated outputs.
- Edit `.agent/profile.yml` or `.agent/project.md`, then recompose instead of editing generated files.
- Use existing npm scripts and focused checks. Do not call production APIs, process customer documents, or submit real monitoring/review data during validation.
- `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.

View File

@@ -0,0 +1,22 @@
## GWCF Monitoring Frontend Repository Rules
### Deliverable and User Workflows
- This Next.js frontend supports GWCF performance records, monitoring assignments, schedules and visits, reviews, users, file preview, and related operational workflows.
- Its product character is similar to KriContact, but its requirements, API, permissions, terminology, and deliverables remain project-specific.
- Preserve selected performance context, assignment state, review state, visit information, filters, file-preview behavior, and user/role boundaries across navigation and mutations.
- Keep personal information, monitoring details, uploaded documents, and exported data out of logs, fixtures, screenshots, and external services.
### Frontend and Local Next.js Guidance
- Use the consumed KRI frontend common and UI registry contracts. Prefer an existing shadcn/ui or registry component before creating a new foundational component.
- Do not create new TypeScript type or interface names ending in `Dto` or `DTO`.
- This repository may use Next.js APIs and conventions newer than model training data. Read the relevant local guide under `node_modules/next/dist/docs/` before changing a Next.js API, routing convention, or file structure, and follow deprecation notices.
- Preserve accessibility, loading, empty, error, unauthorized, confirmation, success, and file-preview states.
- Coordinate request, response, authentication, file, and error changes with the backend without requiring an unsafe simultaneous deployment.
### Harness and Verification
- The previous standalone `AGENTS.md` Next.js guidance has been preserved in this project source. `AGENTS.md` and `CLAUDE.md` are now harness-generated outputs.
- Edit `.agent/profile.yml` or `.agent/project.md`, then recompose instead of editing generated files.
- Use existing npm scripts and focused checks. Do not call production APIs, process customer documents, or submit real monitoring/review data during validation.