컨텍스트는 claude-code식으로 유지하고 품질 강제는 AX 기준으로 복원한다

- Cowork 문서 생성 가이드에 richer section pattern과 생성 후 점검 요약을 다시 넣어 단조로운 문서와 빈약한 최종 요약을 보강

- docs 태스크 최종 보고 프롬프트를 별도 분기해 출력 파일 경로, 핵심 섹션, 구성 규모, 생성 후 확인 사항을 다시 강하게 요구

- balanced/reasoning_first/document_heavy 프로필에서 문서 검증 게이트와 최종 보고 게이트를 복원해 품질 강제를 AX 기준으로 유지

- 검증: 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

@@ -65,6 +65,8 @@ public partial class ChatWindow
         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 only when multi-section structure work clearly improves the result or when the user explicitly requests a plan.");
+        sb.AppendLine("When writing a new document, avoid repetitive same-shape sections. Tailor the structure to the purpose and use summaries, findings, comparison tables, timelines, recommendations, appendices, or action items when they improve clarity.");
+        sb.AppendLine("Prefer concrete and useful content over filler. If a section benefits from bullets, tables, or structured comparison, use them instead of flat generic paragraphs.");
         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)");
@@ -72,6 +74,7 @@ public partial class ChatWindow
         sb.AppendLine("  - 주요 섹션: list key sections/chapters with brief description");
         sb.AppendLine("  - 분량: page count, word count estimate");
         sb.AppendLine("  - 사용 도구: tools used during creation");
+        sb.AppendLine("  - verification: what you checked after generation (section completeness, placeholders, formatting, dates, etc.)");
         sb.AppendLine("The user wants to see what the document contains at a glance without opening the file.");
         sb.AppendLine("Do not stop after a single step. Continue autonomously until the request is completed or a concrete blocker (permission denial, missing dependency, hard error) is encountered.");
         sb.AppendLine("When adapting external references, rewrite names/structure/comments to AX Copilot style. Avoid clone-like outputs.");
@@ -81,6 +84,7 @@ public partial class ChatWindow
         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("  4-1. Use richer section patterns when they help: summary box, key findings bullets, comparison table, timeline, checklist, action items, appendix.");
         sb.AppendLine("  5. The task is complete only after the actual document file has been created or updated.");
 
         // 문서 품질 검증 루프