fix: improve analysis chat rendering, scroll, and traceability persistence

- Fix bold markdown not rendering: reorder repairMarkdownMarkers so
space-adding runs before trim, preventing trim from being undone
- Apply same fix to normalizeAssistantContent before saving to DB
- Add auto-scroll to bottom on send, scroll to top of AI answer on
stream complete
- Tighten markdown spacing (my-3→my-1.5, leading-7→leading-6, space-y-2→space-y-0.5)
- Fix traceability disappearing on page refresh by using message_id
returned from API (now provided by backend) instead of hardcoding
doneMessageId from the agentic stream

.claude/skills/speckit-implement/SKILL.md

@@ -49,7 +49,7 @@ You **MUST** consider the user input before proceeding (if not empty).
     **Automatic Pre-Hook**: {extension}
     Executing: `/{command}`
     EXECUTE_COMMAND: {command}
-    
+
     Wait for the result of the hook command before proceeding to the Outline.
     ```
 - If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently
@@ -150,7 +150,7 @@ You **MUST** consider the user input before proceeding (if not empty).
 
 6. Execute implementation following the task plan:
    - **Phase-by-phase execution**: Complete each phase before moving to the next
-   - **Respect dependencies**: Run sequential tasks in order, parallel tasks [P] can run together  
+   - **Respect dependencies**: Run sequential tasks in order, parallel tasks [P] can run together
    - **Follow TDD approach**: Execute test tasks before their corresponding implementation tasks
    - **File-based coordination**: Tasks affecting the same files must run sequentially
    - **Validation checkpoints**: Verify each phase completion before proceeding

.claude/skills/speckit-specify/SKILL.md

@@ -144,20 +144,20 @@ Given that feature description, do this:
 
       ```markdown
       # Specification Quality Checklist: [FEATURE NAME]
-      
+
       **Purpose**: Validate specification completeness and quality before proceeding to planning
       **Created**: [DATE]
       **Feature**: [Link to spec.md]
-      
+
       ## Content Quality
-      
+
       - [ ] No implementation details (languages, frameworks, APIs)
       - [ ] Focused on user value and business needs
       - [ ] Written for non-technical stakeholders
       - [ ] All mandatory sections completed
-      
+
       ## Requirement Completeness
-      
+
       - [ ] No [NEEDS CLARIFICATION] markers remain
       - [ ] Requirements are testable and unambiguous
       - [ ] Success criteria are measurable
@@ -166,16 +166,16 @@ Given that feature description, do this:
       - [ ] Edge cases are identified
       - [ ] Scope is clearly bounded
       - [ ] Dependencies and assumptions identified
-      
+
       ## Feature Readiness
-      
+
       - [ ] All functional requirements have clear acceptance criteria
       - [ ] User scenarios cover primary flows
       - [ ] Feature meets measurable outcomes defined in Success Criteria
       - [ ] No implementation details leak into specification
-      
+
       ## Notes
-      
+
       - Items marked incomplete require spec updates before `/speckit-clarify` or `/speckit-plan`
       ```
 
@@ -200,20 +200,20 @@ Given that feature description, do this:
 
            ```markdown
            ## Question [N]: [Topic]
-           
+
            **Context**: [Quote relevant spec section]
-           
+
            **What we need to know**: [Specific question from NEEDS CLARIFICATION marker]
-           
+
            **Suggested Answers**:
-           
+
            | Option | Answer | Implications |
            |--------|--------|--------------|
            | A      | [First suggested answer] | [What this means for the feature] |
            | B      | [Second suggested answer] | [What this means for the feature] |
            | C      | [Third suggested answer] | [What this means for the feature] |
            | Custom | Provide your own answer | [Explain how to provide custom input] |
-           
+
            **Your choice**: _[Wait for user response]_
            ```
 

.claude/skills/speckit-tasks/SKILL.md

@@ -49,7 +49,7 @@ You **MUST** consider the user input before proceeding (if not empty).
     **Automatic Pre-Hook**: {extension}
     Executing: `/{command}`
     EXECUTE_COMMAND: {command}
-    
+
     Wait for the result of the hook command before proceeding to the Outline.
     ```
 - If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently
@@ -151,7 +151,7 @@ Every task MUST strictly follow this format:
 4. **[Story] label**: REQUIRED for user story phase tasks only
    - Format: [US1], [US2], [US3], etc. (maps to user stories from spec.md)
    - Setup phase: NO story label
-   - Foundational phase: NO story label  
+   - Foundational phase: NO story label
    - User Story phases: MUST have story label
    - Polish phase: NO story label
 5. **Description**: Clear action with exact file path

.specify/templates/checklist-template.md

@@ -6,16 +6,16 @@
 
 **Note**: This checklist is generated by the `/speckit-checklist` command based on feature context and requirements.
 
-<!-- 
+<!--
   ============================================================================
   IMPORTANT: The checklist items below are SAMPLE ITEMS for illustration only.
-  
+
   The /speckit-checklist command MUST replace these with actual items based on:
   - User's specific checklist request
   - Feature requirements from spec.md
   - Technical context from plan.md
   - Implementation details from tasks.md
-  
+
   DO NOT keep these sample items in the generated checklist file.
   ============================================================================
 -->

docs/API_CONTRACT_BE_GOLANG.md

@@ -106,7 +106,7 @@ Flow yang direkomendasikan:
 2. Ambil `data.id` dari response sebagai `analysis_id`.
 3. Frontend memanggil AI Agent Service terpisah memakai context analysis, business_questions, dan catalog.
 4. Saat user mulai bertanya ke AI Agent Service, rekam pertanyaan dengan `role=user` ke endpoint messages.
-5. Setelah AI Agent Service menjawab, simpan jawaban dengan `role=ai` dan `message_id` dari event `done` Python ke endpoint messages.
+5. Setelah AI Agent Service menjawab, simpan jawaban dengan `role=ai` ke endpoint messages.
 
 ### 5. Conversation Recording
 
@@ -128,7 +128,6 @@ Frontend bertanggung jawab melakukan dua write terpisah:
 ```json
 {
   "role": "ai",
-  "message_id": "msg_88f1",
   "content": "Revenue Q3 turun terutama karena penurunan volume transaksi di segmen enterprise..."
 }
 ```
@@ -141,7 +140,7 @@ Frontend bertanggung jawab melakukan dua write terpisah:
 | `POST` | `/api/login` | Login dan issue token pair |
 | `POST` | `/api/refresh` | Rotate refresh token dan issue token pair baru |
 | `GET` | `/api/v1/documents/doctypes` | List tipe dokumen yang didukung |
-| `POST` | `/api/v1/document/upload` | Upload dokumen ke Azure Blob Storage |
+| `POST` | `/api/v1/document/upload` | Upload dokumen ke private object storage |
 | `POST` | `/api/v1/document/upload-local` | Upload dokumen ke local filesystem untuk benchmark |
 | `POST` | `/api/v1/document/process` | Proses dokumen async |
 | `GET` | `/api/v1/documents/{user_id}` | List dokumen milik user |
@@ -244,6 +243,8 @@ Errors: `400`, `401`, `403`, `500`.
 
 Status umum: `uploaded`, `processing`, `processed`, `failed`.
 
+`blob_name` dipertahankan untuk kompatibilitas response lama, tetapi secara kontrak frontend harus dipahami sebagai stored object reference di private object storage, bukan Azure-specific blob URL.
+
 ### `GET /api/v1/documents/doctypes`
 
 Mengambil tipe dokumen yang didukung.
@@ -267,7 +268,7 @@ Success `200`:
 
 ### `POST /api/v1/document/upload`
 
-Upload dokumen ke Azure Blob Storage. Maksimum 10 MB. Mendukung `pdf`, `docx`, `txt`, `csv`, dan `xlsx`.
+Upload dokumen ke private object storage. Maksimum 10 MB. Mendukung `pdf`, `docx`, `txt`, `csv`, dan `xlsx`.
 
 Content-Type: `multipart/form-data`
 
@@ -284,7 +285,7 @@ Errors: `400`, `401`, `403`, `429`, `500`.
 
 ### `POST /api/v1/document/upload-local`
 
-Upload file ke filesystem lokal untuk benchmarking. Kontrak form sama dengan upload Azure.
+Upload file ke filesystem lokal untuk benchmarking. Kontrak form sama dengan upload object storage.
 
 Success `201`:
 
@@ -347,7 +348,7 @@ Errors: `401`, `403`, `500`.
 
 ### `DELETE /api/v1/document/delete`
 
-Menghapus dokumen dari storage, embedding/parquet terkait, dan record database.
+Menghapus dokumen dari private object storage, embedding/parquet terkait, dan record database.
 
 Request:
 
@@ -548,7 +549,7 @@ Success `200`:
         "source_id": "document-or-client-id",
         "source_type": "tabular",
         "name": "sales.csv",
-        "location_ref": "blob/path/or/db-ref",
+        "location_ref": "object-storage/path/or/db-ref",
         "table_count": 1,
         "updated_at": "2026-06-30T08:00:00Z"
       }
@@ -806,7 +807,6 @@ Errors:
   "user_id": "user-id",
   "role": "user",
   "content": "Apa penyebab revenue turun di Q3?",
-  "message_id": null,
   "created_at": "2026-06-30T08:00:00Z"
 }
 ```
@@ -816,8 +816,6 @@ Errors:
 - `user`: pertanyaan atau instruksi dari user
 - `ai`: jawaban dari AI Agent Service
 
-`message_id` nullable untuk `role=user`, tetapi wajib untuk `role=ai`. Nilainya harus sama dengan `message_id` dari event `done` Python Agentic Service agar message history dapat dikorelasikan dengan observability.
-
 ### `POST /api/v1/analyses/{id}/messages`
 
 Merekam tepat satu pesan conversation ke `analyses_messages`.
@@ -831,12 +829,11 @@ Request untuk pertanyaan user:
 }
 ```
 
