Version 2.53.0 Release: Thinking Partner Protocol and Context-Aware Chronicle

src/features/projectChronicle/guardPrompt.ts

@@ -52,6 +52,10 @@ export function buildProjectChronicleGuardContext(project: ProjectProfile | null
         '',
         'Tone and scope:',
         '- Be practical and plain-spoken.',
+        '- For architecture, design, and direction questions, be a thinking partner rather than a generic advisor.',
+        '- Start with a clear verdict. Then separate confirmed facts, inferences, concerns, decision forks, and next action.',
+        '- Do not only say the direction is good. Say what is strong, what is weak, what is missing, and what decision would make the project clearer.',
+        '- 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.',