코워크 문서 생성 게이트와 코드 후속 검증 게이트를 claw-code 기준으로 경량화

- balanced/tool_call_strict 프로필의 document_plan 재시도와 공격적 문서 fallback 개입을 줄여 Cowork 루프를 더 얇게 정리함

- document_plan 성공 직후 강제 user follow-up 주입을 제거하고 terminal 문서 도구 성공 시 Cowork에서 바로 종료할 수 있게 조정함

- CodeDiffGate, RecentExecutionGate, ExecutionSuccessGate를 review 작업 중심으로 제한해 일반 코드 수정의 과검증을 완화함

- TaskTypePolicy, SystemPromptBuilder, cowork preset을 함께 맞춰 문서 생성/분석형 요청의 종료 조건을 일관되게 정리함

- README.md 및 docs/DEVELOPMENT.md를 2026-04-12 23:05 (KST) 기준으로 갱신함

- 검증: dotnet build src/AxCopilot/AxCopilot.csproj -c Release -v minimal -p:OutputPath=bin\\verify\\ -p:IntermediateOutputPath=obj\\verify\\ (경고 0, 오류 0)

src/AxCopilot/Views/ChatWindow.SystemPromptBuilder.cs

@@ -64,7 +64,7 @@ public partial class ChatWindow
         sb.AppendLine("\nWhen the user explicitly asks for a plan (계획, 계획 수립, 계획 먼저, plan), present a step-by-step plan FIRST and wait for approval before executing.");
         sb.AppendLine("For ordinary Cowork requests where no plan is requested, proceed directly with the work and focus on producing the requested result.");
         sb.AppendLine("If the user asks for a brand-new report, proposal, analysis, manual, or other document and does not explicitly ask to reference workspace files, do NOT start with glob, grep, document_read, or folder_map.");
-        sb.AppendLine("In that case, go straight to the creation tool. Use document_plan when creating multi-section documents (3+ pages) or when the user explicitly requests a plan.");
+        sb.AppendLine("In that case, go straight to the creation tool. Use document_plan only when multi-section structure work clearly improves the result or when the user explicitly requests a plan.");
         sb.AppendLine("After creating files, summarize what was created and include the actual output path.");
         sb.AppendLine("IMPORTANT: In your FINAL response after ALL work is done, provide a structured completion summary in this format:");
         sb.AppendLine("  - 작업 유형: (e.g., report/analysis/proposal)");
@@ -78,7 +78,7 @@ public partial class ChatWindow
         sb.AppendLine("IMPORTANT: When creating documents with dates, always use today's actual date above. Never use placeholder or fictional dates.");
         sb.AppendLine("IMPORTANT: For reports, proposals, analyses, and manuals with multiple sections:");
         sb.AppendLine("  1. Decide the document structure internally first.");
-        sb.AppendLine("  2. Use document_plan for multi-section documents or when the user explicitly asks for a plan. When the user requests a plan, present it for approval before proceeding.");
+        sb.AppendLine("  2. Use document_plan only when multi-section structure work clearly improves the result or when the user explicitly asks for a plan. When the user requests a plan, present it for approval before proceeding.");
         sb.AppendLine("  3. Then immediately create the real output file with html_create, docx_create, markdown_create, or file_write.");
         sb.AppendLine("  4. Fill every section with real content. Do not stop at an outline or plan only.");
         sb.AppendLine("  5. The task is complete only after the actual document file has been created or updated.");
@@ -250,7 +250,7 @@ public partial class ChatWindow
         sb.AppendLine("3. IMPLEMENT: Apply the smallest safe edit. Use file_edit for existing files and file_write for new files.");
         sb.AppendLine("4. VERIFY: Run build_run/test_loop when the change affects buildable or testable behavior, or when the user explicitly asks for verification.");
         sb.AppendLine("   - Use git_tool(diff) when it helps confirm the final change set or explain what changed.");
-        sb.AppendLine("5. REPORT: Summarize what changed and what was verified. Mention remaining risk only when something is actually unresolved.");
+        sb.AppendLine("5. REPORT: Summarize what changed and what was verified. Mention remaining risk only when something is actually unresolved, especially for review or high-impact changes.");
 
         sb.AppendLine("\n## Development Environment");
         sb.AppendLine("Use dev_env_detect to check installed IDEs, runtimes, and build tools before running commands.");