-Request untuk jawaban AI. `message_id` wajib berasal dari event `done` Python Agentic Service, bukan dibuat oleh frontend:
+Request untuk jawaban AI:
 
 ```json
 {
   "role": "ai",
-  "message_id": "msg_88f1",
   "content": "Revenue turun karena penurunan transaksi enterprise dan kenaikan churn di wilayah barat."
 }
 ```
@@ -849,21 +846,23 @@ Success `201`:
   "message": "Message created",
   "data": {
     "message": {
-      "id": "message-id",
+      "id": "uuid-dari-db",
+      "message_id": "uuid-dari-db",
       "analysis_id": "analysis-id",
       "user_id": "user-id",
       "role": "user",
       "content": "Apa penyebab revenue turun di Q3?",
-      "message_id": null,
       "created_at": "2026-06-30T08:00:00Z"
     }
   }
 }
 ```
 
+> `message_id` bernilai sama dengan `id` — disertakan agar frontend dapat langsung menggunakannya untuk memanggil endpoint observability (`GET /api/v1/observability?analysis_id=...&message_id=...`) tanpa mapping tambahan.
+
 Errors:
 
-- `400`: invalid role/content/message_id, invalid analysis ID
+- `400`: invalid role/content, invalid analysis ID
 - `401`: token invalid/missing
 - `409`: inactive analysis atau message limit tercapai
 
@@ -884,11 +883,23 @@ Success `200`:
   "status": "success",
   "message": "Messages retrieved",
   "data": {
-    "messages": []
+    "messages": [
+      {
+        "id": "uuid-dari-db",
+        "message_id": "uuid-dari-db",
+        "analysis_id": "analysis-id",
+        "user_id": "user-id",
+        "role": "ai",
+        "content": "Revenue turun karena penurunan transaksi enterprise.",
+        "created_at": "2026-06-30T08:01:00Z"
+      }
+    ]
   }
 }
 ```
 
+> Setiap item menyertakan `message_id` (sama dengan `id`) untuk digunakan frontend pada pemanggilan `GET /api/v1/observability?analysis_id=...&message_id=...` setelah page refresh.
+
 Errors: `400`, `401`, `404`.
 
 ## Suggested Frontend Integration Sequence
@@ -931,7 +942,7 @@ GET  /api/v1/data-catalog/{user_id}
 POST /api/v1/analyses with business_questions
 call AI Agent Service outside this service
 POST /api/v1/analyses/{analysis_id}/messages with role=user and content=user_question
-POST /api/v1/analyses/{analysis_id}/messages with role=ai, content=agent_answer, and message_id=python_done_message_id
+POST /api/v1/analyses/{analysis_id}/messages with role=ai and content=agent_answer
 GET  /api/v1/analyses/{analysis_id}/messages
 ```
 
@@ -939,16 +950,8 @@ GET  /api/v1/analyses/{analysis_id}/messages
 
 - Jangan mengirim pesan user ke `POST /api/v1/analyses/{id}/messages` dengan ekspektasi service ini akan menjawab. Endpoint ini hanya persistence.
 - AI Agent Service adalah service terpisah. Service ini menyimpan metadata analysis, knowledge catalog, data binding, dan history conversation.
-- Untuk pesan `role=ai`, simpan `message_id` yang dikembalikan Python pada event `done` agar history conversation dapat dikorelasikan dengan observability Python.
 - User-level catalog berisi seluruh knowledge source user; analysis-level catalog hanya berisi source yang ada di `data_bind` analysis.
 - Perubahan `data_bind` akan rebuild analysis-level catalog. Frontend juga dapat memanggil endpoint rebuild analysis catalog secara eksplisit jika diperlukan.
 - Setelah refresh token sukses, selalu replace refresh token lama dengan refresh token baru.
 - Untuk endpoint yang membutuhkan `user_id`, gunakan `data.user.id` dari login dan pastikan sama dengan token aktif.
-- Untuk binding analysis, pakai source yang sudah berhasil diupload/diproses atau database client yang sudah diingest.
-
-
-
-
-
-
-
+- Untuk binding analysis, pakai source yang sudah berhasil diupload/diproses atau database client yang sudah diingest.

docs/API_CONTRACT_BE_PYTHON.md

@@ -98,7 +98,7 @@ event: status
 data: Running 3 steps...
 
 event: chunk
-data: Total sales by region last quarter: 
+data: Total sales by region last quarter:
 
 event: chunk
 data: Central led at $1.21M (38%), East $0.74M, West $0.55M (down 12% QoQ).

specs/001-unified-analysis-chat/contracts/ENDPOINTS.md

@@ -1,8 +1,8 @@
-> Superseded planning note: For the 2026-06-30 dual-backend UX plan, use `frontend-dual-backend-contract.md` as the authoritative frontend contract. This file is retained as historical context from the older endpoint analysis.
+> Superseded planning note: For the 2026-06-30 dual-backend UX plan, use `frontend-dual-backend-contract.md` as the authoritative frontend contract. This file is retained as historical context from the older endpoint analysis.
 # Backend API Endpoints Required
 
-**Feature**: Unified Analysis Chat with Skills  
-**Date**: 2026-06-15  
+**Feature**: Unified Analysis Chat with Skills
+**Date**: 2026-06-15
 **Status**: Required for Implementation
 
 ## Overview
@@ -779,7 +779,7 @@ Based on Success Criteria:
 
 2. **Message Order**: Ensure messages are returned in chronological order (timestamp ASC) for proper conversation flow.
 
-3. **Validation**: 
+3. **Validation**:
    - Validate title length (1-200 chars)
    - Validate problem statement length (1-2000 chars)
    - Prevent removing all data sources from an analysis

specs/001-unified-analysis-chat/contracts/ENDPOINTS_BY_TASK.md

@@ -1,4 +1,4 @@
-> Superseded planning note: For the 2026-06-30 dual-backend UX plan, use `frontend-dual-backend-contract.md` as the authoritative frontend contract. This file is retained as historical context from the older endpoint analysis.
+> Superseded planning note: For the 2026-06-30 dual-backend UX plan, use `frontend-dual-backend-contract.md` as the authoritative frontend contract. This file is retained as historical context from the older endpoint analysis.
 # Backend Endpoints Needed - Organized by Task
 
 This document maps frontend implementation tasks to the backend endpoints they depend on.
@@ -273,19 +273,19 @@ updateAnalysis(analysisId, { dataSources: [...] }); // Already needed
 ## Summary: All Required Endpoints
 
 ### MUST HAVE (MVP):
-1. ✅ POST `/api/analyses` - Create analysis
-2. ✅ GET `/api/analyses` - List analyses
-3. ✅ GET `/api/analyses/:id` - Get analysis with messages
-4. ✅ PUT `/api/analyses/:id` - Update analysis
-5. ✅ DELETE `/api/analyses/:id` - Delete analysis
-6. ✅ POST `/api/analyses/:id/messages` - Add message/invoke skill
-7. ✅ GET `/api/analyses/:id/messages` - Get messages (paginated)
-8. ✅ GET `/api/skills` - Get available skills with status
-9. ✅ GET `/api/datasources` - Get available data sources
+1. [OK] POST `/api/analyses` - Create analysis
+2. [OK] GET `/api/analyses` - List analyses
+3. [OK] GET `/api/analyses/:id` - Get analysis with messages
+4. [OK] PUT `/api/analyses/:id` - Update analysis
+5. [OK] DELETE `/api/analyses/:id` - Delete analysis
+6. [OK] POST `/api/analyses/:id/messages` - Add message/invoke skill
+7. [OK] GET `/api/analyses/:id/messages` - Get messages (paginated)
+8. [OK] GET `/api/skills` - Get available skills with status
+9. [OK] GET `/api/datasources` - Get available data sources
 
 ### NICE TO HAVE (Optional):
-10. ⚠️ GET `/api/skills/:skillName` - Get single skill details
-11. ⚠️ WebSocket `/ws/analyses/:id` - Real-time skill status updates
+10. [WARN] GET `/api/skills/:skillName` - Get single skill details
+11. [WARN] WebSocket `/ws/analyses/:id` - Real-time skill status updates
 
 ---
 
@@ -297,7 +297,7 @@ updateAnalysis(analysisId, { dataSources: [...] }); // Already needed
 3. **READ**: GET `/api/analyses` with pagination
 4. **READ**: GET `/api/analyses/:id` with messages included
 5. **UPDATE**: PUT `/api/analyses/:id` with validation (min 1 source)
-6. **DELETE**: DELETE `/api/analyses/:id` 
+6. **DELETE**: DELETE `/api/analyses/:id`
 7. **READ**: GET `/api/skills` with status computation
 8. **READ**: GET `/api/datasources`
 
@@ -315,16 +315,16 @@ updateAnalysis(analysisId, { dataSources: [...] }); // Already needed
 
 ## Backend Testing Checklist
 
-- [ ] POST `/api/analyses` with valid data → returns 201 with full object
-- [ ] POST `/api/analyses` without data sources → returns 400 "MIN_SOURCES_REQUIRED"
-- [ ] GET `/api/analyses` → returns user's analyses only
-- [ ] GET `/api/analyses/:id` for other user's analysis → returns 403 Forbidden
-- [ ] PUT `/api/analyses/:id` removing all sources → returns 400 "Cannot remove all sources"
-- [ ] GET `/api/skills?analysisId=X` → returns status based on analysis state
-- [ ] POST `/api/analyses/:id/messages` with unmet precondition → returns 400 "PRECONDITION_UNMET"
-- [ ] POST `/api/analyses/:id/messages` with valid skill → returns 201 with message + skillResponse
-- [ ] GET `/api/datasources` → returns documents/databases user has access to
-- [ ] All endpoints without auth → return 401 Unauthorized
+- [ ] POST `/api/analyses` with valid data -> returns 201 with full object
+- [ ] POST `/api/analyses` without data sources -> returns 400 "MIN_SOURCES_REQUIRED"
+- [ ] GET `/api/analyses` -> returns user's analyses only
+- [ ] GET `/api/analyses/:id` for other user's analysis -> returns 403 Forbidden
+- [ ] PUT `/api/analyses/:id` removing all sources -> returns 400 "Cannot remove all sources"
+- [ ] GET `/api/skills?analysisId=X` -> returns status based on analysis state
+- [ ] POST `/api/analyses/:id/messages` with unmet precondition -> returns 400 "PRECONDITION_UNMET"
+- [ ] POST `/api/analyses/:id/messages` with valid skill -> returns 201 with message + skillResponse
+- [ ] GET `/api/datasources` -> returns documents/databases user has access to
+- [ ] All endpoints without auth -> return 401 Unauthorized
 - [ ] Pagination works (limit, offset, hasMore)
 - [ ] Error responses include error code, message, timestamp
 

specs/001-unified-analysis-chat/contracts/ENDPOINTS_SUMMARY.md

@@ -1,7 +1,7 @@
-> Superseded planning note: For the 2026-06-30 dual-backend UX plan, use `frontend-dual-backend-contract.md` as the authoritative frontend contract. This file is retained as historical context from the older endpoint analysis.
+> Superseded planning note: For the 2026-06-30 dual-backend UX plan, use `frontend-dual-backend-contract.md` as the authoritative frontend contract. This file is retained as historical context from the older endpoint analysis.
 # Backend API Endpoints - Quick Reference
 
-## 📋 Endpoint Summary
+##  Endpoint Summary
 
 | Category | Endpoint | Method | Purpose |
 |----------|----------|--------|---------|
@@ -18,7 +18,7 @@
 
 ---
 
-## 🎯 Frontend Dependency by Task
+##  Frontend Dependency by Task
 
 ### Phase 2 Foundational Tasks Needed:
 - **T010**: `analysisService.ts` needs endpoints: POST/GET/PUT/DELETE `/api/analyses`, GET `/api/analyses/:id/messages`
@@ -35,7 +35,7 @@
 
 ---
 
-## 🚀 Critical Endpoints for MVP (User Story 1 Only)
+##  Critical Endpoints for MVP (User Story 1 Only)
 
 If delivering MVP with just **US1 (Unified Interface)**:
 
@@ -48,7 +48,7 @@ These 4 endpoints are the **absolute minimum** to display a working unified chat
 
 ---
 
-## 🔑 Key Features of Each Endpoint
+##  Key Features of Each Endpoint
 
 ### Skill Status Management
 ```
