261007_01_ENH: 컨택 결과 갱신 api호출 시 log남기고 api 결과가 다 도착한 경우만 다음 페이지로 이동

This commit is contained in:
2026-10-07 11:31:30 +09:00
parent 4e180928e5
commit cadf55e7ee
13 changed files with 526 additions and 104 deletions

View File

@@ -35,6 +35,13 @@ Later and more specific instructions may override earlier general instructions o
- Lead with the result or decision, then provide only the detail needed to verify it.
- Do not create or retain a full session transcript.
### Attention-Aware Response Style
- Use `attention-aware-communication` for substantive answers, progress updates, and completion reports.
- Default to concise, bottom-line-first Korean without omitting a condition, risk, number, or uncertainty needed for a correct decision.
- Give full detail when the user requests depth. Use Spartan style only when explicitly requested.
- Presentation rules never reduce investigation, implementation, validation, or reporting obligations.
## Work Authorization
- The default workflow is discussion first and explicit execution approval second.
@@ -152,6 +159,13 @@ Preferred human-facing tools:
- If a possible secret is discovered, do not repeat it. Report only its location, type, and recommended containment action.
- Do not rotate, revoke, copy, or otherwise modify credentials unless that exact action is explicitly authorized.
## Workflow Skills
- Use `project-reference-loader` before substantive repository analysis, planning, implementation, debugging, or review. Read only the current project and shared references routed for that task, and reread them for each related task even if they were loaded earlier in the session.
- Use `karpathy-guidelines` when implementing, refactoring, or reviewing code. It keeps assumptions visible, changes surgical, and success criteria verifiable.
- Use `verification-before-completion` before claiming that work is complete, fixed, passing, ready, or safe to commit or publish.
- A skill does not expand task scope or authorize Git publication, database execution, deployment, destructive actions, or external communication.
## Validation
- Discover supported build, test, lint, type-check, and formatting commands from repository files and project instructions. Do not invent commands.
@@ -241,35 +255,21 @@ When implementation is complete, report in Korean:
- Separate intentional product or behavior changes from framework-only migration changes so each can be reviewed independently.
- For standalone React applications, the default planned target is Next.js with TypeScript unless the project profile explicitly declares another approved target.
## KON-KIWI Repository Rules
# KON-KIWI Project Instruction Router
### Repository Role and Twin-Project Relationship
## Required Project References
- This is a legacy Classic ASP application maintained alongside `KON`; the two repositories are near twins whose main differences are presentation and styling.
- Preserve current routes, includes, sessions, authentication, authorization, form fields, redirects, uploads, downloads, and MSSQL behavior while the application remains in service.
- Before changing shared-looking behavior, compare the corresponding KON implementation and determine whether the change belongs in both repositories or only this one.
- Do not copy a change across the pair blindly. Preserve intentional branding, layout, CSS, asset, configuration, customer, and deployment differences.
- Keep maintenance and small approved feature work narrowly scoped. Do not modernize unrelated business areas or shared include trees as a side effect.
Before each related task, read the current contents of every matching reference below, even if it was read earlier in the session.
### Encoding and File Safety
| Task scope | Required reference |
|---|---|
| Any substantive analysis, planning, implementation, debugging, review, or documentation work in this repository | `.agent/references/repository-rules.md` |
- Treat Classic ASP, include, script, and configuration files as potentially CP949/EUC-KR with CRLF. Verify each touched file's encoding, BOM state, line endings, response code page, and charset behavior before and after editing.
- Never run a repository-wide UTF-8 conversion, formatter, or line-ending normalization. Inspect byte-level diffs and Korean comments, messages, labels, and data after every approved text change.
- Treat existing connection settings and operational configuration as sensitive legacy material. Do not echo their values into chat, logs, fixtures, generated documentation, or completion reports, and do not alter them without explicit task scope.
If a task spans multiple scopes, read every matching reference. Do not assume remembered content is current.
### Runtime and Repository Data
## Harness Workflow
- `Project`, `log`, `ProjectUpload`, `uploadFile`, `WebProject`, `_ServerLog`, and `Files` retain only `.gitkeep`; do not add runtime contents from these directories to Git.
- `store` is intentionally versioned. Preserve its tracked contents and do not add it to ignore rules or remove it as cleanup without explicit approval.
- Do not modify uploaded files, generated projects, logs, or runtime artifacts during analysis or validation.
### Data and Migration Direction
- Trace include chains and shared DB helpers before changing SQL, authentication, authorization, sessions, uploads, or file handling.
- Parameterize new or changed values while preserving ADO parameter order, types, result shapes, transactions, null behavior, and ordering.
- The long-term direction is staged migration to a Spring Boot backend and Next.js/TypeScript frontend. For now, record relevant migration observations briefly and prioritize safe legacy maintenance.
### 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.
- Do not start IIS, connect to a real database, send external requests, or mutate production-like data during validation without separate approval.
- `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.