Feat: Enhance query intent search and answer format readability

docs/records/ConnectAI/development/2026-05-02_answer-format-readability-tuning.md

@@ -0,0 +1,30 @@
+# Development Log: Answer Format Readability Tuning
+
+## Purpose
+Reduce visual clutter in assistant answers by discouraging bullet-heavy output and improving markdown heading readability in the chat UI.
+
+## User Feedback
+The answer content was useful, but many lines started with bullet dots, making the whole response feel visually messy. The user also wanted major sections such as simple summary, request summary, and additional advice to stand out more clearly.
+
+## Implementation Summary
+- Updated the base system prompt to prefer short paragraphs over bullet-heavy formatting.
+- Changed brief summary guidance from bullets to a compact paragraph by default.
+- Added guidance to separate numbered sections with blank lines.
+- Added guidance to use visible markdown headings such as `## 간단 요약`, `## 요청 요약`, and `## 상세 답변`.
+- Updated Project Chronicle Guard prompt with the same paragraph-first and heading guidance.
+- Increased markdown heading visibility in the sidebar UI.
+- Added paragraph and list spacing styles so markdown output is less cramped.
+
+## Changed Files
+- `src/utils.ts`
+- `src/features/projectChronicle/guardPrompt.ts`
+- `src/sidebarProvider.ts`
+- `tests/projectChronicleGuardPrompt.test.ts`
+
+## Verification
+- `./node_modules/.bin/tsc --noEmit`
+- `npm run compile`
+- `./node_modules/.bin/jest --runInBand`
+
+## Result
+Future answers should start with a short conclusion, use fewer bullet dots, separate numbered sections more clearly, and show major headings with better visual hierarchy.

docs/records/ConnectAI/development/2026-05-02_query-intent-search-tuning.md

@@ -0,0 +1,35 @@
+# Development Log: Query Intent Search Tuning
+
+## Purpose
+Improve Second Brain search relevance and answer framing for questions about customer evaluation, approval likelihood, UX, business value, and requirement fit.
+
+## User Feedback
+The answer became safer, but Second Brain still retrieved architecture documents for a question that was really about customer experience, approval risk, and business direction. Approval likelihood should also be labeled as inference, not fact.
+
+## Implementation Summary
+- Added `queryIntent` classification to Second Brain Trace:
+  - `technical`
+  - `ux-business`
+  - `governance`
+  - `general`
+- Expanded retrieval query terms based on intent.
+- For `ux-business`, boosted UX, customer journey, product discovery, virtual store, stakeholder approval, requirement fit, business value, acceptance criteria, and conversion-flow documents.
+- For `ux-business`, penalized API Gateway, microservice, monolithic, backend, database, routing, and generic architecture-principles paths.
+- Added Trace context guidance that approval likelihood is inference unless explicit approval criteria are provided.
+- Added base and Guard prompt guidance to prefer UX/business framing over technical architecture for these questions.
+- Added tests to verify UX/business docs outrank API Gateway docs for approval/customer-experience questions.
+
+## Changed Files
+- `src/features/secondBrainTrace.ts`
+- `src/features/projectChronicle/guardPrompt.ts`
+- `src/utils.ts`
+- `tests/secondBrainTrace.test.ts`
+- `tests/projectChronicleGuardPrompt.test.ts`
+
+## Verification
+- `./node_modules/.bin/tsc --noEmit`
+- `npm run compile`
+- `./node_modules/.bin/jest --runInBand`
+
+## Result
+Second Brain Trace should now better match the user's question intent. Customer approval and UX/business-fit questions should retrieve customer journey and business-value notes before generic technical architecture notes.

docs/records/ConnectAI/timeline.md

@@ -18,3 +18,5 @@
 - Added No Evidence, No Project Claim rules and Second Brain source type classification to prevent general notes from being treated as project implementation evidence.
 - Added project claim policy enforcement so main answers must treat general-only or mixed evidence as cautious and avoid unsupported technical structure claims.
 - Added a deterministic output brake that removes unsupported technical structure claims from final answers when Trace policy is `general-only`.
+- Tuned Second Brain retrieval by query intent so UX/business/approval questions prioritize customer journey, requirement fit, and business value notes over generic architecture notes.
+- Tuned answer readability: paragraph-first summaries, fewer bullet-heavy sections, clearer numbered-section spacing, and larger markdown headings in the sidebar.