@@ -61,7 +61,7 @@ Response includes:
 
 **Frontend responsibility**: Display which skills are available and why others are disabled
 
-**Backend responsibility**: 
+**Backend responsibility**:
 - Compute `status` based on analysis state and skill preconditions
 - Examples:
   - `/analyze-*` skills are `unavailable` until `/problem-statement` is called
@@ -80,7 +80,7 @@ PUT /api/analyses/:id
   Error if: Attempting to remove all sources
 ```
 
-**Frontend responsibility**: 
+**Frontend responsibility**:
 - Validate form before submission (min 1 source selected)
 - Show error if trying to remove last source
 
@@ -93,9 +93,9 @@ PUT /api/analyses/:id
 ### Skill Invocation with Preconditions
 ```
 POST /api/analyses/:id/messages
-  Request: { 
+  Request: {
     content: "/analyze-descriptive",
-    skillName: "analyze-descriptive" 
+    skillName: "analyze-descriptive"
   }
 
 Response if precondition unmet:
@@ -108,7 +108,7 @@ Response if precondition unmet:
 ```
 
 **Frontend responsibility**:
-- Display error message in chat: "❌ /analyze-descriptive requires /problem-statement to be completed first"
+- Display error message in chat: "[NO] /analyze-descriptive requires /problem-statement to be completed first"
 - Don't gray out skills (backend handles status via GET /api/skills)
 
 **Backend responsibility**:
@@ -117,7 +117,7 @@ Response if precondition unmet:
 
 ---
 
-## 📊 Message Structure
+##  Message Structure
 
 Every message in the system has this structure:
 
@@ -142,7 +142,7 @@ Every message in the system has this structure:
 
 ---
 
-## âš¡ Performance Targets
+## Performance Performance Targets
 
 Per Success Criteria from spec.md:
 
@@ -156,7 +156,7 @@ Per Success Criteria from spec.md:
 
 ---
 
-## 🔐 Authentication & Authorization
+##  Authentication & Authorization
 
 - **All endpoints** require authenticated user (JWT token / session)
 - **User isolation**: Only return/allow access to user's own analyses
@@ -164,7 +164,7 @@ Per Success Criteria from spec.md:
 
 ---
 
-## 📝 Error Response Format
+##  Error Response Format
 
 All errors follow this format:
 
@@ -188,36 +188,36 @@ All errors follow this format:
 
 ---
 
-## 🔄 Data Flow Example: Skill Invocation
+## Refresh Data Flow Example: Skill Invocation
 
 ```
 User types: "/analyze-descriptive" in chat
-        ↓
+        v
 Frontend: POST /api/analyses/:id/messages
   {
     content: "/analyze-descriptive",
     skillName: "analyze-descriptive"
   }
-        ↓
+        v
 Backend checks:
-  1. Is user authenticated? ✓
-  2. Does user own analysis? ✓
-  3. Are preconditions met? 
-     - Is /problem-statement called? ✓
-     - Any other preconditions? ✓
+  1. Is user authenticated? [OK]
+  2. Does user own analysis? [OK]
+  3. Are preconditions met?
+     - Is /problem-statement called? [OK]
+     - Any other preconditions? [OK]
   4. Execute skill with analysis context
   5. Return result
-        ↓
+        v
 Backend response (201 Created):
   {
-    "message": { 
+    "message": {
       user message with skill metadata
     },
     "skillResponse": {
       system message with skill output
     }
   }
-        ↓
+        v
 Frontend displays:
   - User message: "/analyze-descriptive" (styled with skill icon)
   - System message: "[skill output]" (styled as system response)
@@ -225,7 +225,7 @@ Frontend displays:
 
 ---
 
-## 📋 Checklist for Backend Implementation
+##  Checklist for Backend Implementation
 
 - [ ] Create Analysis table/collection with fields: id, title, problemStatement, dataSources, createdAt, updatedAt, ownerId
 - [ ] Create Message table/collection with fields: id, analysisId, content, author, timestamp, isSkillInvocation, skillName, skillStatus
@@ -242,7 +242,7 @@ Frontend displays:
 
 ---
 
-## 📞 Questions for Backend Team
+##  Questions for Backend Team
 
 1. **Skill Execution**: How long do skills take to execute? Should we make skill invocation async with polling/websocket for updates?
 

specs/001-unified-analysis-chat/contracts/ENDPOINT_COMPARISON.md

@@ -1,118 +1,118 @@
-> Superseded planning note: For the 2026-06-30 dual-backend UX plan, use `frontend-dual-backend-contract.md` as the authoritative frontend contract. This file is retained as historical context from the older endpoint analysis.
+> Superseded planning note: For the 2026-06-30 dual-backend UX plan, use `frontend-dual-backend-contract.md` as the authoritative frontend contract. This file is retained as historical context from the older endpoint analysis.
 # Endpoint Comparison: Existing vs Needed
 
 ---
 
-## 📊 Visual Comparison
+##  Visual Comparison
 
 ### EXISTING STRUCTURE (Current State)
 
 ```
 Frontend Pages:
-├── Analytics Page (Chat Rooms)
-│   ├── GET /api/v1/chat-rooms              (List rooms)
-│   ├── POST /api/v1/chat-rooms             (Create room)
-│   ├── GET /api/v1/chat-rooms/:roomId      (Get room + messages)
-│   ├── DELETE /api/v1/chat-rooms/:roomId   (Delete room)
-│   └── POST /api/v1/chat/stream            (Send message, get streaming response)
-│
-├── Knowledge Management Page (Documents + Databases)
-│   ├── GET /api/v1/documents/:userId       (List documents)
-│   ├── POST /api/v1/document/upload        (Upload doc)
-│   ├── POST /api/v1/document/process       (Process doc)
-│   ├── DELETE /api/v1/document/delete      (Delete doc)
-│   ├── GET /api/v1/database-clients/dbtypes
-│   ├── POST /api/v1/database-clients       (Connect DB)
-│   ├── GET /api/v1/database-clients/:userId
-│   ├── DELETE /api/v1/database-clients/:id
-│   └── POST /api/v1/database-clients/:id/ingest
-│
-└── Interview Page (Separate)
-    ├── GET /frameworks
-    ├── POST /api/v1/interviews/sessions           (Create session)
-    ├── POST /api/v1/interviews/sessions/:id/message
-    ├── POST /api/v1/interviews/sessions/:id/finish
-    ├── GET /api/v1/interviews/:roomId/result
-    └── POST /api/v1/interviews/sessions/:id/stream-message
++-- Analytics Page (Chat Rooms)
+|   +-- GET /api/v1/chat-rooms              (List rooms)
+|   +-- POST /api/v1/chat-rooms             (Create room)
+|   +-- GET /api/v1/chat-rooms/:roomId      (Get room + messages)
+|   +-- DELETE /api/v1/chat-rooms/:roomId   (Delete room)
+|   +-- POST /api/v1/chat/stream            (Send message, get streaming response)
+|
++-- Knowledge Management Page (Documents + Databases)
+|   +-- GET /api/v1/documents/:userId       (List documents)
+|   +-- POST /api/v1/document/upload        (Upload doc)
+|   +-- POST /api/v1/document/process       (Process doc)
+|   +-- DELETE /api/v1/document/delete      (Delete doc)
+|   +-- GET /api/v1/database-clients/dbtypes
+|   +-- POST /api/v1/database-clients       (Connect DB)
+|   +-- GET /api/v1/database-clients/:userId
+|   +-- DELETE /api/v1/database-clients/:id
+|   +-- POST /api/v1/database-clients/:id/ingest
+|
++-- Interview Page (Separate)
+    +-- GET /frameworks
+    +-- POST /api/v1/interviews/sessions           (Create session)
+    +-- POST /api/v1/interviews/sessions/:id/message
+    +-- POST /api/v1/interviews/sessions/:id/finish
+    +-- GET /api/v1/interviews/:roomId/result
+    +-- POST /api/v1/interviews/sessions/:id/stream-message
 ```
 
 ### NEW STRUCTURE (After Unified Analysis Chat)
 
 ```
 Frontend:
-├── Unified Analysis Chat Page
-│   ├── POST /api/analyses                   (Create analysis) [NEW or EXTEND chat-rooms]
-│   ├── GET /api/analyses                    (List analyses) [NEW or EXTEND]
-│   ├── GET /api/analyses/:id                (Get analysis + messages) [NEW or EXTEND]
-│   ├── PUT /api/analyses/:id                (Update analysis) [NEW - untuk update datasources]
-│   ├── DELETE /api/analyses/:id             (Delete analysis) [NEW or EXTEND]
-│   │
-│   ├── POST /api/analyses/:id/messages      (Add message/invoke skill) [NEW - extend chat/stream]
-│   ├── GET /api/analyses/:id/messages       (List messages paginated) [NEW]
-│   │
-│   ├── GET /api/skills?analysisId=X        (Get available skills) [NEW - skill management]
-│   ├── GET /api/skills/:skillName          (Get skill detail) [NEW - optional]
-│   │
-│   └── GET /api/datasources                (Get documents + databases) [NEW - aggregate]
-│
-├── Knowledge Management (TETAP ADA)
-│   └── Same as before
-│
-└── Interview (TETAP ADA atau DIGABUNG)
-    └── Same as before or merged
++-- Unified Analysis Chat Page
+|   +-- POST /api/analyses                   (Create analysis) [NEW or EXTEND chat-rooms]
+|   +-- GET /api/analyses                    (List analyses) [NEW or EXTEND]
+|   +-- GET /api/analyses/:id                (Get analysis + messages) [NEW or EXTEND]
+|   +-- PUT /api/analyses/:id                (Update analysis) [NEW - untuk update datasources]
+|   +-- DELETE /api/analyses/:id             (Delete analysis) [NEW or EXTEND]
+|   |
+|   +-- POST /api/analyses/:id/messages      (Add message/invoke skill) [NEW - extend chat/stream]
+|   +-- GET /api/analyses/:id/messages       (List messages paginated) [NEW]
+|   |
+|   +-- GET /api/skills?analysisId=X        (Get available skills) [NEW - skill management]
+|   +-- GET /api/skills/:skillName          (Get skill detail) [NEW - optional]
+|   |
+|   +-- GET /api/datasources                (Get documents + databases) [NEW - aggregate]
+|
++-- Knowledge Management (TETAP ADA)
+|   +-- Same as before
+|
++-- Interview (TETAP ADA atau DIGABUNG)
+    +-- Same as before or merged
 ```
 
 ---
 
-## 🔄 Endpoint Reuse Strategy
+## Refresh Endpoint Reuse Strategy
 
 ### Which Endpoints Can Be Reused/Extended?
 
-#### ✅ REUSABLE (Logic mirip):
+#### [OK] REUSABLE (Logic mirip):
 
 ```
-Chat Rooms → Analysis CRUD
-├── GET /api/v1/chat-rooms → GET /api/analyses
-│   Same: List user's conversations
-│   Diff: Response includes dataSources + problem_statement
-│
-├── POST /api/v1/chat-rooms → POST /api/analyses
-│   Same: Create new conversation
-│   Diff: Require dataSources, problem_statement; no longer optional title
-│
-├── GET /api/v1/chat-rooms/:id → GET /api/analyses/:id
-│   Same: Get full conversation with messages
-│   Diff: Include dataSources, problem_statement, skill metadata in messages
-│
-└── DELETE /api/v1/chat-rooms/:id → DELETE /api/analyses/:id
+Chat Rooms -> Analysis CRUD
++-- GET /api/v1/chat-rooms -> GET /api/analyses
+|   Same: List user's conversations
+|   Diff: Response includes dataSources + problem_statement
+|
++-- POST /api/v1/chat-rooms -> POST /api/analyses
+|   Same: Create new conversation
+|   Diff: Require dataSources, problem_statement; no longer optional title
+|
++-- GET /api/v1/chat-rooms/:id -> GET /api/analyses/:id
+|   Same: Get full conversation with messages
+|   Diff: Include dataSources, problem_statement, skill metadata in messages
+|
++-- DELETE /api/v1/chat-rooms/:id -> DELETE /api/analyses/:id
     Same: Delete conversation
     Diff: Same logic
 ```
 
 ```
-Chat Message → Analysis Message + Skill Metadata
-├── POST /api/v1/chat/stream → POST /api/analyses/:id/messages
-│   Same: Send message to conversation, get response
-│   Diff: Add skillName, skillParams; add skill invocation metadata
-│         Response includes message + optional skillResponse
-│
-└── NEW REQUIREMENT: GET /api/analyses/:id/messages
+Chat Message -> Analysis Message + Skill Metadata
++-- POST /api/v1/chat/stream -> POST /api/analyses/:id/messages
+|   Same: Send message to conversation, get response
+|   Diff: Add skillName, skillParams; add skill invocation metadata
+|         Response includes message + optional skillResponse
+|
++-- NEW REQUIREMENT: GET /api/analyses/:id/messages
     Needed for: Paginated message history when switching analyses
     Similar to: GET /api/v1/chat-rooms/:id (but paginated messages)
 ```
 
 ```
-Knowledge Base → Data Sources
-├── GET /api/v1/documents → GET /api/datasources (documents type)
-│   Same: List available data sources
-│   Diff: Filter by type, more metadata
-│
-└── GET /api/v1/database-clients → GET /api/datasources (database type)
+Knowledge Base -> Data Sources
++-- GET /api/v1/documents -> GET /api/datasources (documents type)
+|   Same: List available data sources
+|   Diff: Filter by type, more metadata
+|
++-- GET /api/v1/database-clients -> GET /api/datasources (database type)
     Same: List available data sources
     Diff: Aggregate with documents, unified response
 ```
 
-#### ❌ TIDAK BISA REUSE (Logic baru):
+#### [NO] TIDAK BISA REUSE (Logic baru):
 
 ```
 NEW: PUT /api/analyses/:id
@@ -133,12 +133,12 @@ NEW: POST /api/analyses/:id/messages with skill precondition validation
 
 ---
 
-## 📈 Data Structure Comparison
+##  Data Structure Comparison
 
 ### Current: Room vs New: Analysis
 
 ```typescript
-// ❌ EXISTING: Room (from api.ts)
+// [NO] EXISTING: Room (from api.ts)
 interface Room {
   id: string;
   title: string;
@@ -156,7 +156,7 @@ interface RoomMessage {
   sources?: ChatSource[]; // References to documents used
 }
 
-// ✅ NEW: Analysis (needed for new feature)
+// [OK] NEW: Analysis (needed for new feature)
 interface Analysis {
   id: string;
   title: string;
@@ -194,7 +194,7 @@ interface DataSource {
 
 ---
 
-## 🔌 Integration Points
+##  Integration Points
 
 ### How Frontend Will Call New Endpoints
 
@@ -240,8 +240,8 @@ const analyses = await api.getAnalyses(limit=50);        // NEW
 
 // On sidebar item click:
 const messages = await api.getAnalysisMessages(          // NEW
-  analysisId, 
-  limit=50, 
+  analysisId,
+  limit=50,
   offset=0
 );
 // Load paginated message history
@@ -249,29 +249,29 @@ const messages = await api.getAnalysisMessages(          // NEW
 
 ---
 
-## 📋 Implementation Checklist for Backend
+##  Implementation Checklist for Backend
 
 ### Phase 1: Extend Existing Endpoints (2 days)
 
 ```
-☐ Extend Room table schema:
+[ ] Extend Room table schema:
   - Add: problem_statement TEXT
   - Add: data_sources JSONB
-  
-☐ Extend POST /api/v1/chat-rooms:
+
+[ ] Extend POST /api/v1/chat-rooms:
   - Add: problem_statement, dataSources to request
   - Validate: dataSources.length >= 1
   - Test: Create analysis with data sources
-  
-☐ Extend GET /api/v1/chat-rooms:
+
+[ ] Extend GET /api/v1/chat-rooms:
   - Include: problem_statement, dataSources in response
   - Test: Verify data sources in response
-  
-☐ Extend GET /api/v1/chat-rooms/:id:
+
+[ ] Extend GET /api/v1/chat-rooms/:id:
   - Include: problem_statement, dataSources
   - Test: Verify full analysis structure
-  
-☐ Extend PUT /api/v1/chat-rooms/:id → PUT /api/analyses/:id:
+
+[ ] Extend PUT /api/v1/chat-rooms/:id -> PUT /api/analyses/:id:
   - New endpoint: Update analysis
   - Allow update: title, problem_statement, data_sources
   - Validate: dataSources.length >= 1
@@ -281,37 +281,37 @@ const messages = await api.getAnalysisMessages(          // NEW
 ### Phase 2: New Endpoints (2 days)
 
 ```
-☐ Implement GET /api/datasources:
+[ ] Implement GET /api/datasources:
   - Aggregate: documents + database clients
   - Format: { id, name, type: "document" | "database" }
   - Test: Get datasources, verify both types included
-  
-☐ Implement GET /api/skills:
+
+[ ] Implement GET /api/skills:
   - Query param: analysisId (required)
   - Return: Array of 10 skills with status
-  - Status logic: 
-    - /analyze-* skills → unavailable until /problem-statement called
-    - /help, /check-*, /retrieve-* → always available
+  - Status logic:
+    - /analyze-* skills -> unavailable until /problem-statement called
+    - /help, /check-*, /retrieve-* -> always available
   - Test: Verify status changes based on analysis messages
-  
-☐ Extend RoomMessage schema:
+
+[ ] Extend RoomMessage schema:
   - Add: is_skill_invocation BOOLEAN
   - Add: skill_name VARCHAR(255)
   - Add: skill_status VARCHAR(50)
-  
-☐ Extend POST /api/v1/chat/stream → POST /api/analyses/:id/messages:
+
+[ ] Extend POST /api/v1/chat/stream -> POST /api/analyses/:id/messages:
   - New endpoint or extend existing
   - Input: { content, skillName?, skillParams? }
   - Validate: Check skill preconditions
   - Return error if precondition unmet:
     { error: "PRECONDITION_UNMET", precondition: "problem-statement" }
-  - Execute skill → return both user message + skill response
-  - Test: 
-    - Send regular message → works
-    - Send skill with met preconditions → works
-    - Send skill with unmet preconditions → error 400
-  
-☐ Implement GET /api/analyses/:id/messages (PAGINATED):
+  - Execute skill -> return both user message + skill response
+  - Test:
+    - Send regular message -> works
+    - Send skill with met preconditions -> works
+    - Send skill with unmet preconditions -> error 400
+
+[ ] Implement GET /api/analyses/:id/messages (PAGINATED):
   - Query: limit=50, offset=0
   - Return: { messages, pagination }
   - Test: Large message history, pagination works
@@ -320,26 +320,26 @@ const messages = await api.getAnalysisMessages(          // NEW
 ### Phase 3: Testing & Integration (1 day)
 
 ```
-☐ Integration tests:
-  - Create analysis → Get analysis → Verify structure
-  - Send message → Get messages → Verify in list
-  - Invoke skill → Verify response + skill status
-  - Update datasources → Verify changes persisted
-  
-☐ Error handling tests:
-  - Create analysis without dataSources → 400
-  - Invoke skill without precondition → 400 PRECONDITION_UNMET
-  - Remove all datasources → 400
-  
-☐ Frontend integration:
-  - Frontend calls new endpoints → works
-  - Skill invocation → displays status correctly
-  - Datasource selection → lists both documents & databases
+[ ] Integration tests:
+  - Create analysis -> Get analysis -> Verify structure
+  - Send message -> Get messages -> Verify in list
+  - Invoke skill -> Verify response + skill status
+  - Update datasources -> Verify changes persisted
+
+[ ] Error handling tests:
+  - Create analysis without dataSources -> 400
+  - Invoke skill without precondition -> 400 PRECONDITION_UNMET
+  - Remove all datasources -> 400
+
+[ ] Frontend integration:
+  - Frontend calls new endpoints -> works
+  - Skill invocation -> displays status correctly
+  - Datasource selection -> lists both documents & databases
 ```
 
 ---
 
-## 🎯 Summary Table
+##  Summary Table
 
 | Endpoint | Existing | Status | Effort |
 |----------|----------|--------|--------|

specs/001-unified-analysis-chat/contracts/EXISTING_ENDPOINTS_ANALYSIS.md

@@ -1,39 +1,39 @@
-> Superseded planning note: For the 2026-06-30 dual-backend UX plan, use `frontend-dual-backend-contract.md` as the authoritative frontend contract. This file is retained as historical context from the older endpoint analysis.
+> Superseded planning note: For the 2026-06-30 dual-backend UX plan, use `frontend-dual-backend-contract.md` as the authoritative frontend contract. This file is retained as historical context from the older endpoint analysis.
 # Analisis Endpoint API Existing di Frontend
 
-**Tanggal**: 2026-06-15  
+**Tanggal**: 2026-06-15
 **Purpose**: Memahami endpoint mana yang sudah ada vs yang perlu ditambah untuk fitur Unified Analysis Chat
 
 ---
 
-## 📍 Lokasi API Service Files
+##  Lokasi API Service Files
 
 ```
 src/services/
-├── api.ts                    # Main API service (Orchestration & Agentic)
-└── interviewApi.ts           # Interview-specific API
++-- api.ts                    # Main API service (Orchestration & Agentic)
++-- interviewApi.ts           # Interview-specific API
 ```
 
 ---
 
-## 🔗 Base URLs yang Digunakan
+##  Base URLs yang Digunakan
 
 ```typescript
 // Dari src/env atau environment variables:
 
 ORCHESTRATION_API_BASE_URL = "https://api-orchestration.example.com"
-  ↓ Untuk: Chat Rooms, Documents, Database Clients, Data Catalog
+  v Untuk: Chat Rooms, Documents, Database Clients, Data Catalog
 
-AGENTIC_API_BASE_URL = "https://api-agentic.example.com"  
-  ↓ Untuk: Chat Streaming (Analytics/Chat Page)
+AGENTIC_API_BASE_URL = "https://api-agentic.example.com"
+  v Untuk: Chat Streaming (Analytics/Chat Page)
 
 INTERVIEW_BASE_URL = "https://api-interview.example.com"
-  ↓ Untuk: Interview Page
+  v Untuk: Interview Page
 ```
 
 ---
 
-## 📊 Endpoint Existing - Diorganisir Berdasarkan Feature
+##  Endpoint Existing - Diorganisir Berdasarkan Feature
 
 ### 1. AUTHENTICATION (src/services/api.ts)
 
@@ -68,13 +68,13 @@ Ini adalah fitur **MIRIP** dengan "Analysis" yang kita butuh, tapi nama/struktur
 // Location: src/services/api.ts:140-166
 export const getRooms = (userId: string): Promise<Room[]> =>
   request<{ status: string; message: string; data: Room[] | null }>(
-    ORCHESTRATION_BASE_URL, 
+    ORCHESTRATION_BASE_URL,
     `/api/v1/chat-rooms?user_id=${userId}`
   ).then(res => res.data ?? []);
 
 export const getRoom = (roomId: string): Promise<RoomDetail> =>
   request<{ status: string; message: string; data: RoomDetail }>(
-    ORCHESTRATION_BASE_URL, 
+    ORCHESTRATION_BASE_URL,
     `/api/v1/chat-rooms/${roomId}`
   ).then(res => res.data);
 
@@ -92,7 +92,7 @@ export const deleteRoom = (roomId: string, userId: string) =>
   );
 ```
 
-**🎯 Catatan**: Ini sudah mirip dengan Analysis CRUD yang kita butuh! 
+** Catatan**: Ini sudah mirip dengan Analysis CRUD yang kita butuh!
 - Room = Analysis (conversation)
 - RoomMessage = Message (tapi belum punya skill metadata)
 
@@ -112,7 +112,7 @@ export const deleteRoom = (roomId: string, userId: string) =>
 // Location: src/services/api.ts:170-212
 export const getDocuments = (userId: string): Promise<ApiDocument[]> =>
   request<{ status: string; message: string; data: ApiDocument[] | null }>(
-    ORCHESTRATION_BASE_URL, 
+    ORCHESTRATION_BASE_URL,
     `/api/v1/documents/${userId}`
   ).then(res => res.data ?? []);
 
@@ -120,7 +120,7 @@ export const uploadDocument = async (userId: string, file: File) => {
   const form = new FormData();
   form.append("user_id", userId);
   form.append("file", file);
-  
+
   const res = await fetch(`${ORCHESTRATION_BASE_URL}/api/v1/document/upload`, {
     method: "POST",
     body: form,
@@ -136,7 +136,7 @@ export const deleteDocument = (userId: string, documentId: string) =>
   );
 ```
 
-**🎯 Catatan**: Ini adalah bagian dari "DataSources" yang kita butuh!
+** Catatan**: Ini adalah bagian dari "DataSources" yang kita butuh!
 - Documents = Tipe data source (document type)
 - Kita perlu: `GET /api/datasources` untuk menampilkan opsi pilihan data source dalam dialog
 
@@ -156,7 +156,7 @@ export const deleteDocument = (userId: string, documentId: string) =>
 // Location: src/services/api.ts:264-295
 export const getDatabaseClientTypes = (): Promise<DbTypeInfo[]> =>
   request<{ status: string; message: string; data: DbTypeInfo[] | null }>(
-    ORCHESTRATION_BASE_URL, 
+    ORCHESTRATION_BASE_URL,
     "/api/v1/database-clients/dbtypes"
   ).then(res => res.data ?? []);
 
@@ -167,7 +167,7 @@ export const connectDatabase = (
   credentials: Record<string, string | number | boolean>
 ): Promise<DatabaseClient> =>
   request<{ status: string; message: string; data: DatabaseClient }>(
-    ORCHESTRATION_BASE_URL, 
+    ORCHESTRATION_BASE_URL,
     `/api/v1/database-clients`, {
     method: "POST",
     body: JSON.stringify({ user_id: userId, name, db_type: dbType, credentials }),
@@ -175,12 +175,12 @@ export const connectDatabase = (
 
 export const getDatabaseClients = (userId: string): Promise<DatabaseClient[]> =>
   request<{ status: string; message: string; data: DatabaseClient[] | null }>(
-    ORCHESTRATION_BASE_URL, 
+    ORCHESTRATION_BASE_URL,
     `/api/v1/database-clients/${userId}`
   ).then(res => res.data ?? []);
 
 export const ingestDatabaseClient = (
-  clientId: string, 
+  clientId: string,
   userId: string
 ): Promise<IngestResponse> =>
   request<{ status: string; message: string; data: IngestResponse }>(
@@ -190,7 +190,7 @@ export const ingestDatabaseClient = (
   ).then(res => res.data);
 ```
 
-**🎯 Catatan**: Ini juga bagian dari "DataSources"!
+** Catatan**: Ini juga bagian dari "DataSources"!
 - Database Clients = Type data source (database type)
 - Ingest = Process untuk membuat data tersedia
 
@@ -241,7 +241,7 @@ export const streamChat = (
   });
 ```
 
-**🎯 Catatan**: Ini endpoint untuk mengirim message ke chat!
+** Catatan**: Ini endpoint untuk mengirim message ke chat!
 - Mirip dengan: `POST /api/analyses/:id/messages` yang kita butuh
 - Tapi ini hanya untuk plain message, belum ada skill invocation metadata
 
@@ -295,13 +295,13 @@ export const streamMessage = (
   });
 ```
 
-**🎯 Catatan**: Interview adalah fitur TERSENDIRI
+** Catatan**: Interview adalah fitur TERSENDIRI
 - Kemungkinan: Kita akan **MERGER** interview + analytics menjadi satu Analysis Chat
 - Tapi interview API tetap terpisah untuk structured interview flow
 
 ---
 
-## 📈 Ringkasan Endpoint Existing
+##  Ringkasan Endpoint Existing
 
 ### Total: 22 Endpoint
 
@@ -309,65 +309,65 @@ export const streamMessage = (
 
 | Feature | Count | Status |
 |---------|-------|--------|
-| Authentication | 1 | ✅ |
-| Chat Rooms (Analysis equivalents) | 5 | ✅ |
-| Documents (Data Sources) | 5 | ✅ |
-| Database Clients (Data Sources) | 4 | ✅ |
-| Data Catalog | 2 | ✅ |
-| Chat Streaming | 1 | ✅ |
-| Interview | 6 | ✅ |
+| Authentication | 1 | [OK] |
+| Chat Rooms (Analysis equivalents) | 5 | [OK] |
+| Documents (Data Sources) | 5 | [OK] |
+| Database Clients (Data Sources) | 4 | [OK] |
+| Data Catalog | 2 | [OK] |
+| Chat Streaming | 1 | [OK] |
+| Interview | 6 | [OK] |
 
 ---
 
-## 🆕 Endpoint BARU yang Dibutuhkan untuk Unified Analysis Chat
+##  Endpoint BARU yang Dibutuhkan untuk Unified Analysis Chat
 
 Dari dokumentasi yang sudah saya buat (`ENDPOINTS.md`), inilah endpoint BARU yang perlu ditambah:
 
 | Endpoint | Status | Catatan |
 |----------|--------|---------|
-| `POST /api/analyses` | 🆕 NEW | Bisa reuse logika `POST /api/v1/chat-rooms` |
-| `GET /api/analyses` | 🆕 NEW | Bisa reuse logika `GET /api/v1/chat-rooms` |
-| `GET /api/analyses/:id` | 🆕 NEW | Bisa reuse logika `GET /api/v1/chat-rooms/:id` |
-| `PUT /api/analyses/:id` | 🆕 NEW | TIDAK ADA yang mirip sekarang |
-| `DELETE /api/analyses/:id` | 🆕 NEW | Bisa reuse logika `DELETE /api/v1/chat-rooms/:id` |
-| `POST /api/analyses/:id/messages` | 🆕 NEW | Mirip `POST /api/v1/chat/stream`, tapi dengan skill metadata |
-| `GET /api/analyses/:id/messages` | 🆕 NEW | GET messages dengan pagination, TIDAK ADA sekarang |
-| `GET /api/skills` | 🆕 NEW | TIDAK ADA - untuk skill discovery |
-| `GET /api/datasources` | 🆕 NEW | BISA REUSE dari `/api/v1/documents` + `/api/v1/database-clients` |
-| `GET /api/skills/:skillName` | 🆕 NEW | Optional - untuk skill details |
+| `POST /api/analyses` |  NEW | Bisa reuse logika `POST /api/v1/chat-rooms` |
+| `GET /api/analyses` |  NEW | Bisa reuse logika `GET /api/v1/chat-rooms` |
+| `GET /api/analyses/:id` |  NEW | Bisa reuse logika `GET /api/v1/chat-rooms/:id` |
+| `PUT /api/analyses/:id` |  NEW | TIDAK ADA yang mirip sekarang |
+| `DELETE /api/analyses/:id` |  NEW | Bisa reuse logika `DELETE /api/v1/chat-rooms/:id` |
+| `POST /api/analyses/:id/messages` |  NEW | Mirip `POST /api/v1/chat/stream`, tapi dengan skill metadata |
+| `GET /api/analyses/:id/messages` |  NEW | GET messages dengan pagination, TIDAK ADA sekarang |
+| `GET /api/skills` |  NEW | TIDAK ADA - untuk skill discovery |
+| `GET /api/datasources` |  NEW | BISA REUSE dari `/api/v1/documents` + `/api/v1/database-clients` |
+| `GET /api/skills/:skillName` |  NEW | Optional - untuk skill details |
 
 ---
 
-## 🔄 Mapping: Endpoint Existing → Reusable untuk Analysis Chat
+## Refresh Mapping: Endpoint Existing -> Reusable untuk Analysis Chat
 
 ### BISA LANGSUNG REUSE:
 
 ```typescript
-// Chat Room CRUD → Analysis CRUD
+// Chat Room CRUD -> Analysis CRUD
 // Struktur sama, tinggal ubah nama endpoint
 
-❌ OLD: GET /api/v1/chat-rooms?user_id=X
-✅ NEW: GET /api/analyses (dengan user diambil dari auth)
+[NO] OLD: GET /api/v1/chat-rooms?user_id=X
+[OK] NEW: GET /api/analyses (dengan user diambil dari auth)
 
-❌ OLD: POST /api/v1/chat-rooms { user_id, title }
-✅ NEW: POST /api/analyses { title, problemStatement, dataSources }
+[NO] OLD: POST /api/v1/chat-rooms { user_id, title }
+[OK] NEW: POST /api/analyses { title, problemStatement, dataSources }
 
-❌ OLD: GET /api/v1/chat-rooms/:roomId
-✅ NEW: GET /api/analyses/:id (ubah response structure untuk support dataSources)
+[NO] OLD: GET /api/v1/chat-rooms/:roomId
+[OK] NEW: GET /api/analyses/:id (ubah response structure untuk support dataSources)
 
-❌ OLD: DELETE /api/v1/chat-rooms/:roomId?user_id=X
-✅ NEW: DELETE /api/analyses/:id
+[NO] OLD: DELETE /api/v1/chat-rooms/:roomId?user_id=X
+[OK] NEW: DELETE /api/analyses/:id
 ```
 
 ### PERLU DIMODIFIKASI:
 
 ```typescript
-// Chat Message → Analysis Message + Skill Metadata
-❌ OLD: POST /api/v1/chat/stream { user_id, room_id, message }
-✅ NEW: POST /api/analyses/:id/messages { 
-  content, 
-  skillName?, 
-  skillParams? 
+// Chat Message -> Analysis Message + Skill Metadata
+[NO] OLD: POST /api/v1/chat/stream { user_id, room_id, message }
+[OK] NEW: POST /api/analyses/:id/messages {
+  content,
+  skillName?,
+  skillParams?
 }
 
 Perbedaan:
@@ -378,51 +378,51 @@ Perbedaan:
 ### PERLU DIBIKIN BARU:
 
 ```typescript
-✅ NEW: GET /api/analyses/:id/messages (paginated)
-✅ NEW: GET /api/skills?analysisId=X (skill discovery dengan status)
-✅ NEW: GET /api/datasources (list of documents + databases)
-✅ NEW: PUT /api/analyses/:id (update title, problem, datasources)
+[OK] NEW: GET /api/analyses/:id/messages (paginated)
+[OK] NEW: GET /api/skills?analysisId=X (skill discovery dengan status)
+[OK] NEW: GET /api/datasources (list of documents + databases)
+[OK] NEW: PUT /api/analyses/:id (update title, problem, datasources)
 ```
 
 ---
 
-## 🏗️ Implementation Strategy untuk Backend
+##  Implementation Strategy untuk Backend
 
 ### Option 1: Reuse Chat Room (Recommended)
 
 ```
 Rename/Extend existing endpoints:
-/api/v1/chat-rooms → /api/analyses
-  ✅ Minimal code change
-  ✅ Reuse existing DB schema (bisa extend dengan column dataSources)
-  ✅ Reuse existing pagination, auth logic
+/api/v1/chat-rooms -> /api/analyses
+  [OK] Minimal code change
+  [OK] Reuse existing DB schema (bisa extend dengan column dataSources)
+  [OK] Reuse existing pagination, auth logic
 ```
 
 ### Option 2: Separate Analytics Service
 
 ```
 Create new service:
-/api/v1/analyses → Completely new implementation
-  ✅ Clean separation of concerns
-  ❌ More code duplication
-  ❌ Maintain 2 similar services
+/api/v1/analyses -> Completely new implementation
+  [OK] Clean separation of concerns
+  [NO] More code duplication
+  [NO] Maintain 2 similar services
 ```
 
 ### Option 3: Merge Everything
 
 ```
 Consolidate interview + analytics + chat into ONE service:
-/api/v1/analysis-sessions → Unified endpoint
-  ✅ Single source of truth
-  ❌ Big refactor, breaking changes
-  ❌ Remove existing interview API
+/api/v1/analysis-sessions -> Unified endpoint
+  [OK] Single source of truth
+  [NO] Big refactor, breaking changes
+  [NO] Remove existing interview API
 ```
 
 **Rekomendasi**: **Option 1** - Extend existing chat-rooms dengan skill metadata
 
 ---
 
-## 📋 Database Schema Changes Needed
+##  Database Schema Changes Needed
 
 **Existing Room table**:
 ```sql
@@ -467,7 +467,7 @@ CREATE TABLE analysis_messages (
 
 ---
 
-## 🎯 Skill Execution Logic Perlu Ditambah
+##  Skill Execution Logic Perlu Ditambah
 
 Endpoint existing **TIDAK ADA** untuk:
 - Tracking skill status (available vs unavailable)
@@ -499,20 +499,20 @@ export const invokeSkill = (analysisId: string, skillName: string) => {
 
 ---
 
-## 📝 Kesimpulan & Next Steps
+##  Kesimpulan & Next Steps
 
 ### Existing State:
-✅ Ada 22 endpoint untuk auth, chat rooms, documents, databases, chat streaming, interview
+[OK] Ada 22 endpoint untuk auth, chat rooms, documents, databases, chat streaming, interview
 
 ### Untuk Unified Analysis Chat, butuh:
-🆕 Tambah ~9 endpoint baru (atau extend yang existing)
+ Tambah ~9 endpoint baru (atau extend yang existing)
 - Sebagian bisa reuse logika existing chat-rooms
 - Perlu skill management logic baru
 - Perlu message pagination
 - Perlu data source aggregation
 
 ### Recommended Approach:
-1. **Extend** existing `/api/v1/chat-rooms` → `/api/analyses`
+1. **Extend** existing `/api/v1/chat-rooms` -> `/api/analyses`
    - Add `problem_statement`, `data_sources` fields
    - Add skill metadata ke messages
 2. **Create** new endpoints untuk skills

src/app/components/KnowledgeManagement.tsx

@@ -75,7 +75,7 @@ export default function KnowledgeManagement({
   onClose,
   variant = "modal",
 }: KnowledgeManagementProps) {
-  // ── Document state ──────────────────────────────────────────────────────────
+  // -- Document state ----------------------------------------------------------
   const [docTypes, setDocTypes] = useState<DocTypeInfo[]>([]);
   const [documents, setDocuments] = useState<ApiDocument[]>([]);
   const [loadingDocs, setLoadingDocs] = useState(false);
@@ -85,11 +85,11 @@ export default function KnowledgeManagement({
   const [processing, setProcessing] = useState<string | null>(null);
   const [deleting, setDeleting] = useState<string | null>(null);
 
-  // ── Navigation state ────────────────────────────────────────────────────────
+  // -- Navigation state --------------------------------------------------------
   const [view, setView] = useState<View>("main");
   const [selectedDbType, setSelectedDbType] = useState<DbType | null>(null);
 
-  // ── DB type & client state ──────────────────────────────────────────────────
+  // -- DB type & client state --------------------------------------------------
   const [dbTypeInfos, setDbTypeInfos] = useState<DbTypeInfo[]>([]);
   const [dbClients, setDbClients] = useState<DatabaseClient[]>([]);
   const [loadingDbTypes, setLoadingDbTypes] = useState(false);
@@ -104,11 +104,11 @@ export default function KnowledgeManagement({
   });
   const pollingTimers = useRef<Map<string, ReturnType<typeof setInterval>>>(new Map());
 
-  // ── Data Catalog state ──────────────────────────────────────────────────────
+  // -- Data Catalog state ------------------------------------------------------
   const [catalogSources, setCatalogSources] = useState<DataCatalogSource[]>([]);
   const [loadingCatalog, setLoadingCatalog] = useState(false);
 
-  // ── DB credentials form state ───────────────────────────────────────────────
+  // -- DB credentials form state -----------------------------------------------
   const [connectionName, setConnectionName] = useState("");
   const [dbForm, setDbForm] = useState<Record<string, string | number | boolean>>({});
   const [connecting, setConnecting] = useState(false);
@@ -184,7 +184,7 @@ export default function KnowledgeManagement({
     onClose();
   };
 
-  // ── Document handlers ───────────────────────────────────────────────────────
+  // -- Document handlers -------------------------------------------------------
 
   const loadDocuments = async (userId: string) => {
     setLoadingDocs(true);
@@ -277,7 +277,7 @@ export default function KnowledgeManagement({
     setDocuments([]);
   };
 
-  // ── DB handlers ─────────────────────────────────────────────────────────────
+  // -- DB handlers -------------------------------------------------------------
 
   const handleDbConnect = async () => {
     const userId = getUserId();
@@ -335,7 +335,7 @@ export default function KnowledgeManagement({
     }
   };
 
-  // ── Helpers ─────────────────────────────────────────────────────────────────
+  // -- Helpers -----------------------------------------------------------------
 
   const formatFileSize = (bytes: number) => {
     if (bytes < 1024) return bytes + " B";
@@ -419,7 +419,7 @@ export default function KnowledgeManagement({
 
   const isPage = variant === "page";
 
-  // ── Header title & back button logic ────────────────────────────────────────
+  // -- Header title & back button logic ----------------------------------------
 
   const selectedDbInfo = dbTypeInfos.find((d) => d.db_type === selectedDbType);
 
@@ -441,7 +441,7 @@ export default function KnowledgeManagement({
       ? () => setView("main")
       : null;
 
-  // ── Render ───────────────────────────────────────────────────────────────────
+  // -- Render -------------------------------------------------------------------
 
   return (
     <div className={isPage ? "knowledge-surface h-full min-h-screen bg-slate-50" : "knowledge-surface fixed inset-0 z-50 flex items-center justify-center bg-black/40 p-4 backdrop-blur-sm"}>
@@ -490,7 +490,7 @@ export default function KnowledgeManagement({
         {/* Content */}
         <div className={isPage ? "flex-1 overflow-y-auto px-6 py-5" : "flex-1 overflow-y-auto px-5 py-4"}>
 
-          {/* ── VIEW: main ── */}
+          {/* -- VIEW: main -- */}
           {view === "main" && (
             <div className="space-y-4">
 
@@ -509,7 +509,7 @@ export default function KnowledgeManagement({
                 <div className="text-center">
                   <p className="text-sm font-medium text-slate-700">
                     {uploading
-                      ? "Uploading…"
+                      ? "Uploading..."
                       : <>Drop files, or <span className="text-[#FF8F00]">browse</span></>
                     }
                   </p>
@@ -557,7 +557,7 @@ export default function KnowledgeManagement({
                 <div>
                   <div className="flex items-center justify-between mb-2">
                     <span className="text-[11px] font-semibold text-slate-400 uppercase tracking-wider">
-                      Databases · {dbClients.length}
+                      Databases - {dbClients.length}
                     </span>
                   </div>
                   <div className="space-y-1">
@@ -575,14 +575,14 @@ export default function KnowledgeManagement({
                         </div>
                         <div className="flex-1 min-w-0">
                           <p className="text-sm font-medium text-slate-800 truncate">{client.name}</p>
-                          <p className="text-xs text-slate-400 capitalize">{client.db_type} · {client.status}</p>
+                          <p className="text-xs text-slate-400 capitalize">{client.db_type} - {client.status}</p>
                         </div>
                         <div className="flex items-center gap-1.5 flex-shrink-0">
                           <div className="flex flex-col items-end gap-0.5">
                             <button
                               onClick={() => handleIngest(client.id)}
                               disabled={ingesting === client.id || client.status === "inactive"}
-                              title={ingestTimestamps[client.id] ? `Last ingested: ${new Date(ingestTimestamps[client.id]).toLocaleString()}` : "Never ingested — click to ingest schema"}
+                              title={ingestTimestamps[client.id] ? `Last ingested: ${new Date(ingestTimestamps[client.id]).toLocaleString()}` : "Never ingested -- click to ingest schema"}
                               className={[
                                 "flex items-center gap-1 text-xs px-2.5 py-1 rounded-lg transition disabled:opacity-40 disabled:cursor-not-allowed",
                                 ingestTimestamps[client.id]
@@ -595,7 +595,7 @@ export default function KnowledgeManagement({
                               ) : (
                                 <Database className="w-3 h-3" />
                               )}
-                              {ingesting === client.id ? "Ingesting…" : "Ingest"}
+                              {ingesting === client.id ? "Ingesting..." : "Ingest"}
                             </button>
                             {ingestTimestamps[client.id] && (
                               <span className="text-[10px] text-slate-300 leading-none">
@@ -676,7 +676,7 @@ export default function KnowledgeManagement({
                             {doc.filename}
                           </p>
                           <p className="text-xs text-slate-400">
-                            {formatFileSize(doc.file_size)} · {formatDate(doc.created_at)}
+                            {formatFileSize(doc.file_size)} - {formatDate(doc.created_at)}
                           </p>
                         </div>
                         <div className="flex flex-shrink-0 items-center gap-1.5 sm:gap-2">
@@ -702,7 +702,7 @@ export default function KnowledgeManagement({
             </div>
           )}
 
-          {/* ── VIEW: db-select ── */}
+          {/* -- VIEW: db-select -- */}
           {view === "db-select" && (
             <div className="space-y-4">
               <p className="text-sm text-slate-400">
@@ -760,7 +760,7 @@ export default function KnowledgeManagement({
             </div>
           )}
 
-          {/* ── VIEW: db-credentials ── */}
+          {/* -- VIEW: db-credentials -- */}
           {view === "db-credentials" && (
             <div className="space-y-4">
 
@@ -859,7 +859,7 @@ export default function KnowledgeManagement({
                 className="w-full flex items-center justify-center gap-2 bg-[#FF8F00] hover:bg-[#FF6F00] active:bg-[#E65100] text-white py-2.5 rounded-xl text-sm font-medium transition disabled:opacity-40 disabled:cursor-not-allowed"
               >
                 {connecting ? (
-                  <><Loader2 className="w-4 h-4 animate-spin" /> Connecting…</>
+                  <><Loader2 className="w-4 h-4 animate-spin" /> Connecting...</>
                 ) : (
                   "Connect"
                 )}
@@ -867,7 +867,7 @@ export default function KnowledgeManagement({
             </div>
           )}
 
-          {/* ── VIEW: catalog ── */}
+          {/* -- VIEW: catalog -- */}
           {view === "catalog" && (
             <div className="space-y-3">
               <button
@@ -897,7 +897,7 @@ export default function KnowledgeManagement({
                       <p className="text-sm font-medium text-slate-800 truncate">{src.name}</p>
                       <p className="text-xs text-slate-400">
                         {src.source_type === "schema" ? "Database" : "Tabular"}
-                        {src.table_count != null ? ` · ${src.table_count} table${src.table_count !== 1 ? "s" : ""}` : ""}
+                        {src.table_count != null ? ` - ${src.table_count} table${src.table_count !== 1 ? "s" : ""}` : ""}
                       </p>
                     </div>
                   </div>

src/app/components/analysis/AnalysisShell.tsx

@@ -43,8 +43,9 @@ const wait = (ms: number) => new Promise((resolve) => window.setTimeout(resolve,
 
 function normalizeAssistantContent(content: string) {
   return content
-    .replace(/\*\*\s+([^*\n]*?\S)\s*\*\*/g, "**$1**")
-    .replace(/\*\*([^*\n]*?\S)\s+\*\*/g, "**$1**")
+    .replace(/([A-Za-z0-9])(?=\*\*)/g, "$1 ")
+    .replace(/(\*\*[^*\n]+\*\*)(?=[A-Za-z0-9])/g, "$1 ")
+    .replace(/\*\*([^*\n]*?)\*\*/g, (_, inner) => `**${inner.trim()}**`)
     .trim();
 }
 
@@ -61,6 +62,7 @@ export function AnalysisShell() {
   const [loadingAnalyses, setLoadingAnalyses] = useState(true);
   const [loadingMessages, setLoadingMessages] = useState(false);
   const [streamState, setStreamState] = useState<StreamState>("idle");
+  const [scrollTo, setScrollTo] = useState<"bottom" | "last-ai" | null>(null);
   const [newAnalysisOpen, setNewAnalysisOpen] = useState(false);
   const [reportCollapsed, setReportCollapsed] = useState(false);
   const [staleSources, setStaleSources] = useState<DataBindItem[]>([]);
@@ -189,6 +191,7 @@ export function AnalysisShell() {
       },
     ]);
 
+    setScrollTo("bottom");
     setStreamState(kind === "chat" ? "streaming-chat" : "streaming-help");
     try {
       const onEvent = (event: AgentStreamEvent) => {
@@ -221,6 +224,8 @@ export function AnalysisShell() {
 
       const completedContent = normalizeAssistantContent(finalContent);
       let traceTargetId = aiId;
+      let resolvedMessageId = doneMessageId;
+      setScrollTo("last-ai");
       setMessages((prev) =>
         prev.map((msg) =>
           msg.id === aiId
@@ -232,16 +237,18 @@ export function AnalysisShell() {
       if (completedContent) {
         const saved = await createAnalysisMessage(activeAnalysis.id, { role: "ai", content: completedContent, message_id: doneMessageId });
         traceTargetId = saved.id;
+        const savedUi = toUiMessage(saved);
+        resolvedMessageId = savedUi.messageId ?? doneMessageId;
         setMessages((prev) =>
           prev.map((msg) =>
             msg.id === aiId
-              ? { ...toUiMessage(saved), messageId: doneMessageId, sources: msg.sources, traceabilityLoading: Boolean(doneMessageId) }
+              ? { ...savedUi, sources: msg.sources, traceabilityLoading: Boolean(savedUi.messageId) }
               : msg
           )
         );
       }
 
-      await fetchTraceability(activeAnalysis.id, doneMessageId, traceTargetId);
+      await fetchTraceability(activeAnalysis.id, resolvedMessageId, traceTargetId);
     } catch (err) {
       const message = err instanceof Error ? err.message : "Agent stream failed";
       setMessages((prev) => prev.map((msg) => (msg.id === aiId ? { ...msg, status: "error", statusText: message, traceabilityLoading: false } : msg)));
@@ -327,7 +334,7 @@ export function AnalysisShell() {
           {loadingMessages ? (
             <div className="flex h-full items-center justify-center text-sm text-slate-500">Loading messages</div>
           ) : (
-            <MessageList messages={messages} />
+            <MessageList messages={messages} scrollTo={scrollTo} onScrollDone={() => setScrollTo(null)} />
           )}
         </div>
         <ChatInput disabled={!activeAnalysis} streaming={streamState !== "idle"} onSend={handleSend} onHelp={handleHelp} />

src/app/components/analysis/MarkdownContent.tsx

@@ -6,10 +6,9 @@ import rehypeKatex from "rehype-katex";
 
 function repairMarkdownMarkers(line: string) {
   return line
-    .replace(/\*\*\s+([^*\n]*?\S)\s*\*\*/g, "**$1**")
-    .replace(/\*\*([^*\n]*?\S)\s+\*\*/g, "**$1**")
     .replace(/([A-Za-z0-9])(?=\*\*)/g, "$1 ")
-    .replace(/(\*\*[^*]+\*\*)(?=[A-Za-z0-9])/g, "$1 ");
+    .replace(/(\*\*[^*\n]+\*\*)(?=[A-Za-z0-9])/g, "$1 ")
+    .replace(/\*\*([^*\n]*?)\*\*/g, (_, inner) => `**${inner.trim()}**`);
 }
 
 function normalizeReadableMarkdown(content: string) {
@@ -50,14 +49,14 @@ function normalizeReadableMarkdown(content: string) {
 }
 
 const markdownComponents: Components = {
-  p: ({ children }) => <p className="my-3 leading-7 text-slate-800">{children}</p>,
-  ul: ({ children }) => <ul className="my-3 list-disc space-y-2 pl-5">{children}</ul>,
-  ol: ({ children }) => <ol className="my-3 list-decimal space-y-2 pl-5">{children}</ol>,
-  li: ({ children }) => <li className="pl-1 leading-7 text-slate-800">{children}</li>,
+  p: ({ children }) => <p className="my-1.5 leading-6 text-slate-800">{children}</p>,
+  ul: ({ children }) => <ul className="my-1.5 list-disc space-y-0.5 pl-5">{children}</ul>,
+  ol: ({ children }) => <ol className="my-1.5 list-decimal space-y-0.5 pl-5">{children}</ol>,
+  li: ({ children }) => <li className="pl-1 leading-6 text-slate-800">{children}</li>,
   strong: ({ children }) => <strong className="font-semibold text-slate-950">{children}</strong>,
-  h1: ({ children }) => <h1 className="mb-3 mt-5 text-xl font-semibold leading-7 text-slate-950">{children}</h1>,
-  h2: ({ children }) => <h2 className="mb-3 mt-5 text-lg font-semibold leading-7 text-slate-950">{children}</h2>,
-  h3: ({ children }) => <h3 className="mb-2 mt-4 text-base font-semibold leading-6 text-slate-950">{children}</h3>,
+  h1: ({ children }) => <h1 className="mb-2 mt-4 text-xl font-semibold leading-6 text-slate-950">{children}</h1>,
+  h2: ({ children }) => <h2 className="mb-2 mt-3 text-lg font-semibold leading-6 text-slate-950">{children}</h2>,
+  h3: ({ children }) => <h3 className="mb-1.5 mt-3 text-base font-semibold leading-6 text-slate-950">{children}</h3>,
   a: ({ children, href }) => (
     <a href={href} className="font-medium text-emerald-700 underline decoration-emerald-200 underline-offset-4" target="_blank" rel="noreferrer">
       {children}

src/app/components/analysis/MessageList.tsx

@@ -1,3 +1,4 @@
+import { useEffect, useRef } from "react";
 import { Bot, User } from "lucide-react";
 import type { UiMessage } from "./types";
 import { MarkdownContent } from "./MarkdownContent";
@@ -5,7 +6,28 @@ import { MessageTraceability } from "./MessageTraceability";
 import { EmptyState } from "./AnalysisStates";
 import { cx, formatDateTime } from "./utils";
 
-export function MessageList({ messages }: { messages: UiMessage[] }) {
+export function MessageList({
+  messages,
+  scrollTo,
+  onScrollDone,
+}: {
+  messages: UiMessage[];
+  scrollTo?: "bottom" | "last-ai" | null;
+  onScrollDone?: () => void;
+}) {
+  const containerRef = useRef<HTMLDivElement>(null);
+  const lastAiRef = useRef<HTMLElement>(null);
+
+  useEffect(() => {
+    if (!scrollTo) return;
+    if (scrollTo === "bottom") {
+      containerRef.current?.scrollIntoView({ block: "end", behavior: "smooth" });
+    } else if (scrollTo === "last-ai" && lastAiRef.current) {
+      lastAiRef.current.scrollIntoView({ block: "start", behavior: "smooth" });
+    }
+    onScrollDone?.();
+  }, [scrollTo]);
+
   if (messages.length === 0) {
     return (
       <div className="flex h-full items-center justify-center p-6">
@@ -14,12 +36,15 @@ export function MessageList({ messages }: { messages: UiMessage[] }) {
     );
   }
 
+  const lastAiIndex = messages.reduce((last, msg, i) => (msg.role === "ai" ? i : last), -1);
+
   return (
-    <div className="mx-auto flex w-full max-w-5xl flex-col gap-5 px-4 py-6">
-      {messages.map((message) => {
+    <div ref={containerRef} className="mx-auto flex w-full max-w-5xl flex-col gap-5 px-4 py-6">
+      {messages.map((message, index) => {
         const isUser = message.role === "user";
+        const isLastAi = index === lastAiIndex;
         return (
-          <article key={message.id} className={cx("flex min-w-0 gap-3", isUser && "justify-end")}>
+          <article ref={isLastAi ? lastAiRef : null} key={message.id} className={cx("flex min-w-0 gap-3", isUser && "justify-end")}>
             {!isUser && (
               <div className="mt-1 flex h-8 w-8 flex-shrink-0 items-center justify-center rounded-md bg-slate-900 text-white">
                 <Bot className="h-4 w-4" />