fix(prompt): translate inferred user intent and blocking questions to Korean headings

src/features/projectChronicle/guardPrompt.ts

@@ -23,12 +23,12 @@ export function buildProjectChronicleGuardContext(project: ProjectProfile | null
         '1. Short conclusion first: 2-5 simple sentences that state the main answer before detail.',
         '2. Brief summary: one compact paragraph by default. Avoid bullet-heavy formatting.',
         '3. Detailed answer.',
-        '4. Request summary.',
-        '5. Inferred user intent.',
-        '6. Project record target check. If no project is selected, ask whether to use an existing project, create a new project, or skip recording.',
+        '4. Request summary (must use heading `## 요청 요약`).',
+        '5. Inferred user intent (must use heading `## 사용자 의도 추론`).',
+        '6. Project record target check (must use heading `## 프로젝트 기록 대상 확인`). If no project is selected, ask whether to use an existing project, create a new project, or skip recording.',
         '7. Record path check. If no record root is available, say a Markdown record path is required before writing files.',
-        '8. Ask only 1 to 3 blocking questions.',
-        '9. For every question, include "Question reason" explaining why it changes storage, scope, dependencies, or implementation direction.',
+        '8. Ask only 1 to 3 blocking questions (must use heading `## 핵심 확인 질문`).',
+        '9. For every question, include "질문 의도" (in Korean instead of "Question reason") explaining why it changes storage, scope, dependencies, or implementation direction.',
         '10. Direction review focused on project fit and dependency risk.',
         '11. Recommend a low-dependency MVP first.',
         '12. Put Vector DB, relational DB, knowledge graph, semantic search, and complex automation only under "Later expansion" unless the user explicitly asks for them now.',
@@ -62,7 +62,7 @@ export function buildProjectChronicleGuardContext(project: ProjectProfile | null
         '- If the user is using the tool to organize their thinking, reflect the shape of their uncertainty and turn it into 1-2 concrete choices.',
         '- Keep the top conclusion calm and short so the user can understand the answer before reading the long version.',
         '- Prefer short paragraphs with blank lines between numbered sections. Avoid starting most lines with `*` or `-` bullets.',
-        '- Use visible markdown headings such as `## 간단 요약`, `## 요청 요약`, `## 상세 답변`, and `## 추가 조언` for major sections.',
+        '- Use visible markdown headings such as `## 간단 요약`, `## 요청 요약`, `## 상세 답변`, `## 사용자 의도 추론`, and `## 핵심 확인 질문` for major sections.',
         '- Avoid grand phrases like advanced cognitive architecture, compounding knowledge, perfect graph, or ultimate knowledge distiller.',
         '- When the user wants low dependency, keep the first proposal to Markdown, JSON, local files, and explicit user save actions.',
         '- Do not jump directly to large architectures. Narrow direction before expanding.',