261012_01_ENH: ai 하네스 수정 및 배정 캘린더·모니터링 계정 표시 개선

- AI 하네스 참조 문서·스킬 추가 및 AGENTS.md, .agent/project.md 갱신
- 사업정보: 수정 권한(내부·재단) 계정에 배정 캘린더 버튼 추가
- 사업정보: 모니터링 계정은 본인 배정 슬롯만 표시, 툴팁에 모니터링/컨설팅 구분 표시
- 공연 상세: 모니터링 계정에는 관계자 정보 숨김
- 신청자 수·평가위원 조회 hook에 enabled 옵션 추가
This commit is contained in:
2026-10-12 15:52:44 +09:00
parent 9007f09f7b
commit cfcc474f6e
20 changed files with 541 additions and 111 deletions

View File

@@ -1,9 +1,18 @@
## Generated Next.js Repository Rules
# k-musical-manage-front Project Instruction Router
- This frontend application was generated by `@kri/create-next-app`.
- Keep the generated Next.js routing, server/client boundary, authentication, environment, state, query, and application-shell conventions unless an approved task changes them.
- Prefer shadcn and approved KRI UI Registry components over new local primitives when a suitable component exists.
- Do not create new TypeScript type or interface names ending in `Dto` or `DTO`.
- Consume shared frontend behavior from `@kri/common` and the KRI UI Registry instead of copying provider implementations into this repository.
- `AGENTS.md` and `CLAUDE.md` are central-harness generated outputs. Never edit them directly; update `.agent/profile.yml` or `.agent/project.md` and recompose.
- Run `npm run typecheck` and `npm run build` after relevant source or configuration changes.
## Required Project References
Before each related task, read the current contents of every matching reference below, even if it was read earlier in the session.
| Task scope | Required reference |
|---|---|
| Any substantive analysis, planning, implementation, debugging, review, or documentation work in this repository | `.agent/references/repository-rules.md` |
If a task spans multiple scopes, read every matching reference. Do not assume remembered content is current.
## Harness Workflow
- `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.