Improve search RAG validation and retrieval quality

.env.example

@@ -31,6 +31,7 @@ OPENAI_QUERY_CACHE_SIZE=200
 OPENAI_VISION_MODEL=gpt-5.5
 OPENAI_VISION_IMAGE_DETAIL=auto
 OPENAI_REQUEST_TIMEOUT_MS=45000
+OPENAI_ANSWER_TIMEOUT_MS=12000
 OPENAI_MAX_RETRIES=2
 OPENAI_GENERATION_MAX_RETRIES=0
 OPENAI_PROMPT_CACHE_RETENTION=24h

.prettierignore

@@ -11,3 +11,4 @@ package-lock.json
 public/demo-documents/
 .tmp-visual/
 scratch/
+.claude/worktrees/

TOOLS_CONTEXT_FOR_NEW_CHAT.md

@@ -1,31 +1,37 @@
 # Context handoff: Tools / Applications UX task
 
 ## Purpose
+
 I’m creating this file so a new chat can continue the exact task with full context, including screenshots referenced so far.
 
 ## Scope of this side conversation
+
 - This side conversation is separate from the main thread after a side boundary.
 - Pre-boundary history is reference-only and should not be treated as active instructions unless explicitly restated.
 - Active request in this side conversation was focused on design iteration and mockup direction for the Tools experience.
 - User now requested: create a context file with this chat + main run chat context including all images.
 
 ## Current repository/workspace
+
 - Working directory: `C:\Dev\Apps\Database`
 - No explicit code mutation request was made in this side chat beyond creating this handoff file.
 
 ## Latest user intent (current side thread)
+
 1. User asked to remove unimportant fields from the selected tool detail UI (examples: scope, source type, last use, etc.).
 2. User requested three new mockups in a better, more compact, polished style with stronger UX/UI treatment.
 3. User emphasized optimizing for popup/detail panel UX and improving design quality/compactness.
 
 ## Key visual/UX direction already established
+
 - Remove low-value fields from selected-tool details.
 - Keep focused content: identity/status, launch action, concise overview/description, primary actions, minimal context.
 - Preserve mobile-first detail presentation quality (slide-up/detail sheet style).
 - Keep tools functionality, improve layout density and hierarchy.
 - Keep design intentional and “best UX” style rather than boilerplate.
 
 ## What was done in this side thread (summary)
+
 - Read local frontend design skill file (non-mutating exploration only).
 - Generated three mockup designs:
  1. Compact action panel
@@ -35,6 +41,7 @@ I’m creating this file so a new chat can continue the exact task with full con
 - Shared recommendations to prefer concise, practical selected-tool detail content and keep popup behavior robust.
 
 ## Files/attachments referenced by user (screenshots)
+
 - `C:\Users\joshs\AppData\Local\Temp\codex-clipboard-79c36fc1-c28a-435c-bb2d-6988f78f89e1.png`
 - `C:\Users\joshs\AppData\Local\Temp\codex-clipboard-0c947a77-a138-4762-8152-441be907d12b.png`
 - `C:\Users\joshs\AppData\Local\Temp\codex-clipboard-8060b302-8f9b-4ae4-8f51-a3e7bfb51bac.png`
@@ -43,6 +50,7 @@ I’m creating this file so a new chat can continue the exact task with full con
 - `C:\Users\joshs\AppData\Local\Temp\codex-clipboard-0b05c4e9-1715-47c2-bd70-ed93133384ae.png`
 
 ## Inherited “main run chat” context (pre-boundary)
+
 - Earlier thread work focused on Tools/Applications navigation and behavior in the app.
 - User wanted the standalone `/applications` page preserved and restored.
 - User then asked to embed Applications launcher content into `/?mode=tools` while renaming visible copy to Tools.
@@ -51,10 +59,12 @@ I’m creating this file so a new chat can continue the exact task with full con
 - The side-thread task proceeded from this context but now is narrowed to design direction + new mockups.
 
 ## Notes for continuation in new chat
+
 - This file is only a handoff context snapshot; it does not include any uncommitted design/code changes in this side thread.
 - If continuing implementation, likely first action is reconciling existing Tools detail component with the above compact popup/content model.
 - Use the images above to ground visual expectations.
 - Keep `/applications` and `/?mode=tools` behavior requirements from the parent context in mind.
 
 ## Suggested prompt for new chat
+
 “Please continue from this context file. We need to implement the improved tools selected-item popup/detail view to remove low-value metadata (scope/source type/last use), keep core actions and context, and apply one of the three compact mockup directions (or a refinement). Preserve standalone `/applications` behavior and ensure `/ ?mode=tools` still works in desktop + mobile.”